# illo skill examples

HTML: https://illo-skill.com/examples.html

Four registers the illo skill actually rendered — no manual editing of the pixels.

## Editorial scenes (default)

Hand the skill a post and it pulls the load-bearing moments, then renders one scene per moment so the article has one voice: one character, one palette.

Examples on the site include scope creep as a leaning crate tower, many inputs funneling into one decision, and replatforming a bridge under live traffic.

Ask: `/illo scope creep has a smell`

## Mini-comics

2–4 panels in a single image when the idea is a story beat (fail→fix, before→after) — stuck → slice → shipped. Same character and key object in every panel. A named pipeline is labeled stages inside explainer, not this register.

Ask: `/illo stuck → slice → shipped as a mini-comic`

## Explainer diagrams

One register for labeled stages, flow, fan-out, timeline, loop, stack, or system slice. Use only when the structure itself is the point. A flowchart or labeled workflow locks labeled stages — a named pipeline, not a story beat. Arrow notes sit on the arrows: a verb on the main flow, a condition on the return.

Ask: `/illo how a book gets published explainer diagram`
Ask: `/illo using Blip, make a flowchart of how a newsletter issue ships`
Ask: `/illo Sort incoming mail into keep, later, and trash as a fan-out, using Blip`
Ask: `/illo Diagram the pipeline from a raw idea to a shipped tool. Use Forge.`

## Character cutouts

Transparent PNG of the mascot alone — pose and contact continuity, no scene or text. For slides, docs, or compositing.

Ask: `/illo blot cutout waving`

See the guide for when to pick each register: https://illo-skill.com/guide.html