retire-an-obsolete-skill
Use when a skill no longer matches reality and misleads tasks that load it. Deprecates it, redirects callers, and removes it without leaving a gap.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 81
- Forks
- 17
01 前言 Front Matter
- name
- retire-an-obsolete-skill
- description
- Use when a skill no longer matches reality and misleads tasks that load it. Deprecates it, redirects callers, and removes it without leaving a gap.
02 资源文件 3
- 许可证LICENSE1.0 KB
- 参考文档SOURCE.md350 B
- 参考文档TRUST.auto.yaml2.2 KB
03 SKILL.md 正文
Retire an Obsolete Skill
A skill that no longer works is worse than a missing one: it loads confidently and gives wrong steps. Retirement is a controlled removal — redirect first, then delete.
Procedure
- Prove obsolescence with a concrete failure: run its main command and show it errors or does the wrong thing.
- Find who loads it:
grep -rl "<slug>" . --include='*.md'. - Write the replacement first — retire only once the successor exists and is verified.
- Mark the old skill deprecated rather than deleting immediately:
status: deprecatedplus a pointer to the successor. - Redirect callers by editing their references to the new slug.
- Keep the deprecated file for one release cycle so an external caller does not break silently.
- After the cycle, delete the directory and remove any index or listing entry for it.
- Check the slash-command or skill registry for a leftover entry that still routes to it.
- If it has no successor and the procedure is simply gone, say so plainly rather than leaving a broken skill.
- Record the retirement: slug, reason, successor, date.
Pitfalls
-
Deleting the skill before the replacement is verified, leaving a gap.
-
Leaving a deprecated skill unmarked, so it still loads and still misleads.
-
Marking deprecated but not fixing the references, so callers keep invoking the old slug.
-
Retiring because the skill is old rather than because it is wrong — age is not obsolescence.
-
Forgetting the registry or index entry, so the name still resolves to nothing.
-
Deprecating a skill that an automated task references and never updating the task.
-
Burying the successor pointer in a comment instead of where a reader loads it.
-
Deleting the directory while a task is mid-run and depending on it.
Verification
grep -rn "<slug>" . --include='*.md' | grep -v deprecated; ls skills/<successor>/SKILL.md
# passes when no live reference points at the old slug and the successor exists
Report to the user: the slug retired, the failure that proved it obsolete, the successor, and the references redirected.
04 同仓库更多 Skills
recipe-performance
Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold/warm/background-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout/paint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.
mexc-spot-websocket
MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.
mexc-spot-rest
MEXC Spot REST workflows for public data, signed account requests, orders, wallet/admin actions, and secure signing without exposing API keys.
mexc-futures-websocket
MEXC Futures WebSocket workflows for public streams, private account/order/position streams, ping/pong, subscriptions, and depth maintenance.
0xklen-version-and-refresh-sanctions-lists
暂无简介
verify-tests-cover-changed-lines
Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.