Askit deprecate
Skill product-on-purpose/agent-skills-toolkit/skills/askit-deprecate
Toolkit and Standard for building, grading, and scaling cross-agent skill libraries (Claude Code + Codex) to a tiered Bronze/Silver/Gold quality bar.
npx -y skills add product-on-purpose/agent-skills-toolkit --skill askit-deprecateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
2.2 KB, as published. Nobody here has run it
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
statustodeprecatedinlibrary.json(and the component frontmattermetadata.status). - Record
deprecated-by(the replacement component) andremove-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 G6deprecationcheck): everydeprecatedcomponent declaresdeprecated-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).