djfksjd/imagination-octo/imagination-octo-engine
Claude Code and agent skill by djfksjd/imagination-octo
- community
Checking that the SKILL.md file is still in the repository.
Generate several non-obvious, useful ideas without sacrificing the user's brief. Use only when the user explicitly invokes imagination-octo-engine while it is being evaluated, especially for concepts, premises, mechanics, products, services, worlds, rituals, or when previous ideas feel generic. Not for factual work, routine tasks with a known conventional answer, or developing an idea the user has already selected.
Install
npx vskill@latest install djfksjd/imagination-octo/imagination-octo-engineSKILL.md
The same SKILL.md was published earlier as djfksjd/imagination-octo-engine/imagination-octo-engine.
Imagination Octo Engine
Produce useful surprise: an idea should feel non-obvious after it is understood, yet clearly serve the brief. Treat fit as a veto. Randomness, strangeness, invented vocabulary, and distance from the obvious are not goals by themselves.
Work in the user's language. Keep the search private unless the user asks to see it.
Frame the search
Extract:
- the outcome and audience;
- the non-negotiable constraints;
- what would make an idea valuable rather than merely unusual;
- examples or mechanisms the user has already rejected.
Ask at most one concise question when a missing answer would materially change the search. Otherwise proceed. Do not require the user to construct a ban list or choose a mode.
If a conventional answer is clearly the best fit, say so and give it. Do not manufacture novelty where novelty has no value.
Generate independent candidates
Search in three passes. Scale the number of rough candidates to the task; three to five per pass is usually enough.
Candidates produced in one context anchor on each other, so separate the passes whenever the host allows it. If you can dispatch sub-agents or parallel workers that start without this conversation, including through a tool you must look up first, do it for every brief: give each pass to its own worker, all at once. Send each worker only the brief with its non-negotiables and rejected mechanisms, in the user's language, plus its one pass instruction. Ask for four or five rough candidates as plain sketches: what happens, the mechanism that makes it work, and what could break it. Tell no worker what another found. Only when the host has no such workers, run the passes yourself and finish each before starting the next.
- Direct pass: Generate strong, concrete, high-fit answers without trying
to be strange. This protects the brief from being lost during divergence.
- Mechanism-transfer pass: Borrow causal mechanisms from unrelated
domains, not their nouns or aesthetics. Ask what the source mechanism does, why it works there, and what would play the same functional roles here.
- Premise-shift pass: Change one hidden assumption at a time while
preserving every non-negotiable. Prefer shifts in actor, ownership, timing, unit, information flow, or incentive over arbitrary world changes.
When field-relative novelty matters and research tools are available, inspect the nearest existing approaches and a few remote domains before the transfer pass. Use retrieved material as raw material, not as authority. Never delay a simple creative request with unnecessary research.
Pooled candidates are raw material, not a draft. Workers overlap, and a rough sketch can hide a constraint violation, so everything below applies to each of them. Add a candidate of your own when the pool lacks a mechanism family.
Keep the candidates independent. Do not force unrelated survivors into one hybrid. Combine ideas only when a single causal mechanism genuinely supports both.
Cull by failure, then compare
Reject a candidate when:
- it violates or quietly weakens a non-negotiable;
- its novelty disappears when names, visuals, or invented terminology are
removed;
- it is a familiar mechanism with a new theme;
- it combines distant elements without a causal bridge;
- it needs a long explanation before anyone can see why it serves the brief;
- it differs from another survivor only in presentation.
Compare survivors pairwise rather than assigning absolute self-scores. Use this order:
- Fit: Does it answer the actual brief? A loss here eliminates it.
- Mechanism: Is there a specific reason it could work or remain coherent?
- Useful surprise: Does understanding the mechanism make the idea more
interesting rather than reveal it as random?
- Portfolio difference: Does it add a genuinely different causal shape to
the set?
Do not select one winner internally and fill the remaining slots with weaker decoys. If fewer than three ideas survive, search again from a new mechanism family.
Prove each survivor
Before choosing the final portfolio, make a private proof card for each survivor:
- Constraint evidence: point to the component or action that preserves each
non-negotiable; absence of a violation is not evidence.
- Causal chain: identify the actor, action, changed state, and resulting
value. If a link is only a slogan, reject or repair the candidate.
- First encounter: simulate one ordinary moment in which the audience uses
or experiences the mechanism and can notice its consequence.
- Decisive uncertainty: name the one unknown most likely to make the
mechanism fail despite good execution.
For a story, drama, or other character-driven premise, replace the causal chain and first encounter checks above with:
- Dramatic cause: identify who legitimately wants what, how this premise's
distinctive mechanism makes those wants incompatible, and the consequential choice that follows.
- Changed next choice: trace how that choice alters what someone can do,
know, or reasonably want next. Reject a premise that only repeats the same dilemma at a louder volume or depends on withheld information.
Keep these cards private. Use them to reject attractive sketches that cannot demonstrate fit or survive a concrete moment, not to make the delivered answer longer. A survivor's visible mechanism, fit, and risk should be the compressed result of this proof.
Deliver a portfolio
Return three to five ideas by default, ordered for the user's decision rather than from safest to strangest. Adapt the presentation to the task. A compact default for each idea is:
- the idea in one or two sentences;
- the mechanism that makes it work;
- why it fits this brief;
- the most important risk, tension, or unknown.
Keep the first response easy to scan. Do not add a universal lore section, scene, administrative consequence, novelty claim, scoring rubric, or account of the hidden process unless the task actually needs it.
End with one discriminating question that helps the user choose among the surviving directions. When the user chooses, deepen that direction instead of regenerating the whole portfolio. If they want a full concept review, hand off to imagination-octo-brainstorming when it is available. Do not choose on the user's behalf or automatically chain the workshop; their choice is the decision boundary between divergence and development.
Regenerate without creating a house style
When the user rejects the set:
- identify the rejected mechanisms, not every word or surface element;
- preserve the brief and its non-negotiables;
- switch the search basis: use a different source domain, actor, time horizon,
or premise;
- generate a new independent portfolio;
- state in one sentence what changed in the search.
Do not merely add more constraints, increase weirdness, invert everything, or repeat one signature move such as bodiless processes, debts, retroactive laws, or bureaucratic consequences.
Guardrails
- Never claim that an idea is unprecedented. When that distinction matters,
name the closest known approach and state the operational difference.
- Do not use cruelty, degradation, or shock as shortcuts to originality.
- Do not treat the model's first associations as authoritative evidence about
what is obvious to the user or the field.
- Do not let a method become the product. The user should receive better ideas,
not proof that a pipeline ran.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/imagination-octo-engine/SKILL.md
Popularity
- Repository stars
- 1
- 7-day trend score
- 8
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/djfksjd/imagination-octo/imagination-octo-engine)