.claude/skills/validate-plugin/SKILL.md
Validate plugin structure and manifests against marketplace requirements
npx skillsauth add tmchow/tmc-marketplace validate-pluginInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Validate a plugin meets marketplace requirements before publishing.
/validate-plugin <plugin-name>
Or validate all plugins:
/validate-plugin --all
# Check required files exist
ls plugins/<plugin-name>/.claude-plugin/plugin.json
ls plugins/<plugin-name>/README.md
ls plugins/<plugin-name>/skills/ # At least skills/ or agents/ must exist
Required fields:
name - must match directory nameversion - semver format (e.g., "0.1.0")description - non-empty stringauthor.name - non-empty stringskills - path to skills directory (if skills exist)agents - path to agents directory (if agents exist)# Validate JSON syntax
cat plugins/<plugin-name>/.claude-plugin/plugin.json | jq .
For each plugins/<plugin-name>/skills/*/SKILL.md:
Required frontmatter:
---
name: skill-name # Required
description: ... # Required - when Claude should use this
---
Optional frontmatter:
disable-model-invocation: true # User-only skill
user-invocable: false # Claude-only skill
Check: Frontmatter must be valid YAML between --- markers
For each plugins/<plugin-name>/agents/*/AGENT.md:
Required frontmatter:
---
name: agent-name # Required
description: ... # Required - when Claude should use this agent
---
Check .claude-plugin/marketplace.json contains entry:
{
"plugins": [
{
"name": "<plugin-name>",
"source": "./plugins/<plugin-name>",
"description": "...",
"version": "..."
}
]
}
Verify no commands/ directory exists (commands merged into skills in Claude Code 2.1.3+)
Validating plugin: <plugin-name>
[PASS] Plugin structure valid
[PASS] plugin.json valid
[PASS] 2 skills validated
[WARN] No agents defined (optional)
[PASS] Marketplace entry found
[PASS] No deprecated commands
Result: VALID (5 passed, 1 warning, 0 errors)
Or if errors:
[FAIL] plugin.json missing required field: description
[FAIL] skills/my-skill/SKILL.md missing frontmatter
Result: INVALID (3 passed, 0 warnings, 2 errors)
testing
Turn requirements into a structured implementation plan with subtasks, dependencies, file paths, and test scenarios. Triggers: "create a plan", "tech planning", "write a tech plan", or has requirements ready to formalize.
data-ai
Investigate open questions through parallel research — prior art, constraints, competitive analysis. Triggers: "research this", "investigate questions", "resolve open questions", "look into this", or when a PRD has unresolved questions.
development
Review PRDs, brainstorm docs, tech plans, design docs, specs, or any planning document for issues. This skill should be used whenever the user wants feedback, critique, or a quality check on an existing planning or requirements document — even if they don't use the word "review." Common triggers include: "review the plan", "check the PRD", "critique my tech plan", "what's wrong with this plan", "poke holes in the requirements", "is this plan solid", "take a look at this spec", "give feedback on the brainstorm", or pointing to a doc file and asking if anything is off. Also triggers after writing a PRD or tech plan (to review what was just created), or when invoked by brainstorming or tech-planning skills. Do NOT trigger for code review (PRs, diffs, source files), writing/creating new plans, debugging, or reviewing non-planning documents (READMEs, CLAUDE.md, test coverage).
development
Execute a tech plan with dependency-aware batching, TDD, code review, and PR creation. Triggers: "implement the plan", "start building", "start implementing", "execute the plan".