Claude Audit Skill

Analyze all .claude/ configuration files to find optimization opportunities.

Workflow

Scan files: Find all .md files in .claude/ directory (rules/, commands/, agents/, skills/)
Analyze each file for:
- Redundant instructions: Rules that repeat across multiple files
- Verbose phrasing: Overly wordy explanations that can be concise
- Move to memory candidates: Content rarely needed in context but referenced
Present findings in a structured format
Ask user: Which optimizations to implement?

Analysis Criteria

Redundant Instructions

Same rule mentioned in multiple files
Overlapping scope between rules and agents/skills
Duplicate workflow descriptions

Verbose Phrasing

Long paragraphs that can be shortened
Redundant examples
Over-explanation of obvious concepts

Memory Candidates

Static reference material rarely changing
Detailed examples not needed in every session
Background context that can be loaded on-demand

Output Format

# Claude Audit Report

## Files Analyzed
- [file count] files reviewed

## Findings

### Redundant Instructions
| File | Issue | Recommendation |
|------|-------|-----------------|
| file.md | Description | Action |

### Verbose Phrasing
| File | Section | Suggestion |
|------|---------|------------|
| file.md | section | concise version |

### Memory Candidates
| File | Content | Rationale |
|------|---------|-----------|
| file.md | section | why to move |

## Summary
- X redundant rules
- Y verbose sections
- Z candidates for memory

## Action Items
[ ] Implement specific fix

Present findings to the user and ask which to implement

Boundaries

Focus on Claude configuration quality, duplication, and token efficiency.
Do not rewrite unrelated product code or project business logic.
Do not auto-apply configuration changes without the owner's confirmation.

When NOT to Use

Editing product/application code instead of auditing .claude instructions
Running broad refactors without first producing an audit report
Applying configuration deletions/merges without owner approval

Escalation Rules

Pause and ask the owner before:

deleting or heavily rewriting existing rules instead of proposing targeted reductions
merging files in ways that change the project's instruction hierarchy
making assumptions about which rules should move to memory versus stay in active context

Final Output Contract (MANDATORY)

Every use of this skill should end with:

Skill Fit - why a Claude configuration audit was needed
Primary Deliverable - findings summary and recommended actions
Execution Evidence - files analyzed and overlap patterns discovered
Risks / Open Questions - ambiguity, tradeoffs, or scope concerns
Next Action - the specific optimization step to review or implement next