Project health check
Skill claude-world/director-mode-lite/skills/project-health-check
Audit project health across 7 dimensions (documentation, test coverage, security, code quality, dependencies, database, build/deploy) producing a scored report with prioritized fixes. Use for periodic checkups, before releases, or when the user runs /project-health-check.From its SKILL.md
npx -y skills add claude-world/director-mode-lite --skill project-health-checkAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.6 KB, 380 tokens by cl100k_base, as published. Nobody here has run it
Project Health Check
Comprehensive 7-point audit for project health.
7-Point Audit
1. Documentation
- README is accurate
- API docs exist
- Code comments explain "why"
2. Test Coverage
- Coverage > 80%
- Critical paths tested
- Edge cases covered
3. Security
- No secrets in code
- No vulnerable dependencies
- Input validation exists
4. Code Quality
- Linting passes
- No large files (> 500 lines)
- Consistent naming
5. Dependencies
- No outdated majors
- No unused deps
- Compatible licenses
6. Database
- Schema documented
- Migrations versioned
- Indexes documented
7. Build/Deploy
- Build succeeds
- CI/CD exists
- Env vars documented
Health Score Template
# Project Health Report - [Date]
## Overall Score: [X]/100
| Area | Score | Status |
|------|-------|--------|
| Documentation | /15 | |
| Test Coverage | /15 | |
| Security | /20 | |
| Code Quality | /15 | |
| Dependencies | /15 | |
| Database | /10 | |
| Build/Deploy | /10 | |
### Critical Issues
1. [Fix immediately]
### Warnings
1. [Fix this week]
### Suggestions
1. [Consider]
Frequency
| Check | When |
|---|---|
| Quick | Weekly |
| Standard | Bi-weekly |
| Full | Monthly |
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most docs writing skills give in 380 tokens
Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06
- Use third-person for skill descriptionsin 54 of 1951, across 35 files
- Start descriptions with Use whenin 43 of 1951, across 29 files
- Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
- Use active voicein 40 of 1951, across 36 files
- Map file responsibilities before defining tasksin 36 of 1951, across 29 files
- Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
- Ask one question at a timein 35 of 1951
- Offer execution options after saving the planin 33 of 1951, across 24 files
- Include complete code in every stepin 33 of 1951, across 27 files
- Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
- Announce the skill usage at the startin 30 of 1951
- Verify agent compliance after adding the skillin 29 of 1951, across 17 files
Said here and by no other author read
- Audit documentation accuracy
- Verify test coverage exceeds eighty percent
- Check for secrets in code
- Ensure linting passes
- Identify outdated dependencies
- Document database schema
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.