project-health

1# Project Health
2 
3One 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.
4 
5**Goal**: Zero permission prompts, well-organised context files, no cruft.
6 
7## When to Use
8 
9| You say... | What happens |
10|-----------|-------------|
11| "project health" / "check project" | Full audit: permissions + context + docs |
12| "setup project" / "kickoff" / "bootstrap" | New project setup from scratch |
13| "tidy permissions" / "clean settings" | Fix permissions file only |
14| "capture learnings" / "update CLAUDE.md" | Save session discoveries |
15| "add python" / "add docker permissions" | Add a preset to existing settings |
16| "audit context" / "audit memory" | Context-focused audit only |
17 
18## Architecture: Sub-Agents
19 
20**Heavy analysis runs in sub-agents** to keep the main conversation clean. The main agent orchestrates; sub-agents do the scanning and return summaries.
21 
22### Agent 1: Permission Auditor
23 
24Launched with `Task(subagent_type: "general-purpose")`. Prompt:
25 
26```
27Read .claude/settings.local.json.
28 
29**Discover connected MCP servers**: Use ToolSearch (search "mcp") and extract unique
30server prefixes from tool names (e.g. mcp__vault__secret_list → vault).
31 
32**Discover installed skills**: Use the Skill tool or ToolSearch to list available skills.
33For each skill that has scripts/ in its directory, note what Bash patterns it needs
34…