project-health

# 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 (e.g. mcp__vault__secret_list → vault). **Discover installed skills**: Use the Skill tool or ToolSearch to list available skills. For each skill that has scripts/ in its directory, note what Bash patterns it needs (python3, env var prefixes like GEMINI_API_KEY=*, etc.). Check the SKILL.md...