⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

wonder-pill

ara-mkr@ara-mkr⭐ 133 stars· last commit 2mo ago· 0 open issues

Turns open-ended requests into things to think WITH instead of answers to accept. Audits the hidden assumptions inside a topic, inverts them into sharp "what if" provocations, branches each one outward, and delivers a fully-expanded mind map image plus the written wonderings. Fire this when the person signals they want to open up a space and think alongside you — "wonder about X", "what are the weird angles on X", "help me think about what this could be", "I want to explore, not decide yet" — or when they invoke /wonder or /wonderpill. Do NOT fire when the same topic is attached to a request for concrete, usable, or decided output: a named deliverable, a count ("give me 5 names"), a deadline ("ideas I can ship this week"), or a "which / what should I pick" question — those want straight answers, not a wonder pill. When it is genuinely unclear which they want, this skill opens by asking one line rather than branching. Not for factual lookups or executing a plan already chosen.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐⭐ 133 on GitHubGitHub ↗

Popular

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README


Ask Claude for ideas and you get a list. Install Wonder Pill and you get a map of the questions you didn't know you were standing on — plus an interactive mind map you can drag around, showing where every thought came from and which ones got thrown away.

Not an answer. A different kind of side effect.


Read this part first

Wonder Pill does not generate good ideas. It is not supposed to.

This matters enough to say plainly, because the failure mode of tools like this is someone installing it, reading the output, thinking "half of this is nonsense," and concluding it's broken. It isn't broken. Half of it being nonsense is the design.

What Wonder Pill produces is raw material for your own thinking. A stepping stool. Some of what comes out will be wild. Some of it will be impractical. Some of it will be, honestly, dumb — the kind of thing you'd be embarrassed to say out loud in a meeting. That's the cost of reaching past the obvious, and it's a cost worth paying, because the obvious answers are the ones you'd have found anyway without any tool at all.

Here's the reasoning. Language models are trained to predict likely continuations. Ask one for "ideas" and you get the statistically likeliest ones, which is another way of saying: the ideas everyone else already got. Every tool built on top of a model inherits that pull toward the center of the distribution. The only way out is to deliberately aim at the tails — and the tails contain both the genuinely novel and the genuinely stupid, because that's what "unlikely" means. You cannot filter for one without losing the other.

So Wonder Pill doesn't try. It generates loosely, marks how far each thread has drifted from reality, and hands you the whole spread. You are the filter. That's not a limitation being apologized for — it's the correct division of labor. You know your budget, your deadline, your skill level, your taste, and what would actually be interesting to you. The tool doesn't and can't.

A few honest expectations:

  • Roughly a third of any given map will be useless. Expected. Look at it and move on.
  • A third will be interesting but not usable — right shape, wrong context. Still valuable: it usually tells you something about the problem.
  • A third will be worth pulling on. That's a good yield for something that took thirty seconds.
  • The most useful output is often not a what-if at all but a gut-check line — the note about where the real difficulty hides. Several times in testing, that line reframed what a project actually was. Watch for those.
  • If everything on the map seems sensible, something went wrong. That means it collapsed back toward the consensus answers, which is the exact thing this exists to escape.

Judge it by whether it got you thinking somewhere you wouldn't have gone. Not by whether every branch was correct.


The problem it solves

Ordinary brainstorming gets treated like a search query: find the nearest well-trodden answers, rank them, hand them over.

> give me science fair ideas

1. Build a solar oven
2. Test which paper towel is most absorbent
3. Grow plants under different colored lights
...

Three things just went wrong:

  1. You became the chooser, not the thinker. Your job is now to evaluate someone else's list — which is a much smaller job than the one you actually wanted.
  2. You got anchored. Everything you think next is a variation on "solar oven." The first answer eats the space.
  3. It never left the training distribution. Those are the likeliest answers. That's not a bug in the model, it's what the model is for — which is precisely why you need something pushing the other direction.

Wonder Pill attacks all three by changing the deliverable. Instead of ideas, you get provocations to think with.


What it actually does

> give me science fair ideas

seed: nobody grades a project that isn't finished
   ↓
assumes: a project has to be finished to be judged
→ what if the project were a thing still running — measurements
  arriving during the judging, no known result yet?
   ├─ and the judges watched it change while they stood there
   ├─ and "the result" was whatever it happened to be at 2:47pm
   └─ and you genuinely didn't know if it would work
        └─ so what does a poster board even show?
  gut-check: only interesting if the hard part is the
  unfinishedness, not the topic

