deprecate-skill

Archive obsolete skills with DEPRECATION.md logs and caller updates.

3|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/dvy1987/agent-loom --skill deprecate-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deprecate-skill
Source: https://github.com/dvy1987/agent-loom/tree/main/.agents/skills/deprecate-skill
Command: npx skills add https://github.com/dvy1987/agent-loom --skill deprecate-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deprecation is critical for maintaining a clean skill library: this process retires obsolete skills by archiving them instead of deletion, preserving history and enabling recovery if needed.

Core Features & Use Cases

  • Archive rather than delete to preserve provenance and allow rollback.
  • Update all callers and references (AGENTS.md, READMEs) to reflect the deprecation.
  • Create DEPRECATION.md in the archived directory and log the event for auditing.
  • Enforce user confirmation and document the rationale before archiving.

Quick Start

Document the deprecation case, obtain user confirmation, update all callers, archive the skill under .agents/skills/.deprecated/, and record the incident in the deprecation log.

Frequently Asked Questions about deprecate-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deprecate a skill without losing its history?▼

To deprecate a skill without data loss, archive it in a .deprecated directory instead of deleting it. This preserves provenance and enables recovery while updating all caller references and logging the event for auditing.

What is the best way to archive obsolete skills and update callers?▼

The best way to archive obsolete skills is to move them to .agents/skills/.deprecated/, create a DEPRECATION.md log, and update AGENTS.md and READMEs. This ensures all callers reflect the deprecation and an audit trail is maintained.

When should I use a deprecation workflow instead of deleting redundant skills?▼

Use a deprecation workflow when skills are redundant, superseded, or pose risk and callers must be updated. Archiving rather than deleting preserves history, satisfies audit-trail requirements, and provides a recovery path if needed.

Does skill governance require user confirmation before archiving?▼

Skill governance requires user confirmation before archiving to document the rationale safely. This enforcement ensures the deprecation process is intentional and prevents accidental loss of redundant or superseded skills.

How to document a deprecation event for auditing purposes?▼

To document a deprecation event for auditing, create a DEPRECATION.md file in the archived directory and record the incident in the deprecation log. This satisfies audit-trail requirements while preserving the skill's history.

Can I recover a skill after it has been archived as deprecated?▼

You can recover an archived deprecated skill because the process preserves history by moving it to .deprecated rather than deleting it. A defined recovery path allows rollback if the deprecation was premature or the skill is needed again.