brain-dump
Skill4 starsChanged 10 days agoMITView on GitHub
Turn raw thoughts, monologues, notes, files, or links into a multi-opportunity brief before grilling.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- ggoosen/Digital-Workforcetheir own version, first seen Nov 8, 2026
- anotherben/claude-harnesstheir own version, first seen Nov 8, 2026
- aribajahan/claude-skillstheir own version, first seen Sep 23, 2026
- TechTripAi/techtrip-secondbraintheir own version, first seen Sep 15, 2026
- bohorquezandrea/day-planner-dharmatheir own version, first seen Aug 26, 2026
- eugenezhangco-spec/athenatheir own version, first seen May 3, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- anotherben/claude-harness★ 7same name
- ryankolean/summit-claude-skills★ 4same name
- TechTripAi/techtrip-secondbrain★ 2same name
- ggoosen/Digital-Workforce★ 1same name
- aribajahan/claude-skills★ 0same name
- bohorquezandrea/day-planner-dharma★ 0same name
- eugenezhangco-spec/athena★ 0same name
- niyaznurbhasha/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 repository117 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibilitySkill
- agent-watchdogSkill
- aipSkill
- animateSkill
- animation-performanceSkill
- animation-vocabularySkill
- ask-benSkill
- ask-sonnerSkill
- bazelSkill
- bend-lawsSkill
- blast-radiusSkill
- break-uiSkill
- ci-fixesSkill
- codebase-designSkill
- codex-compatSkill
- codexSkill
- commit-push-prSkill
- connect-querySkill
- create-verification-skillSkill
- demoSkill
- development-lifecycleSkill
- diagnosing-bugsSkill
- docsSkill
- dogfoodSkill
- domain-modelingSkill
- e2e-testingSkill
- effect-tsSkill
- effect-v3-to-v4Skill
- efficient-frontierSkill
- eli5Skill
- excalidraw-diagramSkill
- extend-harnessSkill
- frontend-invariantsSkill
- frontend-starter-kitSkill
- full-sendSkill
- gesturesSkill
- golang-reviewSkill
- golangSkill
- goSkill
- grillingSkill
- handoffSkill
- hook-auditSkill
- implement-specSkill
- improve-animationsSkill
- improve-codebase-architectureSkill
- improveSkill
- launchdarklySkill
- lie-detectorSkill
- maintain-verification-skillSkill
- make-pr-easy-to-reviewSkill
- mobile-nativeSkill
- plan-arbiterSkill
- plow-aheadSkill
- postgresqlSkill
- primeSkill
- productSkill
- protobufSkill
- prototypeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
1
Distinctive
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 64
Keep it self-contained; link or cite sources instead of copying them.
“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
Optional discovery before /grilling. Unstructured thoughts or a monologue may reveal several independent tracks; preserve them instead of forcing one objective.
Return the brief in chat unless asked to save or publish. Do not implement, create tickets, or commit to opportunities.
1. Absorb
Treat the conversation, notes, attachments, articles, files, and links as one dump. If the user is still talking, acknowledge and wait; otherwise proceed. Read supplied material and repo evidence. Extract external claims, conclusions, constraints, timing, and implications; use /read-the-damn-docs or /research when current primary sources matter.
Separate source/repo facts, user observations, labelled inferences, contradictions, and unknowns. Never ask the user to repeat an answer already present.
2. Reconstruct
Extract actors, pains, outcomes, systems, triggers, constraints, ideas, rejected directions, urgency, and success signals. Name the surface; separate need from solution. Record implied answers in an Answer ledger:
- Settled: explicit or directly supported.
- Tentative: inferred and safe to challenge.
- Unknown: missing and able to change direction.
3. Map opportunities
Cluster duplicates and list each distinct, supported direction. Usually show 2-5; keep more only for genuinely broader work. Include disciplines only when evidence supports them.
For each opportunity give outcome/actor, evidence, work products, dependencies/risks/decisions, and cheapest proof: lookup, prototype, measurement, or reversible slice. Recommend by value, evidence, urgency, and reversibility; keep alternatives visible.
4. Return
Prune empty sections from this structure:
## Brain dump brief
### Orientation
<surface, tension, recommendation>
### Source synthesis
<facts, implications, contradictions, citations or paths>
## Answer ledger
| Likely grilling question | Extracted answer | State | Evidence |
|---|---|---|---|
| ... | ... | Settled / Tentative / Unknown | ... |
## Opportunity map
### <Opportunity>
- Outcome:
- Evidence:
- Work products:
- Risks and dependencies:
- Cheapest next proof:
## Grilling handoff
- Settled context to preserve:
- Tentative assumptions to challenge:
- Material user decisions still open:
- Facts to look up without asking the user:
- Candidate prototypes or measurements:Keep it self-contained; link or cite sources instead of copying them.
5. Hand off
Continue with /grilling for material user decisions and pass every track. Ask only Unknown items that could invalidate or prioritize it; challenge Tentative items when downside matters; preserve Settled answers unless contradicted. Otherwise recommend the next lookup, prototype, spec, plan, or execution skill.
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.