scrapped: what if it ran for a year?
  derivation: inverts the deadline
  flaw: the deadline is a hard wall, not a thing you can invert
  judgment: scrapped for generativity — there's nowhere for
  the thread to go once you're standing in "no deadline"

Every what-if is derived by inverting a named assumption — never invented freely. That single constraint is the whole trick, and the reason the output isn't the usual vague "what if you thought bigger?" filler.

The three-part deliverable

PartWhat it is
🗺️ Interactive mind mapDrag to pan, zoom, click any node for its gut-check. Every node states itself in plain language, so the map reads on a first pass without clicking. Fully expanded, nothing hidden behind a reveal. Shows seeds, dead ends, cross-links, and uneven depth.
📝 Orientation paragraphNames the throughlines — which tension kept recurring, where it went feral. Not a summary of the nodes.
🌱 Written wonderingsPremise → What if → tendrils → gut-check, for reading instead of scanning.

And then it stops. No ranking, no "here's my favorite," no quiet convergence back into a recommendation. If you want to land on one, you say so — and then it re-runs the whole audit on just that branch.


What's on the map

The map is deliberately not a tidy tree radiating evenly from a center. Real thinking isn't uniform, and a map that pretends otherwise throws away the most interesting information.

  • Seed nodes sit outside the branch they caused, further from the center than their own consequence. This is where "why did it think that" lives — a real fact, a historical precedent, an oddity it found while looking around. The map reads inward as well as outward.
  • Uneven depth. One branch gets a single hop because the thread ended there. Another goes four deep because it kept opening. A map where every branch is exactly three deep is a map that stopped thinking on a schedule rather than when it ran out of thread.
  • Scrapped what-ifs float detached at the edges, struck through, showing where it came from, what's wrong with it, and why that was judged disqualifying — three separate fields, not one blended reason. Kills can only happen

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • SKILL.md7.9 KBupstream ↗
    ---
    name: wonder-pill
    description: Turns open-ended requests into things to think WITH instead of answers to accept. Audits the hidden assumptions inside a topic, inverts them into sharp "what if" provocations, branches each one outward, and delivers a fully-expanded mind map image plus the written wonderings. Fire this when the person signals they want to open up a space and think alongside you — "wonder about X", "what are the weird angles on X", "help me think about what this could be", "I want to explore, not decide yet" — or when they invoke /wonder or /wonderpill. Do NOT fire when the same topic is attached to a request for concrete, usable, or decided output: a named deliverable, a count ("give me 5 names"), a deadline ("ideas I can ship this week"), or a "which / what should I pick" question — those want straight answers, not a wonder pill. When it is genuinely unclear which they want, this skill opens by asking one line rather than branching. Not for factual lookups or executing a plan already chosen.
    ---
    
    # Wonder Pill
    
    ## What this skill is for
    
    Ordinary brainstorming gets treated like a search query: find the nearest well-trodden answers, rank them, hand them over. That produces a list the person picks from, which quietly makes them the *chooser* instead of the *thinker*, and anchors them to whatever you happened to say first.
    
    This skill produces something different: **provocations to think with.** Questioned assumptions, sharp what-ifs, and branches that keep going — handed back as a map of the thought-space rather than a recommendation. The person stays the thinker. Nothing converges unless they ask it to.
    
    ## The one failure mode that matters
    
    The thing that kills this skill is **"generic wild"** — what-ifs that *sound* expansive but have no hook to pull on. "What if plants were different?" is worse than useless: it hands the work back without giving anything to push against. "What if plants could hear?" is alive, because you can immediately feel what would have to change.
    
    Everything below exists to force specificity. The central mechanism:
    
    > **Never invent a what-if freely. Always derive it by inverting a named assumption.**
    
    That traceability is the whole trick. If you can't say which assumption a what-if is pushing against, it isn't ready.
    
    ---
    
    ## Before you run: is this actually a wonder-pill ask?
    
    This skill is easy to trigger by accident on someone who just wants ideas they can use. Check first:
    
    - **If the request clearly wants concrete or decided output** — a named deliverable, a count, a deadline, "which should I pick" — don't run. Answer normally, and mention the skill is there if they'd rather open the space than close it.
    - **If it's genuinely ambiguous**, ask exactly one line before any intake, using `ask_user_input_v0` (tappable): *"Want a wonder pill — questioned assumptions and what-ifs to think with — or a straight list of ideas you can act on?"* Only start branching if they pick the wonder pill.
    - **An explicit `/wonder`, `/wonderpill`, or "wonder about X" skips this check.** They asked for it by name; go straight to Stage 0.
    
    ---
    
    ## Stage 0 — Intake
    
    Ask **three questions, no more**, before any thinking. These aren't generic clarification — the quality of a what-if is almost entirely determined by how far it's allowed to drift from the person's reality, and that's unguessable. "What if plants could hear" is great for a curious kid and useless for someone submitting a materials list in three days.
    
    Use `ask_user_input_v0` (tappable options are much easier than typing):
    
    1. **Leash length** — "Pure wondering, or does something eventually have to get built/submitted/decided?" → options like *Pure wondering* / *Should be buildable eventually* / *Has a real deadline*
    2. **Hard walls** — "Anything I shouldn't bother questioning?" → options like *Budget* / *Timeline* / *Materials on hand* / *Nothing, go wild*
    3. **Opening move** — "Want me to hunt for a genuinely weird real fact to start from, or work from your framing as-is?" → *Go find something weird* / *Start from my framing*
    
    **Skip intake entirely** if the request already answers all three. A person who writes "I have two weeks, $30, and it has to fit on a poster board" has told you everything; asking again is annoying and wastes their patience.
    
    ---
    
    ## Stage 1 — Oddity hunt (once per session only)
    
    If Stage 0 gave permission, take **one cheap pass** to find a genuinely odd, specific fact or unresolved tension in the topic. Search if that helps. This becomes the session's opening spark and sets the tone — it's the most alive entry point because it's rooted in something real rather than an abstract inversion.
    
    Two rules:
    
    - **Once per session, never per branch.** Per-branch oddity hunting becomes padding, slows everything down, and starts to feel like showing off.
    - **Fail fast.** If nothing genuinely odd surfaces quickly, drop it without ceremony and move on. A forced "huh, interesting" is worse than not doing this at all.
    
    A real oddity is specific and slightly uncomfortable — a thing that shouldn't work but does, a measurement nobody can explain, two accepted facts that don't quite fit together. Not a trivia factoid.
    
    ---
    
    ## Stage 2 — Assumption audit (the backbone)
    
    Surface **3–5 load-bearing assumptions** buried in the request. Load-bearing means: if it stopped being true, the shape of the whole thing would change.
    
    For "science fair project," the buried assumptions might be:
    - it needs a physical demo
    - it needs results measurable in one sitting
    - one person builds it
    - it uses materials you can buy
    - the judges have to understand it in three minutes
    
    Rules that keep this honest:
    
    - **State each assumption plainly as a premise, not as a question.** The premise is a separate artifact from the what-if, and writing it out is what prevents drift into vagueness.
    - **Drop anything the person named as a hard wall.** Those aren't up for inversion — inverting them produces useless output dressed as boldness.
    - **Prefer the assumptions nobody says out loud.** "Needs to be safe" is stated. "Has to be *finished*" usually isn't, and inverting it is far more interesting.
    - **Then invert each one. The inversion IS the what-if.** One per assumption. Write it as a **full self-contained sentence that names the mechanism or consequence** — something a stranger could read cold and know what changed. "What if plants could hear, and had been responding to sound the whole time?" — not "plant hearing". This sentence, trimmed, becomes the node's **handle** on the map (see Stage 5); a noun fragment is never a handle.
    - **Keep the seed.** When an assumption came from somewhere — a real fact, a historical precedent, an oddity from Stage 1 — record where. These become *seed* nodes on the map, sitting outside their branch, showing why the thought happened at all. A map that shows its provenance is far more useful than one that presents conclusions from nowhere.
    
    ### Good vs. bad inversions
    
    | Assumption | Weak what-if (generic wild) | Strong what-if (has a hook) |
    |---|---|---|
    | A project has to be finished to be judged | What if it weren't finished? | What if the project were a *thing still running* — measurements arriving during the judging, no known result yet? |
    | Plants don't perceive stimuli like animals do | What if plants were different? | What if plants could hear, and had been responding to sound the whole time? |
    | The experiment happens where you are | What if location changed? | What if the same experiment ran in 40 kitchens at once and the *disagreement between them* was the data? |
    
    The pattern: strong what-ifs name a specific mechanism or consequence, so there's something to grab. Weak ones just negate. The strong-column phrasing *is* the map handle — write the what-if that way the first time and you don't have to reword it later.
    
    Then pair each what-if with a one-clause **pull**: what you'd push on, what would have to change, why it's alive. "…and every acoustics c
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/ara-mkr-wonder-pill.md

// REPO STATS

133 stars
0 open issues
Last commit: 2mo ago