Retire Model
Automates the model lifecycle — promoting entries from current to legacy to deprecated to retired as their dates pass, and stripping references from content pages once a model is gone.
Entry verified April 21, 2026
The short answer
Manual lifecycle management stops scaling past 3-4 models. This skill checks today's date against each model's retiresOn field, proposes status promotions, and lists content-page references that need removing. Output is a diff you approve before anything is applied.
When to use it
Weekly. Ideal as a scheduled run alongside /drift-check so model staleness never sits past the next publishing cycle.
Setup
- 1
Save the file as ~/.claude/skills/retire-model.md.
- 2
Feed: a data file with status and retiresOn fields per model.
- 3
Skill outputs a diff — status changes plus reference removals — which you approve before apply.
- 4
Don't wire to auto-apply; a premature retirement flag, before the vendor confirms, breaks pages that still need to serve traffic.
Example
You: /retire-model Claude: 1 promotion: Haiku 3 → retired. Removes 3 references from FAQ on /ai-models. Apply?
Source & attribution
- Author
- Bryan Collins
- Licence
- MIT
- Type
- Original
Original pattern published under MIT — attribution preserved by convention, not licence requirement.
Caveats
Don't auto-apply — a premature retirement flag (before vendor confirms) breaks pages.
56 skills across 10 categories, all licence-verified.