delete
Skill1 starsChanged 5 months agoMITView on GitHub
Remove a knack - its manifest and the skills it owns - from the project, safely. Use when the user wants to "remove a knack", "delete a capability", "retire X", or take a skill set off the project. Checks who composes the target and which skills are shared with other knacks.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- devjiwonchoi/skillstheir own version, first seen Nov 8, 2026
- microsoft/Employee-Self-Service-Agent-Developer-Kittheir own version, first seen Oct 13, 2026
- SuShuheng/obshare-clitheir own version, first seen Mar 19, 2026
- SprintsAI/lightsprint-claude-code-plugintheir own version, first seen Mar 1, 2026
- jjenkins/agent-image-skillstheir own version, first seen Mar 1, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- microsoft/Employee-Self-Service-Agent-Developer-Kit★ 29same name
- devjiwonchoi/skills★ 2same name
- SprintsAI/lightsprint-claude-code-plugin★ 2same name
- SuShuheng/obshare-cli★ 2same name
- jjenkins/agent-image-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
Check & record: Run /knacks:validate to confirm no dangling refs or broken graph remain.
- Distinctive: line 33
Propose first by default: Treat steps 1-4 as read-only and show the full plan before any delete or edit.
- Distinctive: line 38
Delete only what's exclusively the target's: When in doubt about sharing, prefer keep and say why.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/knacks:delete: retire a knack safely
Removing a capability is not a blind delete. Other knacks may compose the target, and its skills may be shared with other knacks. This skill checks both before touching anything and proposes exactly what to delete / keep / update.
Steps
- Resolve the target. Get the
idfrom$ARGUMENTS(or ask). Readknacks/<id>.md; note itsskills:andcomposes:. If there's no such manifest, say so and stop. - Who composes it? Glob
knacks/*.mdfor any knack whosecomposes:lists the target. For each, the user picks: keep the target (cancel removal), or update that dependent to drop the target from itscomposes:(and fix any prose that referenced it). Never leave a danglingcomposes:ref. - Which skills are exclusive? For each skill in the target's
skills:, check whether any other knack lists it (count a dependent you're updating in step 2 as no longer listing it):- Exclusive (no other knack lists it) -> propose delete.
- Shared (another knack lists it) -> propose keep, naming who still uses it.
- Propose the full plan, change nothing yet. One reviewable list: the target manifest -> delete; any dependent edits from step 2; each owned skill -> delete (exclusive) or keep (shared, with who uses it). One line of rationale each; invite the user to override any line. Ask for an explicit yes.
- Apply, in order: dependent edits first (so nothing transiently dangles), then the target manifest, then the exclusive skill directories. Never touch a skill marked keep.
- Check & record. Run
/knacks:validateto confirm no dangling refs or broken graph remain.
Rules
- Propose first by default. Treat steps 1-4 as read-only and show the full plan before any delete or edit. Apply without a separate yes only when the project's settings permit it; gating is the project's call, not this skill's.
- Never break a dependent. A knack that composes the target is resolved (keep or update) before the target goes; a shared skill is never deleted while another knack still lists it.
- Delete only what's exclusively the target's. When in doubt about sharing, prefer keep and say why; under-deleting is recoverable, over-deleting is not.
- Operate on one knack per invocation. To tear down a subsystem, remove the leaves first.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.