Agent skill · writing content · anthropics
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project memory optimization".
Why this skill is useful
Adds a structured auditing and improvement process for CLAUDE.md files, which includes specific quality assessment criteria and targeted updates that the AI wouldn't generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 33,212 stars on the source repository.
What this skill does
CLAUDE.md Improver Audit, evaluate, and improve CLAUDE.md files across a codebase to ensure Claude Code has optimal project context. This skill can write to CLAUDE.md files. After presenting a quality report and getting user approval, it updates CLAUDE.md files with targeted improvements. Workflow Phase 1: Discovery Find all CLAUDE.md files in the repository: File Types & Locations: Type Location Purpose ------ ---------- --------- Project root ./CLAUDE.md Primary project context (checked into git, shared with team) Local overrides ./.claude.local.md Personal/local settings (gitignored, not shared) Global defaults ~/.claude/CLAUDE.md User-wide defaults across all projects Package-specific ./packages//CLAUDE.md Module-level context in monorepos Subdirectory Any nested location Feature/domain-specific context Note: Claude auto-discovers CLAUDE.md files in parent directories, making monorepo setups work automatically. Phase 2: Quality Assessment For each CLAUDE.md file, evaluate against quality criteria. See references/quality-criteria.md for detailed rubrics. Quick Assessment Checklist: Criterion Weight Check ----------- -------- ------- Commands/workflows documented High Are build/test/deploy commands present? Architecture clarity High Can Claude understand the codebase structure? Non-obvious patterns Medium Are gotchas and quirks documented? Conciseness Medium No verbose explanations or obvious info? Currency High Does it reflect current codebase state? Actionability High Are instructions executable, not vague? Quality Scores: A (90-100): Comprehensive, current, actionable B (70-89): Good coverage, minor gaps C (50-69): Basic info, missing key sections D (30-49): Sparse or outdated F (0-29): Missing or severely outdated Phase 3: Quality Report Output ALWAYS output the quality report BEFORE making any updates. Format: Phase 4: Targeted Updates After outputting the quality report, ask user for confirmation before updating. Update Guidelines (Critical): 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills anthropics/claude-md-improver