validate
Skill3 starsChanged 48 days agoMITView on GitHub
Validate all plugins for structure, manifests, references, shell scripts, and markdown conventions
- Installs packages
69 other projects use a version of this.
Adopted by
Most recently taken up by
- lenhatthanh20/natamuxtheir own version, first seen Nov 16, 2026
- aya-taleb/mimic-skillstheir own version, first seen Nov 15, 2026
- intelligentcode-ai/skillstheir own version, first seen Nov 15, 2026
- aya-taleb/entrepreneur-skillstheir own version, first seen Nov 15, 2026
- RemiPelloux/kill-my-ideatheir own version, first seen Nov 15, 2026
- SireJeff/k0ntexttheir own version, first seen Nov 15, 2026
Used with
Projects with it also use policy-init, create and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
open-coder-aiSkillpolicy-init
Create conformant Chock policy from request. args(request, target_path,
Also in 3 projects that use this
MicrosoftSkillcreate
Also in 4 projects that use this
HermeticOrmusSkillclose
End-of-session ritual. Captures session state, updates auto-memory, writes a session summary, then exits the session cleanly.
Also in 4 projects that use this
Hugging FaceSkillsprint
Work on a batch of GitHub issues in parallel using Agent Teams. Creates one worktree per issue with TDD enforcement, coordinates via a lead agent, then produces stacked PRs.
Also in 4 projects that use this
qtzx06Skilleval
Evaluate trained YOLO model accuracy with mAP metrics and per-class error analysis. Identifies failure cases for targeted improvement. Use after training.
Also in 4 projects that use this
csiddhant796-blipSkillboard
Read, write, and browse the AgentHub message board for agent coordination.
Also in 3 projects that use this
Other versions69 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 69
- iPlug2/iPlug2★ 2.4ksame name
- sirius-db/sirius★ 1.1ksame name
- H-mmer/pentest-agents★ 815same name
- nudgebee/nudgebee★ 525same name
- microsoft/skills-for-copilot-studio★ 486same name
- boshu2/agentops★ 454same name
- scaccogatto/okf-skills★ 444same name
- whawkinsiv/solo-founder-skills★ 260same name
- whawkinsiv/claude-code-skills★ 258same name
- OffchainLabs/arbitrum-docs★ 252same name
59 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- doc-auditSkill
- feature-doneSkill
- progressive-disclosureSkill
- release-docsSkill
- test-plugins-locallySkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 59 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Run all quality checks across every plugin in the marketplace.
- Very specific: line 12
Read .claude-plugin/marketplace.json to get the list of registered plugins.
- Very specific: line 50
Run shellcheck on all .sh files across all plugins and .claude/hooks/.
- Very specific: line 52
If shellcheck is not installed:
- Distinctive: line 54
Do NOT report as FAIL
- Distinctive: line 56
If installed, report any ShellCheck errors as WARN (not FAIL — scripts may have intentional suppressions).
- Distinctive: line 87
If any category is FAIL, overall is FAIL.
- Distinctive: line 91
Run all checks — don't stop at the first failure
“Common” is measured: kept by at least 6 in 10 of the 59 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/validate — Plugin Validation
Run all quality checks across every plugin in the marketplace. Reports PASS/WARN/FAIL per category.
Step 1: Identify Plugins
Read .claude-plugin/marketplace.json to get the list of registered plugins. For each plugin, extract the source path.
Step 2: Structure Check
For each plugin directory, verify:
.claude-plugin/plugin.jsonexistsREADME.mdexists- At least one of
skills/,commands/,agents/exists
Report missing items as FAIL.
Step 3: Manifest Validation
For each plugin.json, verify:
- Valid JSON syntax
- Required fields present:
name,version,description,author,license,keywords namematches the plugin directory name
Report missing/invalid fields as FAIL.
Step 4: Version Sync
Compare each plugin's plugin.json version with its marketplace.json entry:
- Versions must match exactly
- Both must be valid semver
Report mismatches as FAIL.
Step 5: Reference Integrity
For each skills/*/SKILL.md, check if the skill directory has a references/ subdirectory. If it does, verify every .md file in it exists and is non-empty.
For each agents/*.md, check for any script references (paths to .sh files). Verify those scripts exist.
Report broken references as FAIL.
Step 6: ShellCheck
Run shellcheck on all .sh files across all plugins and .claude/hooks/.
If shellcheck is not installed:
- Report as WARN: "ShellCheck not installed — skipping script validation. Install with: brew install shellcheck"
- Do NOT report as FAIL
If installed, report any ShellCheck errors as WARN (not FAIL — scripts may have intentional suppressions).
Step 7: SKILL.md Section Check
For each SKILL.md, verify:
- H1 title exists (line begins with
#followed by descriptive text) - H1 does NOT use the
/<plugin>:<skill>slash form — per.claude/rules/skills-authoring.md, the slash is derived from frontmattername, not the H1 - Has a
## Key Rulessection (or similar closing constraints section)
Report violations as WARN.
Step 8: Report
Present a summary table:
Plugin Validation Report
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Category Status
─────────────────────────────
Structure PASS | FAIL (details)
Manifests PASS | FAIL (details)
Version Sync PASS | FAIL (details)
Reference Integrity PASS | FAIL (details)
ShellCheck PASS | WARN | SKIP
SKILL.md Sections PASS | WARN (details)
Overall: PASS | FAILIf any category is FAIL, overall is FAIL. If only WARNs, overall is PASS with warnings.
Key Rules
- Run all checks — don't stop at the first failure
- Distinguish FAIL (structural violation) from WARN (advisory)
- ShellCheck not installed is a WARN, not a FAIL
- Report per-plugin details for any failures, not just aggregate counts
- A partially-created plugin (in progress) should get WARN for missing structure, not FAIL
Next: documentation audit
Structure is only half the picture. After /validate passes, run /doc-audit to verify the
human docs match what's shipped (per-plugin Skills sections, root command index, manifest/desc
sync, docs-site parity).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

