skill-health-check
Skill192 starsChanged 42 days agoMITView on GitHub
Validate skill quality against routing, progressive loading, and verification criteria. Use when: auditing skills, checking skill health, reviewing skill design. Not for: code review (use codex-code-review) or doc review (use doc-review). Output: health report with per-skill ratings + Gate.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- bordenet/superpowers-plustheir own version, first seen Nov 13, 2026
- sd0xdev/sd0x-harnessword for word, first seen Oct 6, 2026
- u9401066/template-is-all-you-needtheir own version, first seen Mar 6, 2026
Other versions3 projects use a version of this.
Word for word · 1
- sd0xdev/sd0x-harness★ 192100% same
Edited · 0
None found.
Wrote their own version · 2
- bordenet/superpowers-plus★ 8same name
- u9401066/template-is-all-you-need★ 3same name
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 repository102 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adrSkill
- agentctl-setupSkill
- architectureSkill
- askSkill
- best-practicesSkill
- bug-fixSkill
- bump-versionSkill
- check-coverageSkill
- claude-healthSkill
- code-exploreSkill
- code-investigateSkill
- codex-architectSkill
- codex-brainstormSkill
- codex-cli-reviewSkill
- codex-code-reviewSkill
- codex-explainSkill
- codex-implementSkill
- codex-review-branchSkill
- codex-review-docSkill
- codex-review-fastSkill
- codex-reviewSkill
- codex-securitySkill
- codex-setupSkill
- codex-test-genSkill
- codex-test-reviewSkill
- contract-decodeSkill
- create-prSkill
- create-requestSkill
- de-ai-flavorSkill
- debugSkill
- deep-analyzeSkill
- deep-exploreSkill
- deep-researchSkill
- dep-auditSkill
- deploy-flowSkill
- dev-security-auditSkill
- doc-refactorSkill
- doc-reviewSkill
- epic-mergeSkill
- feasibility-studySkill
- feature-devSkill
- feature-verifySkill
- fp-briefSkill
- generate-runnerSkill
- gh-stackSkill
- git-investigateSkill
- git-profileSkill
- install-hooksSkill
- install-rulesSkill
- install-scriptsSkill
- issue-analyzeSkill
- jiraSkill
- load-pr-reviewSkill
- merge-prepSkill
- necessity-auditSkill
- next-stepSkill
- obsidian-cliSkill
- op-sessionSkill
- orchestrateSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Document review (use /codex-review-doc)
- Distinctive: line 75
Read flagged skills and evaluate:
- Distinctive: line 84
Only run Step 2 when user explicitly requests deep audit.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill Health Check
Trigger
- Keywords: skill health, skill audit, skill lint, check skills, skill quality, validate skills
When NOT to Use
- Code review (use
/codex-review-fast) - Document review (use
/codex-review-doc) - Creating new skills (use
skill-creatorplugin, external) - .claude directory structure check (use
/claude-health)
Core Principle
Skills are on-demand context packages. Their value comes from routing precision (right skill triggers at right time) and context efficiency (minimum tokens for maximum capability). A poorly routed skill wastes context on every mismatch; a well-routed skill transforms a generalist into a specialist at exactly the right moment.
Workflow
Run automated lint → Review manual dimensions → Produce integrated report → GateStep 1: Automated Lint
node skills/skill-health-check/scripts/skill-lint.js --fix-hintScript I/O contract:
| Parameter | Description |
--skills-dir <path> | Skills directory (default: ./skills) |
--agents-dir <path> | Agents directory (default: ./agents) |
--json | Output JSON instead of markdown |
--fix-hint | Include fix suggestions |
| Exit 0 | All pass |
| Exit 1 | Warnings only (P2) |
| Exit 2 | Errors found (P0/P1) |
Per-skill checks (11 items):
| # | Check | Severity | Criteria |
| 1 | Frontmatter exists | P0 | name + description required |
| 2 | Routing signature | P1 | Description has at least 2 of 3 routing cues (Use/Avoid/Output); 0 cues = P1, 1 cue = P2 |
| 3 | When NOT section | P1 | Body has "When NOT to Use" heading |
| 4 | Output section | P2 | Body defines expected deliverable |
| 5 | Verification section | P2 | Body has verification checklist |
| 6 | References routing | P2 | Each reference file mentioned in body |
| 7 | Scripts contract | P2 | Each script filename referenced in SKILL.md body |
| 8 | Line count | P2 | Warning >150, flag >250 |
| 9 | Agent entitlement | P2 | Body describes Agent() dispatch but allowed-tools lacks Agent |
| 10 | Task entitlement | P2 | Body describes Task() dispatch but allowed-tools lacks Task |
| 11 | Cross-skill ref path | P1 | Bare ref paths not found locally but existing in another skill → must use @skills/<parent>/ prefix |
Cross-skill checks (3 items):
| # | Check | Severity | Criteria |
| 12 | Description overlap | P2 | Jaccard similarity >60% flagged |
| 13 | Agent ref validity | P1 | subagent_type references in skills must exist in agents/ |
| 14 | Agent tools syntax | P2 | Agent .md tools field uses canonical format (ToolName or Bash(<prefix>:*)) |
Step 2: Manual Review (when comprehensive audit requested)
Read flagged skills and evaluate:
| Dimension | Question | Rating |
| Why > What | Does skill explain underlying principles, not just steps? | ⭐1-5 |
| Scope fitness | Is the skill focused? Could it be split? | ⭐1-5 |
| Progressive loading | Is heavy content in references/, not inline? | ⭐1-5 |
| Routing precision | Would a user's request unambiguously trigger this skill? | ⭐1-5 |
Only run Step 2 when user explicitly requests deep audit. Default: Step 1 only.
Output
# Skill Health Check Report
## Summary
| Metric | Value |
|--------|-------|
| Skills scanned | N |
| Checks passed | N |
| P0 (Must Fix) | N |
| P1 (Should Fix) | N |
| P2 (Suggestion) | N |
## Per-Skill Results
| Skill | Routing | When-NOT | Output | Verification | Refs | AgEnt | TskEnt | Lines | Status |
|-------|---------|----------|--------|--------------|------|-------|--------|-------|--------|
| name | ✅/🟡/⚪ | ... | ... | ... | ... | ✅/⚪ | ✅/⚪ | N | ✅/🟡/⚪/🔴 |
## P0 (Must Fix)
- **skill-name**: Issue → Fix recommendation
## P1 (Should Fix)
- **skill-name**: Issue → Fix recommendation
## P2 (Suggestion)
- **skill-name**: Issue → Fix recommendation
## Gate: ✅ All Pass / ⛔ N issues need fixingVerification
- Automated lint executed (exit code checked)
- All P0/P1 findings have fix recommendations
- Per-skill table includes all scanned skills
- Gate sentinel present for hook parsing
References
references/routing-signature-guide.md— How to write effective routing signatures (read when fixing P1 routing issues)
Examples
Input: /skill-health-check
Action: Run skill-lint.js → Output markdown report + Gate
Input: /skill-health-check --deep
Action: Run skill-lint.js → Manual review of flagged skills → Integrated report
Input: Are my skills well-designed?
Action: Trigger health check → Report + improvement suggestionsDoes 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.

