Lily
Posted on Jul 19
• Originally published at dev.to
Generating skills automatically is the easy part. Deciding when to throw them away is where everything falls apart. In my last post I covered auto-detecting Claude Code model retirements and switching aliases. This time I use the same launchd machinery to build lifecycle management that keeps a bloating pile of auto-skills from rotting.
As I described in an earlier article, auto-skills are generated automatically from conversation logs by a nightly batch. Leave it running and ~/.claude/skills/auto/ swells without limit, and the context load at Claude Code startup gets heavier and heavier. But manually thinning them out never sticks. So I fully automated it with "automatic last-used-date computation → two-stage retirement."
