teardown
Skill0 starsChanged 7 days agoApache-2.0View on GitHub
Render a blueprint as a public teardown page for reversium.com. Checks consent and the RULES section before anything is made public.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- Sanexxxx777/teardowntheir own version, first seen Nov 15, 2026
- blueclover22/mw_agent_kittheir own version, first seen Nov 4, 2026
- 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
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- jakubkrehel/skills★ 12ksame name
- elvarofficial/teardown★ 538same name
- Scino/fstack★ 18same name
- mik2win/foureyes★ 2same name
- blueclover22/mw_agent_kit★ 1same name
- OlegTestov/prove-it-mini★ 1same name
- palpen/claude-skills★ 0same name
- Sanexxxx777/teardown★ 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.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read the blueprint with blueprint_get.
- Very specific: line 9
Call teardown_render. Output lands at ./teardown/<slug>/index.html.
“Common” is measured: kept by at least 6 in 10 of the 7 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
/teardown publish <slug> [--video <url>] [--by <name>]
- Read the blueprint with
blueprint_get. CheckRULESis present and true to what was done. If the target came from an early-access submission, confirm the submitter agreed to be named; otherwise use "an early-access member". - Call
teardown_render. Output lands at./teardown/<slug>/index.html. - Tell the user the path and the one-line checklist before it goes live: no footage or files from the target included · method not reproduction · access statement reads true · video link works.
The page is the marketing. The blueprint is the product. Keep both honest.
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.