project-health
All-in-one project configuration and health management. Sets up new projects (settings.local.json, CLAUDE.md, .gitignore), audits existing projects (permissions, context quality, MCP coverage, leaked secrets, stale docs), tidies accumulated cruft, captures session learnings, and adds permission presets. Uses sub-agents for heavy analysis to keep main context clean. Trigger with 'project health', 'check project', 'setup project', 'kickoff', 'bootstrap', 'tidy permissions', 'clean settings', 'capture learnings', 'audit context', 'add python permissions', or 'init project'.
npx skills add jezweb/claude-skills --skill project-health --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Project Health One skill for everything about your project's Claude Code configuration. Run it at the start, middle, or end of a project — it figures out what's needed. **Goal**: Zero permission prompts, well-organised context files, no cruft. ## When to Use | You say... | What happens | |-----------|-------------| | "project health" / "check project" | Full audit: permissions + context + docs | | "setup project" / "kickoff" / "bootstrap" | New project setup from scratch | | "tidy permissions" / "clean settings" | Fix permissions file only | | "capture learnings" / "update CLAUDE.md" | Save session discoveries | | "add python" / "add docker permissions" | Add a preset to existing settings | | "audit context" / "audit memory" | Context-focused audit only | ## Architecture: Sub-Agents **Heavy analysis runs in sub-agents** to keep the main conversation clean. The main agent orchestrates; sub-agents do the scanning and return summaries. ### Agent 1: Permission Auditor Launched with `Task(subagent_type: "general-purpose")`. Prompt: ``` Read .claude/settings.local.json. **Discover connected MCP servers**: Use ToolSearch (search "mcp") and extract unique server prefixes from tool names
- When to Use
- Architecture: Sub-Agents
- Agent 1: Permission Auditor
- Agent 2: Context Auditor
- Parallel Execution
- Mode 1: Full Health Check
- Steps
- Mode 2: New Project Setup
- Mode 3: Tidy Permissions
- Mode 4: Capture Learnings
- Mode 5: Add Preset
- Mode 6: Restructure Context
- Size Targets
- Permission Syntax Quick Reference
What does the project-health skill do?
All-in-one project configuration and health management. Sets up new projects (settings.local.json, CLAUDE.md, .gitignore), audits existing projects (permissions, context quality, MCP coverage, leaked secrets, stale docs), tidies accumulated cruft, captures session learnings, and adds permission presets. Uses sub-agents for heavy analysis to keep main context clean. Trigger with 'project health', 'check project', 'setup project', 'kickoff', 'bootstrap', 'tidy permissions', 'clean settings', 'capture learnings', 'audit context', 'add python permissions', or 'init project'.
How do I install it?
Run `npx skills add jezweb/claude-skills --skill project-health --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jezweb/claude-skills, a repository with 954 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.