Why a good setup goes bad
The more you build in Claude Code, the more it drifts. Files go stale, instructions point at folders that moved, and the agent starts answering from last month's numbers without telling you.
- Poisoning. A stale file the agent trusts as the truth.
- Bloat. So much loaded context that the important part gets lost.
- Confusion. Two files that say different things about the same fact.
- Clash. Instructions that contradict each other, so behavior flips.
What it checks
01 Freshness Every data feed, and when it last actually updated.
02 Routing Every path and pointer in your instructions, checked against what exists.
03 Organization Duplicates, bloated folders, anything a human couldn't find.
04 Verdict Red, yellow or green, with the fixes grouped for your yes.
Copy. Paste. Done.
Paste this into Claude Code. It installs the skill and checks it worked.
Install the os-audit skill from https://github.com/ezjonline/ezj-automations/tree/main/skills/os-audit into my Claude Code skills directory. Clone https://github.com/ezjonline/ezj-automations, copy the skills/os-audit folder to ~/.claude/skills/os-audit, then confirm the skill is available.Try it with
/os-auditRun it at the root of any project. It reads, it reports, and it tells you how each problem would bite.
Free AI Audit
Want the whole system, not just the skill?
This is one piece of how I run my business. Book a free AI Audit and I'll map out what the full setup looks like for yours.
Get my free AI Audit