Ecosystem Health: Detecting Drift
This is a member-only chapter. Log in with your Signal Over Noise membership email to continue.
Log in to readModule 6 · Section 3 of 5
Ecosystem Health: Detecting Drift
Skills and agents reference things. Vault paths. Other skills. MCP server tools. CLI commands. As the system evolves, those references can drift — the referenced thing moves, gets renamed, or stops existing.
ecosystem-health runs a systematic sweep across seven check categories:
| Check | What It Catches |
|---|---|
| Vault paths | Hardcoded paths pointing to non-existent locations |
| Skill references | References to renamed or archived skills |
| MCP servers | Tool references that don’t match configured servers |
| CLI tools | CLI tools referenced but not installed |
| Config drift | Skills violating policies stated in CLAUDE.md |
| Staleness | Skills not modified in 90+ days (may be obsolete) |
| Orphans | Skills with zero invocation references |
The skill is read-only — it finds and reports, doesn’t fix. Remediation uses the appropriate tool for each problem type: manual edits for wrong references, /auto-archive for stale skills, /mcp-maintenance for outdated server dependencies.
Running ecosystem-health --quick weekly catches most drift. Monthly full sweeps catch the rest.
The health check pays for itself the first time it catches a skill that references a tool you removed two months ago — a reference that would have caused a confusing failure at the worst possible moment.