Menu
Audits a local plugin directory to ensure it perfectly matches the Agent Skills and Claude Plugin Open Standards.
ADR management skill. Auto-invoked for generating architecture decisions, documenting design rationale, and maintaining the decision record log. Uses native read/write tools to scaffold and update ADR markdown files.
(Industry standard: Parallel Agent) Primary Use Case: Work that can be partitioned into independent sub-tasks running concurrently across multiple agents. Parallel multi-agent execution pattern. Use when: work can be partitioned into independent tasks that N agents can execute simultaneously across worktrees. Includes routing (sequential vs parallel), merge verification, and correction loops.
Systematically analyze agent plugins and skills to extract design patterns, architectural decisions, and reusable techniques. Trigger with "analyze this plugin", "mine patterns from", "review plugin structure", "extract learnings from", "what patterns does this plugin use", or when examining any plugin or skill collection to understand its design.
Triggers the L5 Red Team Sub-Agent to rigorously audit a plugin against the 39-point L4 pattern matrix.
Bridge plugin capabilities (commands, skills, agents, hooks, MCP) to specific agent environments (Claude Code, GitHub Copilot, Gemini, Antigravity). Use this skill when converting or installing a plugin to a target runtime.
Claude CLI sub-agent system for persona-based analysis. Use when piping large contexts to Anthropic models for security audits, architecture reviews, QA analysis, or any specialized analysis requiring a fresh model context.
| name | audit-plugin |
| description | Audits a local plugin directory to ensure it perfectly matches the Agent Skills and Claude Plugin Open Standards. |
| disable-model-invocation | false |
| allowed-tools | Bash, Read, Write |
| dependencies | ["skill:analyze-plugin"] |
This skill acts as the final CI/CD review gate for the agent ecosystem. It delegates to the agent-plugin-analyzer to execute a deep, multi-dimensional semantic scrub of a target plugin against our strict Level 4 specifications.
When instructed to audit or validate a plugin, or to verify if a skill is compliant, use the Python analyzer script. Do not use legacy basic audit scripts.
Usage:
Trigger the `agent-plugin-analyzer` skill targeting the plugin directory `--dir <path-to-plugin> --security`
(Note: Always run with the --security flag to catch P0 malware heuristics before reviewing architecture.)
Parameters:
--dir: The absolute or relative path to the root of the plugin being audited.Audit Checks Include:
skills-ref validate <path-to-skill> to definitively catch frontmatter parse errors, length constraints, and required fields (name, description).verb + -ing, e.g., analyzing-spreadsheets). Reject generic nouns. Ensure the name exactly matches the parent directory. Verify description is written strictly in the third person.CONNECTORS.md, README.md, YAML frontmatter purity. Verifies SKILL.md uses 1-level deep relative file references ONLY and is < 500 lines. Enforces that all supporting files are strictly organized into the official scripts/, references/, or assets/ directories.Remediation & Next Steps:
If the script outputs a low Maturity Score or fails the --security gate (which forces an immediate sys.exit(1)), you MUST read the generated output report and actively use your file editing tools to fix the compliance issues in the target plugin. Run the audit again until it achieves Level 3 or higher.
create-skill to fix identified gaps.create-stateful-skill to upgrade to L4 maturity.