scenario-inspiration
Scenario Inspiration
Overview
Asked for inspiration, an agent averages. It returns the most typical answer for the brief, so every user with a similar brief gets the same look. This skill trades that for four phases: prime, widen, choose, board. Connection and scope: see the scenario skill in this repo. If a sibling skill named here is missing from your available skills, ask the user to install it (npx skills add scenario-labs/skills --skill <name>); unattended, proceed from tool schemas and flag the gap.
Four moves carry most of the value. Name the reflex answer for this brief and the answer of someone merely avoiding that reflex, then rule out both, because an agent told to be original lands on the second-obvious answer. Randomize the operator, never the subject: what varies is the transformation applied to the brief, and a random subject is just noise. When you generate candidates yourself instead of searching for them, ask yourself for a distribution rather than an answer, and work from its tail. Then make the user pick, because options that never resolve are a gallery, not direction.
Quick reference
| Phase | Do | Detail |
|---|---|---|
| 1. Prime | Locked constraints, the open axis, both reflexes, what counts as a hit | references/widen.md |
| 2. Widen | Four lanes plus wildcard draws; over-gather, near and far | widen.md, references/sources.md |
| 3. Choose | Three or four mutually exclusive directions one named axis apart, plus an escape hatch | references/choose.md |
| 4. Board | The pick becomes a collection, every reference annotated with its job | references/moodboard.md |
Four lanes feed phase 2. Ask the user first, for three things they already love and one they cannot stand; unattended, take those from the task instructions and continue without them if it names none. Then search with target: "assets" twice, once over the team's own work (public omitted) and once over the public catalog (public: true), and last the open web, which is not a search call. Public asset hits carried metadata.prompt, the wording that produced them, and target: "models" hits carried exampleAssetIds at authoring time: free style research either way. images: {like, unlike} steers by example in both directions.