project-health
Skill1 starsChanged 7 months agoMITView on GitHub
Internal health check skill for AI DevStudio project. Checks skill count consistency across docs, detects stale sessions, and identifies cache files to clean. Not user-facing.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Fallen-leaves089/project-healththeir own version, first seen Nov 1, 2026
- davekilleen/Dextheir own version, first seen Aug 31, 2026
- shaunburdick/skillstheir own version, first seen Apr 19, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- davekilleen/Dex★ 509same name
- Fallen-leaves089/project-health★ 1same name
- shaunburdick/skills★ 1same 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 repository206 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skill-validatorSkill
- accessibilitySkill
- agent-debugSkill
- agent-evaluateSkill
- ai-governanceSkill
- ai-system-reviewSkill
- api-docs-generateSkill
- api-examplesSkill
- api-mockSkill
- api-test-generateSkill
- api-validateSkill
- architecture-diagramSkill
- ask-mattSkill
- assumption-mapSkill
- boilerplateSkill
- brainstormSkill
- branch-finishSkill
- briefingSkill
- browser-testing-with-devtoolsSkill
- bundle-analyzeSkill
- cache-strategySkill
- canarySkill
- carefulSkill
- cavemanSkill
- changelog-autoSkill
- chaos-testSkill
- ci-setupSkill
- ci-sweepSkill
- cleanprojectSkill
- click-path-auditSkill
- codebase-designSkill
- code-review-checklistSkill
- code-tourSkill
- commitSkill
- completion-verifySkill
- complexity-reduceSkill
- component-librarySkill
- config-cleanupSkill
- config-generateSkill
- conflict-resolveSkill
- container-optimizeSkill
- context-budgetSkill
- context-engineeringSkill
- context-restoreSkill
- context-saveSkill
- continuous-learningSkill
- contributingSkill
- cost-trackSkill
- councilSkill
- create-todosSkill
- cross-modal-reviewSkill
- database-connectSkill
- db-diagramSkill
- ddd-modelSkill
- debug-root-causeSkill
- debug-sessionSkill
- debug-systematicSkill
- decision-logSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 16
Verify that the skill count (99) is consistent across all documentation files:
- Very specific: line 57
Check that docs/ modification dates are recent relative to skills/ changes:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Project Health Check Skill
Internal skill used by the session-daily command. Checks the health of the AI DevStudio project itself.
Checks
1. Skill Count Consistency
Verify that the skill count (99) is consistent across all documentation files:
Bash: ls skills/ | wc -lThen check these files reference the correct count:
CLAUDE.md: grep for skill countAGENTS.md: grep for skill countREADME.md: grep for skill count
Report any inconsistencies found.
2. Stale Session Files
Bash: find .claude/sessions/ -name "*.json" -mtime +30 2>/dev/null | wc -lReport count of session files older than 30 days. Suggest running /cleanproject if count > 5.
3. Cache Size
Bash: du -sh .claude/cache/ 2>/dev/null || echo "No cache directory"Report cache size. Suggest cleanup if > 50MB.
4. Install Script Sync
Bash: python3 -c "import ast, sys; ast.parse(open('install.py').read()); print('install.py: OK')" 2>&1
Bash: bash -n install.sh 2>&1 && echo "install.sh: OK"Report any syntax errors.
5. Documentation Currency
Check that docs/ modification dates are recent relative to skills/ changes:
Bash: git log --oneline -1 -- skills/ docs/Output Format
Project Health: <OK|ISSUES FOUND>
Skill count: N (consistent: yes/no)
Stale sessions: N files
Cache: <size>
Install scripts: OK / <error>
Docs currency: OK / <last updated>Token Optimization
Expected range: 200-500 tokens
Patterns used: Bash-based queries, early exit if all checks pass
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.

