Improve my agent setup

A setup-wide health check for someone doing agentic development. It measures what can be measured (skills, memory, config, tools, git, transcripts), interviews the user about the parts that can't be measured (ethics, focus, habits), scores each theme, writes a report to .claude/scratchpads/, and then offers to fix the weak spots one at a time.

The point is not a vanity score. It is to find the two or three changes that would most improve how this person works with agents, and then actually make them. A setup rots the same way a codebase does: skills pile up unused, memory bloats with things the model already knows, tools go redundant, and nobody prunes. This skill is the prune.

Guiding stance, echoed across this marketplace: every installed tool, skill, and line of memory competes for the agent's attention and context. More is not better. The best setup is the smallest one that does the job, owned and tuned by the person using it.

How to use this skill

1. Pick the audit mode from $ARGUMENTS (or the user's phrasing); it sets depth, interview cadence, and tone
2. Run the scan script at the breadth that mode implies, to gather deterministic facts
3. Read references/dimensions.md for the full rubric; it defines each theme, what good looks like, and the signals to read from the scan
4. Interpret the facts theme by theme; do not just echo the JSON
5. Interview the user for what the scan can't see; how often you interview depends on the mode
6. For the context-files theme, apply references/context-review.md (the absorbed context audit)
7. Write the report to .claude/scratchpads/setup-audit-<YYYY-MM-DD>.md using the template below
8. Walk the top fixes with the user and offer to apply them, and strongly advise a recurring re-audit; see references/fix-catalog.md