Loading...
Loading...
Found 57 Skills
Audits and auto-fixes a project's CLAUDE.md against Anthropic best practices. Activates during ship phase — checks conciseness, enforces @import structure for detailed docs, auto-excludes bloat, identifies hook candidates, and auto-fixes structural issues. Flags content questions for developer review.
Post-restart smoke tests + auto-fix for gbrain and OpenClaw environments. Tests critical services, auto-fixes known issues, extensible via user-defined test scripts in ~/.gbrain/smoke-tests.d/*.sh.
Deep linter reference for authoring or debugging a vigiles enforce() rule — plugin tables, AST selectors, type-aware rules, auto-fix, and edge cases for ESLint, Ruff, Pylint, RuboCop, and Stylelint. Use when you need the exact rule name or config for a specific linter, not for running a linter.
Python code quality with ruff linter. Fast linting, rule selection, auto-fixing, and configuration. Use when checking Python code quality, enforcing standards, or finding bugs.
Runs Vale prose linter on markdown/text files and auto-fixes issues. Use when the user asks to lint, proofread, or improve writing quality of markdown or text files.
Run Python (ruff) and JavaScript (Biome) linting, formatting, and code quality checks with auto-fix support. Use when code needs linting, formatting, or style checking before commits. Use for "lint", "format", "ruff", "biome", "code style", or "check quality". Do NOT use for comprehensive code review (use systematic-code-review).
Review code for quality, security, and pattern compliance, then auto-fix Critical/High issues. Grounds every finding in actual codebase reference files.
Comprehensive security auditing for Clawdbot deployments. Scans for exposed credentials, open ports, weak configs, and vulnerabilities. Auto-fix mode included.
Validate SKILL.md frontmatter and .feature-radar/ files against format rules. Runs validate.sh, reports errors/warnings, and auto-fixes issues. MUST use this skill after editing any SKILL.md or .feature-radar/ file — catches format bugs like the 1024-char description limit before they break skill registration. Use when: - User says "validate", "check format", "lint skills", "run validation" - You just edited a SKILL.md (description, name, or body) — run proactively - You created or modified files in .feature-radar/ — run proactively - Before committing changes that touch skills/ or .feature-radar/ - User asks "are my skills valid?", "verify skills", "check skill format" IMPORTANT: Use this proactively after ANY edit to skills/ or .feature-radar/ files, even if the user doesn't ask for it. Format validation prevents silent breakage.
Pre-commit review: security scan, quality gates, auto-fix.
Inspect or run the manual maintenance workflow. Uses explicitly configured repository checks, applies safe auto-fixes, and archives successful maintenance changes.
Scan, fix, and remediate security vulnerabilities in a local code repository using Mobb MCP/CLI. Use when the user asks to scan for vulnerabilities, run a security check, auto-fix issues, remediate findings, or apply Mobb fixes (e.g., \"scan this repo\", \"fix security issues\", \"remediate vulnerabilities\", \"run Mobb on my changes\").