duct-tape-dev
Skill10 starsChanged 5 months agoMITView on GitHub
Ships the quick patch that unblocks you right now and clearly flags it as debt to revisit later; invoke via /duct-tape-dev when you're blocked and need a working stopgap immediately, accepting that it's temporary.
In this repository24 other files it gives its agents.
- apollo-13Skill
- autopilot-chaosSkill
- basement-hackerSkill
- caffeine-overdoseSkill
- chinese-grandpaSkill
- cowboy-coderSkill
- crackhead-energySkill
- divorced-dadSkill
- feral-goblinSkill
- gas-station-geniusSkill
- goblin-modeSkill
- keyboard-gremlinSkill
- macgyverSkill
- meth-labSkill
- panic-modeSkill
- questionable-engineeringSkill
- rage-compileSkill
- redneck-engineerSkill
- schizotechSkill
- sleep-deprived-founderSkill
- speedrunSkill
- tax-fraudSkill
- weaponized-autismSkill
- zero-sleepSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
- Distinctive: line 17
Keep the patch contained and reversible — no sprawling changes that are hard to rip out later.
- Very specific: line 18
Add a clear // TODO(duct-tape): marker at the patch site explaining what's hacked and why.
- Distinctive: line 19
Verify the unblock actually works on the path that matters.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Duct Tape Dev
It's not pretty and it's not forever — but it'll hold until you can do it right. This mode finds the fastest patch that unblocks the current problem, then loudly marks it as debt so it doesn't quietly become permanent.
When to use
- You're blocked and need to move now; the proper fix can wait.
- A stopgap is acceptable as long as everyone knows it's a stopgap.
Behavior
- Identify the exact thing blocking forward progress and target only that.
- Apply the smallest patch that removes the block, even if it's inelegant.
- Keep the patch contained and reversible — no sprawling changes that are hard to rip out later.
- Add a clear
// TODO(duct-tape):marker at the patch site explaining what's hacked and why. - Verify the unblock actually works on the path that matters.
- State the risk: what this patch does NOT handle and when it will bite if left in.
- Suggest the proper fix in one or two lines so the real solution is captured before it's forgotten.
Output
A minimal working patch, an inline debt marker, and a short note of the risk plus the proper fix to do later.
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.