scenario-storyboards
Use when a story must unfold across a sequence of Scenario images: a comic page or strip, manga or webtoon panels, a children's storybook, a film, game, or ad storyboard, animatic pre-viz frames, or any shot list where the same characters and world must persist from panel to panel and dialogue must…
Install / Use
npx skills add scenario-labs/skills --skill scenario-storyboardsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OtherSupported Platforms
Our assessment of scenario-storyboards
scenario-storyboards scores 82/100 on our quality scale, 276th of 330 Other skills we index.
Its SKILL.md is 7.1 KB long, split into 5 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 29 days ago, so scenario-storyboards is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-09. Automated pattern scan on 2026-11-09. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
scenario-storyboards compared with similar skills
All 4 of these similar skills score higher than scenario-storyboards; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-storyboards (this skill)by scenario-labs | 82 | 1.0k | 29d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| LocalAIby mudler | 100 | 50.4k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install scenario-storyboards?
- Run
npx skills add scenario-labs/skills --skill scenario-storyboards. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-storyboards work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is scenario-storyboards safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is scenario-storyboards still maintained?
- The repository was last updated 29 days ago, so scenario-storyboards is actively maintained.
Skill content
View source on GitHubname: scenario-storyboards description: "Use when a story must unfold across a sequence of Scenario images: a comic page or strip, manga or webtoon panels, a children's storybook, a film, game, or ad storyboard, animatic pre-viz frames, or any shot list where the same characters and world must persist from panel to panel and dialogue must stay legible. Keywords: storyboard, comic, panel, sequential art, storybook, shot list, pre-viz, animatic, scene to scene, character consistency." license: MIT
Scenario Storyboards and Comics
Overview
Asked for a comic page, an agent prompts one model for "a page with six panels" and gets a page it
cannot fix: uneven panel geometry, a hero whose face changes between cells, dialogue rendered as
garble. The unit of generation is the panel, never the page. Script first, lock the cast, one
model_run per panel anchored to the same references, letter in post, assemble the page last.
Connection and the core loop: see the scenario skill. Character lock: scenario-consistency.
Per-model image contracts: scenario-image. Lettering: scenario-text-overlay. If a sibling skill
named here is missing from your available skills, load it with skill_get (Scenario MCP) or ask the
user to install it (https://github.com/scenario-labs/skills#install); unattended, proceed from tool
schemas and flag the gap.
Quick reference
| Stage | Do |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| 1. Script | A beat table before any generation: per panel, the shot size and angle, the action, the setting, the dialogue |
| 2. Cast and style | One approved hero image per character plus a style pick (search with query="comic" surfaces style LoRAs); write each baseline |
| 3. Panels | One model_run per panel: byte-identical baselines plus that panel's clause, references wired per the schema |
| 4. Review | jobs_wait, then check identity panel over panel before lettering |
| 5. Letter | Dialogue, captions, and sound effects as scenario-text-overlay cards composited onto text-free art |
| 6. Assemble | Page layout and contact sheets: layer composition in scenario-video-assembly (Image Studio), or the grid tool in scenario-image-editing |
Label the panels the way a shot list does, in that order: number, shot size, angle, lens or camera move, then the action with each character's frame side and facing. Arrange them as coverage rather than a row of pictures: open on a master that establishes the geography, hold one side of the axis so screen direction never flips, climb the size ladder as tension rises, and punctuate with an insert or a reaction.
A storyboard headed for animation stops at stage 4. Approved panels become first frames for
image-to-video (scenario-video), one clip per shot, when each shot stands on its own. When the
movement itself has to carry across the cuts, animating panels independently resets the performance
at every one: that sequence belongs in the scenario-seedance-storyboard skill, which chains each
shot's exit pose to the next shot's entry.
Worked example: a six-panel comic page
- Script the page as a table: panel, shot size and angle, lens or camera move, action, dialogue and captions. The action column holds only what a camera sees: a thought, a smell, or backstory renders as nothing, so it becomes visible evidence or a caption. Dialogue and captions are written down here, never prompted into the art.
- Cast lock: generate or upload the hero and iterate until approved; unattended, the script's own
character description stands in for the approval, so take the candidate that matches it and
continue.
asset_displaythe hero and write its baseline enumeration (geometry, costume, palette by name or hex) perscenario-consistency. - Style:
searchwithtarget="models",query="comic",public=true; the public catalog carried comic-style LoRA hits at authoring time. Confirm the pick with the user (unattended, take it from the task instructions, else the first result in returned order), thenmodel_schema_getit for the reference field's name, cap, and cardinality. No reference field that fits the cast? Capabilities may advertise adapters the schema never exposes; the schema wins. Keep the pick for hero generation andrecommenda reference-capable model for the panels, restating the style line in every prompt. - Six
model_runcalls. Each prompt is the style line, the character baseline, and the setting line (location, time of day), all byte-identical across the panels that share them, plus that panel's clause (shot, action), plus "clean art, no lettering, no speech bubbles". A dropped setting line breaks continuity the same way a dropped baseline breaks identity. Wire the hero reference as the schema says: an array only underarray: true. A batch-count field repeats one prompt, so it cannot carry per-panel clauses. jobs_waiton the six jobs, re-calling withpending_job_ids. Review each panel against the hero; fix drift by tightening that panel's enumeration and re-running from the baseline, never by chaining from a neighboring panel.- Letter with
scenario-text-overlay, composite the cards as layers, assemble the page, then file panels and page in a collection (scenario-asset-analysis).
Common mistakes
- Generating a page in one run: panels from a single prompt cannot be regenerated one at a time, so one bad panel costs the whole page.
- Prompting dialogue: generated lettering drifts and garbles; keep the art text-free and letter in post.
- Chaining panel to panel: feeding panel three panel two's output compounds drift; anchor every panel to the same approved hero.
- Writing "same character as before": there is no memory between calls; restate the full baseline every time.
- Carrying a lasting change (a new costume from panel four on) as a per-panel clause against the old hero: the reference pulls the old costume back. Generate a second hero from the first with the change described, approve it, rewrite the baseline, and anchor the later panels to it.
- Animating unapproved panels: image money is cheap, video money is not; gate the expensive stage
the way
scenario-video-adsprices its board first. - Merged characters: with several heroes in one panel, state each reference's role in the prompt, check the schema's reference cap fits the cast before planning the scene, and keep extras generic and unnamed; only cast that must stay recognizable gets a baseline and a slot.
- Abandoning a moderation-blocked action beat: providers can reject a weapon or fight panel
(
moderation_blocked); soften that panel's clause, de-emphasizing the weapon, and re-run from the baseline.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
LocalAI
50.4kLocalAI is the open-source AI engine. Run any model - LLMs, vision, voice, image, video - on any hardware. No GPU required.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
