ecosystem-audit

Audit Claude Code ecosystems by scanning skills, memory, handoffs, ADRs, and worktrees into a scored HTML report.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/wan-huiyan/claude-ecosystem-hygiene --skill ecosystem-audit-wan-huiyan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecosystem-audit
Source: https://github.com/wan-huiyan/claude-ecosystem-hygiene/tree/main/plugins/ecosystem-audit
Command: npx skills add https://github.com/wan-huiyan/claude-ecosystem-hygiene --skill ecosystem-audit-wan-huiyan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve? Over time a Claude Code setup accumulates hundreds of installed skills, stale memory files, orphaned handoffs, and abandoned worktrees, with no visibility into which artifacts are actually used or healthy. This Skill performs a full-coverage audit of the ~/.claude ecosystem and turns raw session data into prioritized cleanup actions. ## Core Features & Use Cases - Parallel multi-category scan: Orchestrates 4 subagents covering 9 artifact categories (skills, memory, handoffs, ADRs, plans, reviews, findings, tasks, worktrees), parsing JSONL session logs for real skill invocation data. - Health scoring and evidence checks: Computes 0-100% health per category on 6 radar axes, enforces A/B-evidence-backed T1 tier promotion, and flags skills whose trigger surface is mismatched (high reference count but no measured pitfall reduction). - Interactive HTML report: Generates a dark-themed dashboard with radar chart, priority-coded P0/P1/P2 action cards, and a ready-to-run cleanup script. - Use Case: Ask "my ~/.claude feels bloated, audit my setup" and receive a report showing 8.9% skill utilization, 157 skills safe to uninstall, stale worktrees to remove, and a shell script that performs the cleanup. ## Quick Start Ask the assistant to run a full ecosystem audit of your Claude Code setup and generate the health report with cleanup recommendations.

Frequently Asked Questions about ecosystem-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my Claude Code skills and find unused ones?

Run the ecosystem audit, which parses JSONL session logs in ~/.claude/projects to count actual skill invocations over a configurable window (default 30 days). Skills are classified as Active, Relevant-Dormant, Niche-Dormant, DevOps-Dormant, or Deprecated, with uninstall recommendations for dormant categories.

How do I clean up stale worktrees and orphaned handoff files?

The audit scores each worktree by lifecycle state (merged branches score 25%, unmerged branches older than 14 days score 0%) and classifies handoffs as current, historical, or orphaned prompts. It then generates a ready-to-run shell script with the cleanup commands.

What does a T1 warning without A/B evidence mean in the audit report?

It means a layer was promoted to T1 (load-bearing) based only on reference count, without an A/B-harness result showing delta_vs_noop_se >= 1.0 above the noise floor. Either run the ab-harness to generate evidence or set evidence to 'reference-count-only' as an explicit disclaimer.

Why is a skill flagged as a trigger surface mismatch?

A mismatch means the skill has high reference count (over 10 appearances in session logs) but its A/B signal is below the 1.0 SE noise-floor threshold, so it adds latency on generic tasks without measurably reducing pitfalls. Remedies are narrowing the trigger description, restricting scope to pitfall-prone tasks, or deprecating it.

What happens if memory-hygiene is not installed when the audit runs?

The Memory axis renders as N/A with a hatched pattern on the radar chart instead of a fabricated score, and the report's Coverage section lists the blockers. The audit also fails loudly if the installed memory-hygiene major version differs from the pinned calibration version.

Does the ecosystem audit work without session logs?

Yes, but skill usage analysis is skipped and the report notes that no session data is available. All other categories (memory, handoffs, ADRs, docs, worktrees) still scan and score normally.