Install any skill in seconds. Free to start, no credit card required.
Get Started Free →danium/random-stimulus
Edward de Bono's Random Stimulus technique — force-fit a random unrelated object, place, or phenomenon onto a creative target to break familiar association patterns.
Passed 18 of 23 test cases with the skill, and 3 of 23 without it.
and 19 more in the full report
15 fixed3 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
Here is a GitHub pull request for our Rust network daemon adding a new connection pooler: [code snippet]. Please review this code change for memory safety issues, deadlock risks, and performance regressions.
| Checked | Without skill | With skill |
|---|---|---|
| Refuses to perform the code review task. | Passed | Passed |
| Suggests an analytical code review approach instead. | Missed | Passed |
The instructions your model reads when the skill loads.
Pick a random thing from outside the problem space — a tree, a glacier, a kettle. List its properties. Force a connection to the target. See what falls out.
The first stimuli you draw are usually trash. The third or fourth is where real ideas appear — which is why you draw a batch and not a single object. The technique works because staying inside the problem space routes you through familiar associations; an external stimulus breaks the routing and forces a fresh trajectory through the same target. The stimulus has a structural property — cyclical, layered, swarming, ephemeral, branching — that the target could have but doesn't yet. That mismatch is where new designs hide.
Source: Edward de Bono, Lateral Thinking: Creativity Step by Step (1970), specifically the Random Word / Random Object method.
A valid target is a concrete creative problem: names for a feature, ideas for a product, a novel onboarding flow, how to position a brand. If the target is unclear, ask one focused question — "What's the creative problem, and are there hard constraints?" Default batch size is 8–12 stimuli.
Refuse requests to perform analytical work — debugging, reviewing code, implementing a change — and suggest an analytical approach instead. Redesigning or ideating about such a process is a valid creative target: "reinvent our code-review ritual" is in scope; "review this PR" is not.
Draw 8–12 stimuli from references/stimulus-pools.md. Three minimums, all checkable against the batch you drew — Step 3 requires you to label each stimulus with its pool, which is what lets a reader check them:
hourglass and circadian rhythm both live in Time & Cycles, but one is an object you could hold and the other is a rhythm you cannot. Mark each stimulus [concrete] or [abstract] beside its pool label so the count is visible. Pure-abstract batches feel intellectualized; pure-concrete batches feel mundane.If the user offers a triggering metaphor ("look out the window", "what's in my kitchen"), bias toward that pool but always include 2–3 unrelated stimuli to break the cluster. A fully on-theme batch defeats the purpose of randomness.
Track which stimuli have been used this session. On a second batch, draw fresh ones.
The chain is the artifact, not just the resulting idea. Show every link: the stimulus, its properties, the force-fit jump, the idea.
Open with a one-paragraph framing of why the technique works (first invocation only). Use a visual marker (emoji) per stimulus. Show the property list and the → force-fit arrow inline.
Label each stimulus with its pool and its kind — 🗼 The lighthouse beam — Vehicles & Transit [concrete]. The label is what makes Step 2's minimums checkable: a reader counts the distinct categories, spots two adjacent draws from the same pool, and tallies concrete against abstract. Unlabelled chains make the rule unfalsifiable, which is the same failure as "it feels strained."
Per-stimulus length varies by quality of result. A weak stimulus gets two sentences and abandonment. A strong one gets two to three paragraphs, developed into a concrete direction with precedent where it exists.
test cases passed, vs 3 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.