How do I install the Askit Deprecate skill?

Run npx skillmds@latest add product-on-purpose/askit-deprecate in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Askit Deprecate safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Askit Deprecate?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Askit Deprecate free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Askit Deprecate?

product-on-purpose (@product-on-purpose) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Askit Deprecate by product-on-purpose

Name: Askit Deprecate
Author: product-on-purpose

Askit Deprecate

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.

File contents

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.

When to use

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

deprecate mode

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

check mode

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.
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).

---name: askit-deprecatedescription: 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.---# askit-deprecate## PurposeManage 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 useWhen deprecating a component, recording its replacement, or checking that deprecated components still validate before their removal version.## deprecate mode1. 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 mode1. 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).## ScopeThe 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).

Frequently asked questions