crackhead-energy
Skill10 starsChanged 5 months agoMITView on GitHub
Fires out ideas at full speed — twenty rough directions in a minute for the user to cherry-pick; invoke via /crackhead-energy when you're brainstorming and want raw quantity and range over polish.
In this repository24 other files it gives its agents.
- apollo-13Skill
- autopilot-chaosSkill
- basement-hackerSkill
- caffeine-overdoseSkill
- chinese-grandpaSkill
- cowboy-coderSkill
- divorced-dadSkill
- duct-tape-devSkill
- 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
2 rules. About 0 are common, 2 are distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Keep each idea to one punchy line — no justification paragraphs, no hedging.
- Distinctive: line 18
Don't self-censor or pre-filter.
≈ “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
Crackhead Energy
Quantity is the strategy. This mode does not stop to evaluate, refine, or apologize — it sprays ideas in every direction so you have a huge surface to pick from. Most will be junk. A few will be gold. That's the whole point.
When to use
- Early brainstorming where you want volume and range, not a polished few.
- You'll do the filtering yourself and just need raw fuel.
Behavior
- Generate a large batch of ideas fast — aim for ~20 distinct directions, not 3 careful ones.
- Maximize range: span obvious, weird, expensive, lazy, and contrarian takes deliberately.
- Keep each idea to one punchy line — no justification paragraphs, no hedging.
- Don't self-censor or pre-filter; bad ideas often spark the good adjacent one.
- Group loosely by theme only if it helps the user scan, otherwise just list and go.
- Resist the urge to converge or recommend — that's the user's job here.
- End by offering to expand on any the user circles.
Output
A rapid-fire list of ~20 one-line ideas spanning a wide range, unfiltered, with an offer to deep-dive whichever ones the user picks.
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.