01-package-scaffolding/skill-deprecation-manager/SKILL.md
Safely deprecate, retire, or merge obsolete skills while preserving backward references and library clarity. Use when a user says 'deprecate this skill', 'retire this', or 'this is replaced by X', when a catalog audit identifies a skill for retirement, or when a skill is causing harm and needs immediate pull. Do not use when the skill needs improvement (use skill-improver) or when the repo doesn't support deprecation (just delete).
npx skillsauth add chelch5/skilllibrary skill-deprecation-managerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Safely deprecates a skill: updates state, adds notices, redirects references, preserves content for history.
Determine the reason:
# Search across repo
grep -r "<skill-name>" AGENTS.md **/SKILL.md skills-lock.json docs/ 2>/dev/null
# Check "Do NOT use when" sections in sibling skills
grep -r "Do NOT use" **/SKILL.md | grep -i "<skill-name>"
Replace with replacement skill pointer, or note "no replacement available".
metadata:
maturity: deprecated
deprecated_by: replacement-skill # or "none"
deprecated_reason: "Superseded by newer version"
At top of SKILL.md body:
> ⚠️ DEPRECATED as of [date]. Use [replacement] instead.
> Reason: [one sentence]. Kept for reference only.
mkdir -p ARCHIVE
mv skill-name/ ARCHIVE/skill-name/
Do NOT delete — preserve for reference and provenance.
deprecated: true in skills-lock.json## Deprecation: [skill-name]
**Reason**: [superseded | merged | unused | failing | harmful]
**Replacement**: [skill] or "none"
**Date**: [YYYY-MM-DD]
### References Updated
| File | Change |
|------|--------|
| [file] | [old → new] |
### Verification
- [x] All references updated
- [x] Deprecation notice added
- [x] Archived
- [x] Registry updated
testing
Manages context window budgets, loading strategies, and compaction techniques for AI-assisted coding sessions. Trigger on 'context window', 'what to load', 'context management', 'context overflow', 'token budget'. DO NOT USE for loading specific project docs into agent context (use project-context) or prompt wording and optimization (use prompt-crafting).
development
Implements authentication, session, token, and authorization patterns for the current stack. Trigger on 'add auth', 'JWT', 'OAuth', 'login endpoint', 'session management', 'API key auth'. DO NOT USE for OWASP hardening checklists (use security-hardening), threat modeling (use security-threat-model), or secret rotation/storage (use security-best-practices).
tools
Defines request/response shapes, versioning, validation, and compatibility rules for API-first work. Trigger on 'design API', 'OpenAPI spec', 'REST schema', 'API versioning', 'generate client SDK'. DO NOT USE for GraphQL schemas, gRPC/protobuf definitions (use stack-standards), auth endpoint logic (use auth-patterns), or external API client wrappers (use external-api-client).
development
Create a repo-local ticket system with an index, machine-readable manifest, board, and individual ticket files. Use when a repo needs task decomposition that autonomous agents can follow without re-planning the whole project each session. Do not use for executing tickets (use ticket-execution) or quick fixes that don't warrant formal tickets.