
Use when appending structured perf investigation notes and evidence.
Use when running controlled perf experiments to validate hypotheses.
Sync documentation with code. Use when user asks to update docs, check docs, fix stale documentation, update changelog, or after code changes.
Use when user asks to "validate delivery", "check readiness", or "verify completion". Runs tests, build, and requirement checks with pass/fail instructions.
Browse and interact with web pages headlessly. Use when agent needs to navigate websites, click elements, fill forms, read content, or take screenshots.
Use when preparing releases, validating cross-platform compatibility, or updating installation infrastructure. Meta-skill for maintaining AgentSys's 3-platform architecture.
Research any topic online and create learning guides. Use when user asks to 'learn about', 'research topic', 'create learning guide', 'build knowledge base', or 'study subject'.
Use when reviewing SKILL.md files for structure and trigger quality.
Use when user wants to clean AI slop from code. Use for cleanup, remove debug statements, find ghost code, repo hygiene.
Use when improving agent prompts, frontmatter, and tool restrictions.
Use when mapping code paths, entrypoints, and likely hot files before profiling.
Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.
Use when user asks to "run repo intel", "generate repo map", "analyze repo", "query hotspots", "check ownership", or "bus factor". Unified static analysis - git history, AST symbols, project metadata.
Use when checking cross-file consistency: tools vs frontmatter, agent references, duplicate rules, contradictions.
Use when reviewing hooks for safety, timeouts, and correct frontmatter.
Use when analyzing plugin structures, MCP tools, and plugin security patterns.
Authenticate to websites with human-in-the-loop browser handoff. Use when user needs to log into a website, complete 2FA, or solve CAPTCHAs for agent access.
Use when user asks to "deep review the code", "thorough code review", "multi-pass review", or when orchestrating the Phase 9 review loop. Provides review pass definitions (code quality, security, performance, test coverage), signal detection patterns, and iteration algorithms.
Use when user asks to "discover tasks", "find next task", "prioritize issues", "what should I work on", or "list open issues". Discovers and ranks tasks from GitHub, GitLab, local files, and custom sources.
Use when running performance benchmarks, establishing baselines, or validating regressions with sequential runs. Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks.
Use when generating performance hypotheses backed by git history and code evidence.
Cross-tool AI consultation. Use when user asks to 'consult gemini', 'ask codex', 'get second opinion', 'cross-check with claude', 'consult another AI', 'ask opencode', 'copilot opinion', or wants a second opinion from a different AI tool.
Structured AI debate templates and synthesis. Use when orchestrating multi-round debates between AI tools, 'debate topic', 'argue about', 'stress test idea', 'devil advocate'.
Use when the user asks about plan drift, reality check, comparing docs to code, project state analysis, roadmap alignment, implementation gaps, or needs guidance on identifying discrepancies between documented plans and actual implementation state.
Use when improving CLAUDE.md or AGENTS.md project memory files.
Use when improving documentation structure, accuracy, and RAG readiness.
Use when coordinating multiple enhancers for /enhance command. Runs analyzers in parallel and produces unified report.
Use when improving general prompts for structure, examples, and constraints.
Use when synthesizing perf findings into evidence-backed recommendations and decisions.
Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version.
Use when user asks to 'lint agent configs', 'validate skills', 'check CLAUDE.md', 'validate hooks', 'lint MCP'. Validates agent configuration files against 385 rules.
Use when user asks to 'lint agent configs', 'validate skills', 'check CLAUDE.md', 'validate hooks', 'lint MCP'. Validates agent configuration files against 385 rules across 10+ AI tools.
Use when analyzing code quality
Use when testing invalid model validation
Use when testing unreachable skills
Use when validating frontmatter keys
Use when testing argument hints
Use when testing per-client skill rules
Use when you need pull-request review help
Use when testing custom agent validation
Use when testing hooks validation
Use when testing per-client skill rules
Use when testing agent without context validation
Deploys to production
Use when deploying to production environment
Use when validating indexed arguments
Use when testing invalid agent validation
Use when testing invalid context validation
No frontmatter here.
Use when validating name-directory matching
Use when testing boolean type validation
Use when testing per-client skill rules
Use when testing per-client skill rules
Use when testing per-client skill rules
Use when testing injection limit validation
Use when validating vague skill names
Use when testing per-client skill rules
Use when testing valid hooks
Use when testing valid context and agent configuration
Use when validating windows paths
Use when testing per-client skill rules
Use when testing per-client skill rules
Use when user wants to review code
Use when testing boolean type validation
Use when testing context without agent validation
Use when testing valid model configuration
Use when validating deep references
Use when user asks to review code for quality and security issues.
Use when greeting users
Use when testing unknown tool validation
Use when looking up documentation