← ClaudeAtlas

ecosystem-auditlisted

ALWAYS use this skill when the user asks any question about their Claude Code setup, installed skills, memory system, handoffs, worktrees, or ~/.claude directory health. This is the go-to skill for introspection of the Claude Code environment itself. Specifically trigger on: (1) Skill inventory questions — "how many skills do I have", "which skills am I using", "what's dormant", "which skills can I uninstall", "are there overlapping skills"; (2) Cleanup and hygiene requests — "clean up my ecosystem", "audit my setup", "~/.claude feels bloated", "monthly hygiene check", "what needs cleanup", "stale worktrees", "orphaned handoff prompts"; (3) Diagnostic symptoms — "my memory system isn't working", "lessons aren't being picked up", "skill is not triggering", "claude keeps forgetting", "why is the wrong skill firing", "duplicate skill confusion"; (4) Health dashboards — "show me a health dashboard", "utilization across skills/memory/handoffs", "ecosystem health report"; (5) Any mention of auditing persistent arti
wan-huiyan/claude-ecosystem-hygiene · ★ 0 · Data & Documents · score 73
Install: claude install-skill wan-huiyan/claude-ecosystem-hygiene
# Ecosystem Audit A comprehensive audit of the entire `~/.claude/` ecosystem that scans 9 categories of persistent artifacts, scores each on a health scale, and produces an interactive HTML dashboard with prioritized cleanup recommendations. ## When to Use - User wants to know what skills are installed and which are actually used - User wants to clean up their Claude Code environment - User asks about ecosystem health, dormant artifacts, or storage bloat - Monthly hygiene check (recommend running every 30 days) - Before/after installing a batch of new skills - When memory-hygiene or schliff:doctor findings suggest broader issues ## Architecture This skill orchestrates parallel subagents for speed. The audit runs in 3 phases: ``` Phase 1: Scan (parallel subagents) ├── Skills: parse JSONL logs for invocations, classify by domain ├── Memory: check all project dirs, apply memory-hygiene thresholds ├── Handoffs: count, classify lifecycle state, find orphans └── ADRs + Docs: read status fields, check links, classify Phase 2: Score (sequential) ├── Calculate health % per category ├── Apply lifecycle scoring for worktrees ├── Cross-reference with memory-hygiene thresholds └── Generate prioritized recommendations (P0/P1/P2) Phase 3: Report (write files) ├── Markdown summary → docs/handoffs/ecosystem_audit_report.md └── Interactive HTML → docs/handoffs/ecosystem_audit_report.html ``` ## Phase 1: Scan Launch 4 parallel subagents, each responsible for one sc