auditlisted

## What this skill does Runs the **Four Cs Audit** on the current Claude Code project. Reads (never writes) the project's operating manual, memory, skills, agents, MCPs, decisions, and references. Scores each of the Four Cs out of 25. Surfaces strengths and the top 3 leverage-weighted gaps with concrete next-step commands. **Scope is structural — "is the AIOS built right?"** It is NOT a capability planner. Capability gaps ("you could build a daily brief if you connected calendar") belong to `/level-up`. The audit answers: are the files, folders, registries, and connections in good shape? First run is the baseline. Re-run weekly to watch the score climb. That's the compounding hook. ## Today's context - **Date:** !`date +%Y-%m-%d` - **Project root:** the current working directory ## The Four Cs (scored 25 each = 100 total) | Layer | Test | |---|---| | **Context** | Knows the business — identity, team, voice, decisions, references | | **Connections** | Reaches the user's stuff — MCPs, integrations, data sources | | **Capabilities** | Knows how to do work — skills + agents | | **Cadence** | Runs without being asked — schedules, hooks, recurring rituals | ## Execution ### Step 1: Discover the project shape The audit looks for **patterns and intent**, not exact paths. File names vary. Use Glob and Read to check: **Operating manual:** `CLAUDE.md` (root), `CLAUDE.local.md` (gitignored). **Memory:** `MEMORY.md` (root), `~/.claude/projects/<id>/memory/MEMORY.md`, or `memory