Project Health

Runs at project start, middle, or end to eliminate permission prompts and organize your Claude Code setup. Spins up parallel sub-agents to audit permissions (leaked secrets, missing MCP servers, stale entries, legacy syntax) and context quality (oversized files, stale references, missing documentation). For new projects it detects your stack from files present and generates settings.local.json with the right presets, plus a starter CLAUDE.md. The sub-agent architecture is smart: keeps heavy filesystem scanning out of your main conversation so you get clean summaries instead of walls of diagnostic output. Also handles mid-project cleanup and end-of-session learning capture. Basically prevents the configuration drift that makes Claude Code chatty.

skills.sh installs: 1.6K
GitHub stars: 1.1K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add jezweb/claude-skills --skill project-health --agent claude-code

Installs into .claude/skills of the current project.

Files

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.