teardown
Skill1 starsChanged 8 days agoMITView on GitHub
Use when asked to remove the mak-managed rules block from ~/.claude/CLAUDE.md, especially before uninstalling the plugin.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- elvarofficial/teardowntheir own version, first seen Nov 1, 2026
- jakubkrehel/skillstheir own version, first seen Oct 25, 2026
- Scino/fstacktheir own version, first seen Oct 25, 2026
- OlegTestov/prove-it-minitheir own version, first seen Oct 20, 2026
- mik2win/foureyestheir own version, first seen Oct 8, 2026
- palpen/claude-skillstheir own version, first seen Apr 14, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- jakubkrehel/skills★ 12ksame name
- elvarofficial/teardown★ 538same name
- Scino/fstack★ 18same name
- mik2win/foureyes★ 2same name
- OlegTestov/prove-it-mini★ 1same name
- palpen/claude-skills★ 0same 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.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brainstormingSkill
- commitSkill
- design-doc-templateSkill
- dev-kickoffSkill
- dev-resumeSkill
- doc-auditSkill
- reverse-engineeringSkill
- review-reportSkill
- roadmap-planningSkill
- setupSkill
- verify-checklistSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
If it does not exist, or contains no <!-- mak:begin marker: report "nothing to remove" and stop.
- Distinctive: line 16
If a begin marker exists without an end marker, or more than one begin/end marker exists (corrupted/duplicated state): do not guess the …
- Very specific: line 22
Only the marker-delimited block is removed.
- Very specific: line 23
Do not run git commands; ~/.claude may not be a repository.
“Common” is measured: kept by at least 6 in 10 of the 5 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
mak:teardown — Remove the mak Block from the Global CLAUDE.md
Reverses mak:setup: deletes the marker-delimited block from ~/.claude/CLAUDE.md. Content outside the markers is never touched.
Procedure
- Read
~/.claude/CLAUDE.md.- If it does not exist, or contains no
<!-- mak:beginmarker: report "nothing to remove" and stop.
- If it does not exist, or contains no
- Remove the block — delete everything from the
<!-- mak:beginmarker line through the<!-- mak:end -->marker line, inclusive. Collapse any resulting runs of 3+ blank lines to one.- If a begin marker exists without an end marker, or more than one begin/end marker exists (corrupted/duplicated state): do not guess the block boundary. Show the user the marker locations and ask how far to remove.
- If the file is now empty or whitespace-only — tell the user; offer to delete the file or leave the empty file (their choice). Do not delete it unprompted.
- Report — state that the block was removed. If
~/.claude/CLAUDE.md.mak-backupexists, mention it: it holds the pre-setup snapshot and can be deleted by the user once they're satisfied, or used to compare (diff) if anything looks off. Do not delete the backup automatically.
Cautions
- Only the marker-delimited block is removed. Never remove legacy (pre-plugin) manually-pasted sections here — that was only offered during
mak:setupwith confirmation. - Do not run
gitcommands;~/.claudemay not be a repository.
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.