AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Askit Deprecate

skill-product-on-purpose-agent-skills-toolkit-askit-deprecate · by product-on-purpose

Validates and records a component's deprecation (status, replacement, and removal target) and keeps deprecated components validating until removal. Use when deprecating a component, recording its replacement, or checking the deprecation contract.

↗ Website ↗ Repository
— No reviews yet
0 installs
3 views
0.0% view→install

Install

$ agentstack add skill-product-on-purpose-agent-skills-toolkit-askit-deprecate

✓ 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 Askit Deprecate? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

askit-deprecate

Purpose

Manage a component's end-of-life cleanly. Two modes: deprecate marks a component status: deprecated and records its replacement (deprecated-by) and the version it will be removed in (remove-in), per Standard sec 3.7 / 7.5; check runs the G6 deprecation check (the contract is complete) and confirms a deprecated component still validates until its remove-in version, so consumers get a migration window rather than a sudden break. Policy and the lifecycle are in [references/deprecation-policy.md](references/deprecation-policy.md).

When to use

When deprecating a component, recording its replacement, or checking that deprecated components still validate before their removal version.

deprecate mode

  1. Set the component's status to deprecated in library.json (and the component frontmatter metadata.status).
  2. Record deprecated-by (the replacement component) and remove-in (the target plugin version for removal).
  3. Point users at the replacement in the component's description or body; do not delete it yet.

check mode

  1. Run node scripts/check.mjs (the aggregate gate, which includes the G6 deprecation check): every deprecated component declares deprecated-by + remove-in, and no component carries an invalid status.
  2. Confirm each deprecated component still passes its tier checks until remove-in (a deprecated component must keep validating during the migration window).

Scope

The G6 deprecation check enforces the contract deterministically; this skill is the front door and the policy. Actual removal at the remove-in version is a release-time action driven by askit-release (and recorded in the CHANGELOG). Deprecation is the Gold G6 baseline; a dedicated removal-automation skill is roadmap (the policy and frontmatter handling are what v1 requires).

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.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills