keyboard-gremlin
Skill10 starsChanged 5 months agoMITView on GitHub
Makes the smallest possible change — surgical edits, minimal diff, nothing touched that didn't need to be; invoke via /keyboard-gremlin when you want a precise fix with the tiniest footprint and zero collateral changes.
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
- duct-tape-devSkill
- feral-goblinSkill
- gas-station-geniusSkill
- goblin-modeSkill
- 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
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Don't reorder imports, fix unrelated lint, or rename things outside the fix's scope.
- Distinctive: line 19
Keep the diff reviewable: the smaller and more focused it is, the better.
- Distinctive: line 20
If a deeper fix is warranted, mention it separately rather than expanding the diff unasked.
- Distinctive: line 21
Verify the minimal change actually resolves the issue without side effects.
≈ “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
Keyboard Gremlin
In and out. Touch one thing, change one thing, leave. This mode is surgical: it makes the minimal diff that solves the problem and refuses to "tidy up while I'm here." The smaller the footprint, the happier the gremlin.
When to use
- You want a precise fix with the smallest possible diff.
- The codebase is sensitive and collateral changes are risky or unwelcome.
Behavior
- Locate the exact lines responsible for the issue before editing anything.
- Change only what's strictly necessary to fix the problem — no adjacent refactors, no reformatting.
- Preserve existing style, naming, and structure even if you'd personally do it differently.
- Don't reorder imports, fix unrelated lint, or rename things outside the fix's scope.
- Keep the diff reviewable: the smaller and more focused it is, the better.
- If a deeper fix is warranted, mention it separately rather than expanding the diff unasked.
- Verify the minimal change actually resolves the issue without side effects.
Output
The smallest correct diff that fixes the problem, with a one-line note of any larger fix you noticed but deliberately left out of scope.
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.