remove-skill
Remove a repo-owned runtime-kit skill with a dry-run-first active reference audit and retained historical plan records.
- License 许可
- MIT
- 最近更新
- 2026-08-29
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- remove-skill
- description
- Remove a repo-owned runtime-kit skill with a dry-run-first active reference audit and retained historical plan records.
03 SKILL.md 正文
Remove Skill
Contract
Prereqs:
- Run from the
agent-runtime-kitrepository root. - The target is a repo-owned managed skill in
manifests/skills.yaml. - The first pass is dry-run only. File mutation requires explicit apply approval from the user or the active delivery plan.
agent-runtimeis installed from the released nils-cli package and available onPATH.
Inputs:
- Canonical skill ID in the form
<domain>.<skill>. - Optional explicit cleanup approval for retained historical docs. Historical plan records are retained by default.
Outputs:
- A dry-run list of active files and reference classes that would change.
- After apply approval: removed
core/skills/<domain>/<skill>/source,manifests/skills.yamlentry,manifests/plugins.yamlcontainment, product render metadata, golden snapshots, sandbox expected skill pins, runtime-smoke cases, hook/reminder metadata, and maintained docs references. - A reviewed
manifests/skill-dispositions.yamlrow is retained when the skill belongs to the frozen #562 migration cohort; it records destination, replacement/compatibility needs, and live cleanup instead of deleting history. - A validation summary proving no active references remain.
Failure modes:
- The target skill is ambiguous or not represented in the manifest.
- Active references remain after apply.
- The workflow would edit historical
docs/plans/**records without explicit cleanup approval. - The validation gate fails after removal.
Entrypoint
Start with a dry-run reference inventory:
skill_id="<domain>.<skill>"
domain="${skill_id%%.*}"
skill="${skill_id#*.}"
rg -n "$skill_id|$skill" \
core manifests targets tests docs/source SUPPORT_MATRIX.md DEVELOPMENT.md
Classify matches before editing:
- source skill directory
- skill manifest entry
- plugin containment
- product plugin metadata or target path
- rendered build output and golden snapshots
- sandbox expected skill lists
- runtime-smoke matrix and case-runner probes
- hook/reminder metadata
- maintained docs
- retained historical records under
docs/plans/**
After apply approval and edits:
bash scripts/ci/skill-governance-audit.sh --update-counts
bash scripts/ci/skill-governance-audit.sh
agent-runtime render --product codex --update-golden
agent-runtime render --product claude --update-golden
agent-runtime render --product hermes --update-golden
bash scripts/ci/sandbox-install-rehearsal.sh
bash tests/runtime-smoke/run.sh --mode deterministic --domain "$domain"
bash scripts/ci/all.sh
Workflow
- Confirm the skill ID exists exactly once in
manifests/skills.yaml. - Build the dry-run inventory with
rgand classify every active reference. - Exclude
docs/plans/**from default mutation. Keep those records as historical evidence unless the user explicitly asks for cleanup. - Present the planned active delta and stop unless apply approval is already part of the active plan.
- Remove the source directory and active manifest entry. If the ID belongs to
the frozen migration cohort, update its disposition row to
reviewed; never delete or replace a baseline row to make a new pending skill fit. - Remove plugin containment and product metadata for the target skill.
- Remove rendered/golden/sandbox/runtime-smoke/hook/reminder references.
- Run
bash scripts/ci/skill-governance-audit.sh --update-countsto refresh maintained active skill-count surfaces without touching historicaldocs/plans/**records. - Re-run the reference inventory and fail if active references remain outside the allowed historical set.
- Run governance, render, sandbox, runtime-smoke, and full CI validation.
Boundary
This skill owns safe removal sequencing and the decision to retain historical
records. It does not own a general-purpose deletion engine. If removal needs a
stable dry-run/apply planner or machine-readable reference graph, implement and
release that primitive in sympoies/nils-cli, then pin the consumed binary in
manifests/skills.yaml.
04 同仓库更多 Skills
removable-skill
暂无简介
removable-skill
暂无简介
removable-project-skill
Fixture project-local skill used to prove remove-project-skill dry-run coverage.
project-sample-skill
Fixture project-local skill used to prove create-project-skill governance coverage.
project-local-skill
Fixture project-local skill used by runtime-kit project-local smoke checks.
topic-radar
Aggregate read-only AI and technology trend signals (Polymarket, Hacker News, GitHub, arXiv, Hugging Face, news search) into source-grounded Markdown or JSON; the lower-level data engine behind `daily-brief`.