AgentStack
SKILL verified MIT Self-run

Braindump

skill-samuelndce-claude-super-skill-library-braindump · by SamuelNDCE

The prompt fixer: turns a messy, unstructured brain dump into a clear, well-structured prompt, confirms it, then executes it, so the user never has to prompt engineer by hand. Auto-triggers on any raw, rambling, stream-of-consciousness message, even without the /braindump command, as long as it's a single-topic ask. Also triggers on explicit invocation via /braindump, or requests to 'fix this pro…

No reviews yet
0 installs
6 views
0.0% view→install

Install

$ agentstack add skill-samuelndce-claude-super-skill-library-braindump

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Braindump? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Braindump

> The prompt fixer. Skip prompt engineering: dump your thoughts as messy as they come, get back a clean, structured prompt built from them, review it in one glance, then it runs.

What this does

Takes everything after /braindump, however messy, rambling, or disorganized, and turns it into a clean, structured prompt. Shows the refined prompt for approval, then executes it in the same session. The user gets the output quality of a well-written prompt without having to write one.

Choosing between braindump and superbraindump

| | braindump (this skill) | [superbraindump](../superbraindump/SKILL.md) | |---|---|---| | Use for | A single, contained ask, messy but simple | Multiple bundled asks, large/cross-cutting scope, heavy ambiguity, high stakes | | Fires on | /braindump, any raw single-topic ramble, or "fix this prompt" / "clean this up" | /superbraindump, or a ramble showing the complexity signals in the left column | | Template | Goal / Context / Constraints / Done when | Same, plus Output format and Edge cases |

If a dump turns out to match the right column partway through Step 1, stop and switch to superbraindump instead of continuing here.

Usage

/braindump 

Process

Step 1: Extract the signal

Read the entire dump and pull out:

  • Goal: what the user actually wants done (not just what they said first)
  • Context: project, files, tools, prior work mentioned in passing
  • Constraints: anything phrased as "but", "don't", "except", "it has to", "I hate when"
  • Success criteria: what "done" or "good" looks like, stated or implied
  • Ambiguities: anything that could be read two ways

Ignore filler, self-corrections, and tangents unless they change the goal.

Step 2: Rewrite as a structured prompt

Produce a compact prompt block:

**Goal:** 
**Context:** 
**Constraints:** 
**Done when:** 

Omit any section that has nothing real in it. Do not pad. The refined prompt should be shorter than the dump, not longer.

Step 3: Show it and flag assumptions

Present the refined prompt to the user. Below it, list any assumptions made to fill gaps, e.g.:

> Assumed: "the store" means the Snagworthy Shopify store.

Then ask for a go-ahead: the user replies "go", tweaks the prompt, or corrects an assumption.

Step 4: Execute on approval

When the user approves, execute the refined prompt immediately in the current session as if it were their message. Follow all normal workflows and skills that the refined prompt would trigger.

Rules

  • One clarifying question max, and only if execution is genuinely impossible without the answer. Otherwise make a reasonable assumption and flag it in Step 3.
  • Never execute before approval. Step 3 is a hard gate.
  • Preserve the user's intent, not their wording. If they rambled toward X but clearly meant Y by the end, the prompt is Y.
  • No side effects during refinement. No vault writes, no logging, no file changes until execution is approved.
  • Keep the refined prompt in the user's language and terms where they are precise; replace vague terms with concrete ones only when the dump makes the meaning clear.

Example

Dump: > ok so like the product pages are kinda slow i think its the images maybe? also owen said something about the reviews widget but idk. anyway main thing is speed, google is gonna tank us, oh and dont touch the checkout we just fixed it

Refined prompt: > Goal: Diagnose and fix product page load speed on the store. > Context: Images are the suspected cause; a reviews widget was also flagged (secondhand, unverified). > Constraints: Do not modify anything in the checkout flow. > Done when: Product pages measurably load faster (before/after numbers shown). > > Assumed: "the store" = Snagworthy. The reviews widget is investigate-only unless it turns out to be the actual bottleneck.

See also

[superbraindump](../superbraindump/SKILL.md) — the complex/high-stakes tier. See the comparison table above for which one fires when.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.