$npx -y skills add tmchow/illo-skill --skill illoCreates original editorial illustrations where a recurring mascot character performs the idea — one caught scene by default, a hand-built explainer diagram (a flow, fan-out, timeline, loop, or stack) when the structure itself is the point, or a transparent character cutout (pose-
| 1 | # Illo |
| 2 | |
| 3 | Make original, distinctive editorial illustrations for written content. One |
| 4 | image explains one idea: a key judgment, a flow, a before/after, a trap, a |
| 5 | loop. A **recurring mascot** is the one performing the idea in every scene — |
| 6 | the subject, never decoration. When one idea advances through stages, it can |
| 7 | be a **mini-comic**: 2–4 panels inside a single image. And when the idea is |
| 8 | itself a traceable structure — a pipeline, a fan-out, a timeline, a loop — |
| 9 | it can be an **explainer**: the same mascot and look drawing the structure |
| 10 | as a hand-built sketch-diagram with arrows and callouts |
| 11 | (`references/composition.md`, "Two registers"; editorial scene is always |
| 12 | the default). Or a **character cutout**: the mascot alone on a transparent |
| 13 | PNG for downstream overlay — pose and contact continuity only, no idea, no |
| 14 | text, no environment (`references/cutout.md`). |
| 15 | |
| 16 | This is a configurable house style, not a generic image generator. The |
| 17 | **methodology is the constant**; the **character pack and palette are the |
| 18 | parameters** — and a character pack carries its **style** with it: one look |
| 19 | per pack, chosen from the bundled look library (riso — grainy halftone, |
| 20 | ink-layer offset, paper grain, one bold softly-rounded outline — plus |
| 21 | blueprint, woodcut, pixel, clay, manila, chalk, phosphor, enamel, |
| 22 | gouache, felt, diorama, sketchbook, bricks, fizz, and bloom) or a custom style file. The default mascot is |
| 23 | **Blot**, a deadpan ink-drop in riso. Palettes come |
| 24 | from presets, the user's own palette file, or one derived color. Whatever the |
| 25 | parameters, it is intentionally not a photo — with one deliberate exception, the |
| 26 | `bricks` look, a toy-brick photography style — not a logo, not a corporate |
| 27 | infographic, not a formal flowchart, not a UI mockup. |
| 28 | |
| 29 | ## Use cases — route the request |
| 30 | |
| 31 | | The user wants | The path | |
| 32 | |---|---| |
| 33 | | **Illustrate an article / post / newsletter / URL** | Steps 0–7: route the source first (thesis → coverage: hero / hero+set / set / mini-comic — `references/composition.md`, "Source routing"), then shot list (hero row + anchors), one image per anchor, interleave by placement. | |
| 34 | | **One image for a single concept** | Step 1 concept branch (up to ~3 quick questions if the idea is thin), then a single image. | |
| 35 | | **Surprise / random** — "surprise me", "random", "surprise me with art quote using bray" | Read `references/surprise.md` in full (character + register resolved there — ignore `defaultCharacter`), then Steps 0 + 3–7 as one headless image: invent or fetch a safe **saying** (sense-bar originals; multi-source verified citations only), deliver saying + image. Poster titles default off; mini-comics still get per-panel labels. | |
| 36 | | **A sequence — process, before→after, fail→fix** | One **mini-comic** when the progression sits in one place (shape routing in `references/composition.md` — the idea picks the shape, the destination never does). | |
| 37 | | **A traceable structure** — "show the flow", "diagram the pipeline", "map the steps", "as an explainer" | The **explainer register** (`references/composition.md`, "The explainer register"): a hand-built flow / fan-out / timeline / loop / stack / system slice in the active look, the mascot a working part of it. Also reachable without the phrases when a unit's thesis IS the structure (the register gate). | |
| 38 | | **Social-ready art for X posts / article body images** | 16:9 (or 1:1 when square is explicitly useful), bold `ink-punch`, watermark with the `x` handle if configured or asked. | |
| 39 | | **X Article banner / hero image** | Use the unique banner format: **1536 × 640 px** when the user asks for an X Article hero/banner. Prompt and render through the normal `illo.py generate` image pipeline, with normal, undistorted character/object proportions and crop |