Plugin Validator
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: <example> Context: User finished creating a new plugin user: "I've created my first plugin with commands and hooks" assistant: "Great! Let me validate the plugin structure." <commentary> Plugin created, proactively validate to catch issues early. </commentary> assistant: "I'll use the plugin-validator agent to check the plugin." </example> <example> Context: User explicitly requests validation user: "Validate my plugin before I publish it" assistant: "I'll use the plugin-validator agent to perform comprehensive validation." <commentary> Explicit validation request triggers the agent. </commentary> </example> <example> Context: User modified plugin.json user: "I've updated the plugin manifest" assistant: "Let me validate the changes." <commentary> Manifest modified, validate to ensure correctness. </commentary> assistant: "I'll use the plugin-validator agent to check the manifest." </example>
By anthropics
How to install
Skill (folder)A Skill is a folder with a SKILL.md file that gives Claude extra instructions for a task.
Claude Code (project or global):
# per-project mkdir -p .claude/skills/plugin-validator # ...or for all projects mkdir -p ~/.claude/skills/plugin-validator # copy SKILL.md and any supporting files into that folder
Claude.ai / Claude Desktop:
Customize → Skills → “+” → Browse skills → Install. (Installed skills are view-only; download a copy to customise.)
Claude auto-detects skills in that folder — no restart needed.
Exact steps can vary per project — always double-check the original source. New to this? Read the full install guide →
Source
More in Agents & Workflow
View all →Dispatching Parallel Agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Subagent Driven Development
Use when executing implementation plans with independent tasks in the current session
Conversation Analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Typical triggers include the /hookify command being invoked without arguments, or the user explicitly asking to look back at the current conversation and surface mistakes that should be prevented in the future. See "When to invoke" in the agent body for worked scenarios.
Linear Server
Manage Linear issues, projects, and workflows for seamless project management integration