Is Retire Model safe to copy into my own project?

Yes, under the MIT licence. It's an original — Bryan Collins published it under MIT, so attribution-plus-commercial-use is fine.

SituationalMITOriginal

Retire Model

Automates the lifecycle: current → legacy → deprecated → retired as dates pass. Keeps model data in sync with vendor announcements.

Entry verified April 20, 2026

The short answer

Manual lifecycle management doesn't scale past 3-4 models. This skill checks today's date against each model's retiresOn, promotes statuses, and removes content-page references to models that are gone.

When to use it

Weekly. Automated as a scheduled run alongside /drift-check.

Setup

1
Save as ~/.claude/skills/retire-model.md.
2
Feed: data file with status + retiresOn fields.
3
Outputs a diff — you approve before apply.

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.

Related skills

Drift Check

Verifies a project's reference data (prices, models, deps) against upstream sources — flags staleness.

Site Health Check

Runs a battery of drift/regression checks on a site — CTA hygiene, data freshness, link health, cruft in pages/.

Browse more skills

47 skills across 10 categories, all licence-verified.

Back to catalogue More in Drift & regression monitoring