Use this agent when the user asks to "validate my plugin", "check plugin structure", "verify plugin is correct", "validate plugin.json", "check plugin files", or mentions plugin validation. Also trigger proactively after user creates or modifies plugin components. Examples:
How to install plugin-validator?
ajsai47/holyclaude/plugin-validator
$curl -o .claude/agents/plugin-validator.md https://raw.githubusercontent.com/ajsai47/holyclaude/HEAD/agents/plugin-validator.mdInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Install plugin-validator by running `curl -o .claude/agents/plugin-validator.md https://raw.githubusercontent.com/ajsai47/holyclaude/HEAD/agents/plugin-validator.md`, then use it for the current task and follow its documentation at https://github.com/ajsai47/holyclaude.
Related
6 picksType
- debuggerRoot-cause analysis, regression isolation, stack trace analysis, build/compilation error resolutionJul 2026
- exploreCodebase search specialist for finding files and code patternsJul 2026
- tracerEvidence-driven causal tracing with competing hypotheses, evidence for/against, uncertainty tracking, and next-probe recommendationsJul 2026
- performance-analystThe Performance Analyst profiles game performance, identifies bottlenecks, recommends optimizations, and tracks performance metrics over time. Use this agent for performance profiling, memory…May 2026
- debuggerUse this agent when encountering errors, test failures, unexpected behavior, or any issues that require root cause analysis. The agent should be invoked proactively whenever debugging is needed.Jul 2026
- explorerRead-only code exploration sub-agent. Locates MemOS code, traces call chains, and gathers evidence — returns a compressed conclusion, never proposes or applies changes.Jul 2026
