Validate Plugin
- 652 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
validate-plugin is a Claude Code skill that validates plugin directory structure, plugin.json schema, and MCP tool references before a plugin is published or deployed.
About
validate-plugin is a ruflo skill that verifies Claude Code plugins follow the correct format after creation or modification. It accepts a plugin-path argument and performs three check classes: directory structure confirming .claude-plugin/plugin.json exists at the plugin root, plugin.json schema validation for required fields name, description, and version, and skills auto-discovery ensuring every skills/<name>/SKILL.md is a valid skill. Allowed tools include MCP claude-flow transfer_plugin-info plus Bash, Read, Glob, and Grep. Developers run validate-plugin before publishing to catch structural issues early. The skill prevents broken plugin manifests and invalid skill frontmatter from reaching registries or team installs.
- Validates agent plugins against specification and behavioral rules
- Runs automated checks on plugin structure, outputs, and edge cases
- Prevents invalid or hallucinated agent behavior from reaching production
- Integrates directly into agent development and iteration loops
- Supports 433+ active installs across indie builder workflows
Validate Plugin by the numbers
- 652 all-time installs (skills.sh)
- +6 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #582 of 2,153 Testing & QA skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill validate-pluginAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 652 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you validate a Claude Code plugin?
Automatically validate that an AI agent or plugin follows its defined rules, schema, and expected behavior before deployment.
Who is it for?
Developers authoring or modifying Claude Code plugins who need pre-publish structural and schema validation.
Skip if: Developers validating application runtime behavior or MCP server connectivity beyond plugin manifest structure.
When should I use this skill?
A Claude Code plugin was created or modified and needs structural validation before publishing.
What you get
Plugin validation report covering directory structure, plugin.json schema compliance, and valid SKILL.md skill entries.
- plugin validation report
- schema compliance confirmation
By the numbers
- Performs 3 validation check classes: directory structure, plugin.json schema, and skills auto-discovery
Files
Validate Plugin
Validate that a plugin follows the correct Claude Code plugin format.
When to use
After creating or modifying a plugin, run validation to catch structural issues before publishing.
Checks performed
1. Directory structure — .claude-plugin/plugin.json exists at plugin root 2. plugin.json schema — required fields present (name, description, version) 3. Skills auto-discovery — every skills/<name>/SKILL.md is a valid skill (Claude Code auto-discovers from directory; plugin.json MUST NOT list a skills array) 4. Commands auto-discovery — every commands/<name>.md is a valid command (auto-discovered; no commands array in plugin.json) 5. Agents auto-discovery — every agents/<name>.md is a valid agent (auto-discovered; no agents array in plugin.json) 6. No legacy arrays in plugin.json — presence of skills, commands, or agents arrays in plugin.json is a validation error (they cause Claude Code to reject the plugin) 7. SKILL.md frontmatter — each skill has name, description, and allowed-tools (no wildcards) 8. Agent frontmatter — each agent has name, description, and model 9. No files in wrong locations — skills/commands/agents not inside .claude-plugin/ 10. MCP tool references — tools in allowed-tools are valid mcp__claude-flow__* identifiers
Steps
1. Read the plugin's plugin.json and assert no skills / commands / agents arrays present 2. Glob skills/*/SKILL.md, commands/*.md, agents/*.md and validate each frontmatter 3. For each SKILL.md, verify frontmatter has required fields and allowed-tools has no wildcards 4. For each agent .md, verify frontmatter has required fields 5. Report pass/fail for each check with actionable fix suggestions
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.544k196k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.181k264kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.179k196kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.164k196k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.123k165k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.102k12.3kHow it compares
Pick validate-plugin over generic lint skills when the artifact is a Claude Code plugin bundle, not application source code.
FAQ
What does validate-plugin check?
validate-plugin checks Claude Code plugin directory structure for .claude-plugin/plugin.json, validates required plugin.json fields name, description, and version, and auto-discovers every skills/<name>/SKILL.md for valid skill frontmatter.
When should I run validate-plugin?
validate-plugin should run after creating or modifying a Claude Code plugin and before publishing. Early validation catches structural and schema issues that would break plugin installs or skill discovery in production.