AgentStack
SKILL verified Apache-2.0 Self-run

Deprecation And Migration

skill-mmccalla-coding-agent-skill-library-deprecation-and-migration · by mmccalla

Use when retiring an old path, replacing a legacy behaviour or moving users to a new interface or workflow.

No reviews yet
0 installs
12 views
0.0% view→install

Install

$ agentstack add skill-mmccalla-coding-agent-skill-library-deprecation-and-migration

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Deprecation And Migration? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Deprecation and Migration

When to use

Use this skill when removing or replacing a skill, doc path, workflow, API surface or other user-facing behaviour that still has active dependents.

Objective

Remove old paths safely by providing a clear replacement, a controlled transition period and a verified end state.

Procedure

  1. Identify what is being replaced and why.
  2. Define the replacement path and compatibility expectations.
  3. Mark the old path clearly with deprecation guidance.
  4. Migrate dependents in small, observable steps.
  5. Remove the old path only after usage is confirmed to be gone or intentionally waived.

Rules

  • Do not delete a legacy path before the replacement is valid.
  • Do not surprise users with a silent incompatibility break.
  • Do not leave parallel paths undocumented.
  • Do not treat migration as complete until the old path is no longer needed.

Example

When replacing an old skill path, add the new path first, update references, leave a short deprecation note where users will find the old entry and run a search for dependants. Remove the old path only after consumers have moved or the user explicitly accepts the compatibility break.

References

Verification

  • [ ] Deprecated surface and timeline stated.
  • [ ] Migration path and consumer communication documented.
  • [ ] Compatibility or dual-run period noted.
  • [ ] Residual migration risks stated.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.