Help us improve
Share bugs, ideas, or general feedback.
From jeremy-plugin-tool
Validates Claude Code plugin structure, JSON schemas, frontmatter format, security compliance, and marketplace catalog consistency. Triggers on 'validate plugin', 'check plugin', or 'verify' to run CI checks before commit.
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/jeremy-plugin-tool:plugin-validatorThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Validates Claude Code plugin structure, JSON schemas, frontmatter format, security compliance, and marketplace catalog consistency. Runs the same checks as the CI pipeline to catch issues before committing.
Validates Claude Code plugin directories against Anthropic spec via structural checks (plugin.json, files, permissions) and content grading (SKILL.md, commands). Use for building, auditing, or marketplace prep.
Audits Claude Code plugins for security vulnerabilities, best practices, CLAUDE.md compliance, marketplace readiness, git hygiene, performance, and UX. Produces scored reports using scans for secrets, dangerous commands, and structure validation.
Validates Claude Code plugins for compliance with official guidelines including plugin.json manifest, directory structure, and formats for agents/skills/commands to prevent installation failures.
Share bugs, ideas, or general feedback.
Validates Claude Code plugin structure, JSON schemas, frontmatter format, security compliance, and marketplace catalog consistency. Runs the same checks as the CI pipeline to catch issues before committing.
.claude-plugin/marketplace.extended.jsonjq installed for JSON validation (jq empty <file>)grep and find available on PATH for pattern scanning./scripts/validate-all-plugins.sh available at the repository root.claude-plugin/ subdirectory.${CLAUDE_SKILL_DIR}/references/validation-checks.md):
.claude-plugin/plugin.json present and valid JSON.README.md present and non-empty.LICENSE file present.commands/, agents/, skills/, hooks/, or mcp/).plugin.json schema:
name (kebab-case), version (semver x.y.z), description, author.name, author.email, license, keywords (array, minimum 2).name, version, description, author, repository, homepage, license, keywords).commands/*.md): require name, description, model (one of sonnet, opus, haiku).agents/*.md): require name, description, model.skills/*/SKILL.md): require name, description; allowed-tools optional but validated against the allowed tools list if present.${CLAUDE_SKILL_DIR}/references/validation-checks.md for the complete structure diagram)..sh files and verify they have execute permission. Report any that lack it with a fix command.marketplace.extended.json.plugin.json and the catalog entry.${CLAUDE_PLUGIN_ROOT} instead of hardcoded absolute paths (/home/, /Users/).${CLAUDE_SKILL_DIR}/references/validation-report-format.md.A structured validation report containing:
| Error | Cause | Solution |
|---|---|---|
| Plugin directory not found | Incorrect path provided | Verify path matches plugins/[category]/[name]/ and the directory exists |
jq parse error on JSON | Malformed JSON in plugin.json or catalog | Run jq empty <file> to locate the syntax error line |
| Frontmatter parse failure | Missing --- delimiters or invalid YAML | Ensure YAML frontmatter is enclosed in --- lines with valid key-value pairs |
| Version mismatch | plugin.json and marketplace.extended.json carry different versions | Update the stale version to match; run pnpm run sync-marketplace |
| Scripts not executable | .sh files missing execute permission | Run chmod +x <script> for each flagged file |
| Disallowed fields in plugin.json | Extra fields beyond the allowed set | Remove disallowed fields; only name, version, description, author, repository, homepage, license, keywords are permitted |
Validate a specific plugin:
Trigger: "Validate the skills-powerkit plugin."
Process: Run all 10 validation checks against plugins/community/skills-powerkit/. Identify 2 failures (script permissions, version mismatch). Provide fix commands: chmod +x scripts/*.sh and version update instruction. Report overall: FAILED (see ${CLAUDE_SKILL_DIR}/references/examples.md).
Pre-commit readiness check: Trigger: "Check if my plugin is ready to commit." Process: Detect the plugin from working directory context. Run comprehensive validation including marketplace compliance. Report PASSED or list blocking issues with fixes.
Debug CI failures:
Trigger: "Why is my plugin failing CI?"
Process: Run the same validation checks that CI executes (validate-all-plugins.sh). Identify the exact failure (e.g., disallowed field in plugin.json). Provide the fix command and verify the fix resolves the issue.
${CLAUDE_SKILL_DIR}/references/validation-checks.md -- complete list of all 10 validation categories with specific checks${CLAUDE_SKILL_DIR}/references/validation-report-format.md -- report template with pass/fail formatting${CLAUDE_SKILL_DIR}/references/examples.md -- validation scenario walkthroughs${CLAUDE_SKILL_DIR}/references/errors.md -- error handling patterns