Scroll Promo Site Builder
kangarooking/kangarooking-skills
Create a scroll-controlled cinematic product website with rich motion (动效网站) from product materials, reference pages or videos, and brand assets.
A skill your agent uses when a Seedance video must hold continuous movement across shots: dance choreography, fights, sports, or any performance where limbs teleport, feet slide, or motion resets at…
$ npx skills add scenario-labs/skills --skill scenario-seedance-storyboard -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install scenario-labs/skills scenario-seedance-storyboard --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/scenario-seedance-storyboard .claude/skills/scenario-seedance-storyboard && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "scenario-seedance-storyboard" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-seedance-storyboard into .claude/skills/scenario-seedance-storyboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-seedance-storyboard", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/scenario-labs/skills/tree/main/skills/scenario-seedance-storyboardType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add scenario-labs/skills --skill scenario-seedance-storyboard -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install scenario-labs/skills scenario-seedance-storyboard --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/scenario-seedance-storyboard .agents/skills/scenario-seedance-storyboard && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "scenario-seedance-storyboard" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-seedance-storyboard into .agents/skills/scenario-seedance-storyboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-seedance-storyboard", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add scenario-labs/skills --skill scenario-seedance-storyboard -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install scenario-labs/skills scenario-seedance-storyboard --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/scenario-seedance-storyboard .cursor/skills/scenario-seedance-storyboard && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "scenario-seedance-storyboard" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-seedance-storyboard into .cursor/skills/scenario-seedance-storyboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-seedance-storyboard", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/scenario-labs/skills.git --path skills/scenario-seedance-storyboard--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add scenario-labs/skills --skill scenario-seedance-storyboard -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install scenario-labs/skills scenario-seedance-storyboard --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/scenario-seedance-storyboard .gemini/skills/scenario-seedance-storyboard && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "scenario-seedance-storyboard" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-seedance-storyboard into .gemini/skills/scenario-seedance-storyboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-seedance-storyboard", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install scenario-labs/skills scenario-seedance-storyboardInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add scenario-labs/skills --skill scenario-seedance-storyboard -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/scenario-seedance-storyboard .github/skills/scenario-seedance-storyboard && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "scenario-seedance-storyboard" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-seedance-storyboard into .github/skills/scenario-seedance-storyboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-seedance-storyboard", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add scenario-labs/skills --skill scenario-seedance-storyboard -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install scenario-labs/skills scenario-seedance-storyboard --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/scenario-seedance-storyboard .opencode/skills/scenario-seedance-storyboard && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "scenario-seedance-storyboard" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-seedance-storyboard into .opencode/skills/scenario-seedance-storyboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-seedance-storyboard", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
scenario-seedance-storyboardA skill your agent uses when a Seedance video must hold continuous movement across shots: dance choreography, fights, sports, or any performance where limbs teleport, feet slide, or motion resets at…
Scenario Seedance Storyboard is an agent skill from scenario-labs/skills. Use when a Seedance video must hold continuous movement across shots: dance choreography, fights, sports, or any performance where limbs teleport, feet slide, or motion resets at every cut, or when turning a storyboard and character sheet into a multi-shot sequence that plays as one take. Keywords: storyboard to video, choreography, movement control, pose chain, timecoded shot script, first and last frame chaining, character sheet, multi-shot continuity, Seedance 2.5 and 2.0.
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `README.md`, `references/board-craft.md` and `references/chained-lane.md`).
It sits in Media & Creative, covering Comics and storyboards, AI video generation and Slides and decks. It works with Seedance. The repository describes itself as: Get production-ready images, video, audio, and 3D from any AI agent: skills that pick the right model, price before spending, and keep characters and brands consistent through… The licence is MIT.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit f6f8ab7. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npxFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Scenario Seedance Storyboard loads about 2.7k tokens when it runs, and up to ~8.3k if it reads all its reference files. Until then it costs about 127 tokens; SKILL.md has 1,424 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from scenario-labs/skills at commit f6f8ab7, republished under its MIT licence (© scenario-labs). 1,424 words, ~2,709 tokens.
.claude/skills/scenario-seedance-storyboard/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Prompted shot by shot, generated movement falls apart: limbs teleport, feet slide, and every cut resets the performance. So storyboard instead of prompting harder. What this delivers is continuous motion through the handoffs, not editorially distinct cuts: for cuts a viewer can feel, cut the delivered clip yourself with scenario-video-editing. Write a timecoded shot script, draw a character sheet and a numbered panel per shot, and hold one rule: every shot ends in the pose the next one starts from. Pinned boundaries leave nothing to reset, so the cuts play as one performance.
Connection and the core loop: the scenario skill; the Seedance parameter contract, conditioning traps, and sound lanes: the scenario-seedance skill; identity across stills and a reusable character sheet: the scenario-consistency and scenario-identity-library skills; a board or comic page that is itself the deliverable: the scenario-storyboards skill; splitting and rejoining shots: the scenario-video-editing and scenario-video-assembly skills. 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.
| Step | What | How |
|---|---|---|
| 1. Script | timecoded list, cast and setting agreed first | per shot: number, size, angle, lens or move, action verbs, entry and exit poses |
| 2. Plates | one image per performer who must stay recognizable, several angles; extras generic and unnamed | image model via recommend; one clean still of a real performer also works |
| 3. Briefs | one line per panel, coverage not pictures | master first, hold the axis, climb the size ladder, punctuate |
| 4. Panels | one model_run per panel | plates as references, light pencil line on bare paper, each at delivery ratio |
| 5. Gate | two passes per panel, then repair one panel | artifacts and differences, per board-craft |
| 6. Assemble | the approved panels into the board | model_scenario-compose-image at explicit coordinates |
| 7. Approve | script, plates, board shown to the user | reshoot by panel number; unattended, record and continue |
| 8. Frames | two or three photoreal key frames | same plates, delivery ratio; they set the delivered look |
| 9. Video | one scripted run, or chained runs | Seedance model_run, one of the two lanes below |
| 10. Check | the delivery is clean and carries its track | sample every half second, not only the cuts, and match each cut to its panel |
Label each panel as a shot list does: number, shot size, angle, lens or camera move, then three action verbs. Arrange them as coverage, not twelve pictures: open on a master that sets the geography, hold one side of the axis so screen direction never flips, climb the size ladder, and punctuate with an insert or a reaction. Adjacent shots share an edge by construction: shot 3's exit is shot 4's entry.
Draw the board light: thin pale line on bare paper, the setting in two or three quick lines, no rendered environment. A board drawn as a competing picture is treated as one, and its markings render into the delivery as objects, which no prompt clause can clean. Drawn light, the same markings transfer nothing, so numbers, captions and arrows can all stay on the board a human reviews. What carries that is prompt wording, not drawing: declare the marks as the director's planning guides rather than prohibiting them, and pass the key frames as concept art so appearance has a photographic source. Both are in video-prompt.md.
Panels are generated one at a time, so one bad panel costs one panel, and gated before any video run on two passes: an AI-quality score for artifacts, and a spot-the-difference against the plate. A board-level verdict is not the bar: panels average defects away.
File as you go: one collection per sequence, created before the first generation, holding plates, panels, repairs, board and video (board-craft).
Stop for approval before the first video run, with the key frames shown alongside the script, plates and board, and invite a reshoot by panel number; unattended, record the assumption and continue.
One scripted run. When the sequence fits one job's duration cap (30 seconds on 2.5 at authoring time), pass the plates, board and key frames as referenceImages and build the prompt to the seven-section shape in video-prompt.md. One generation carries the internal cuts: the plates hold identity, the pose chain holds continuity. Name aspectRatio; it defaults to adaptive here, so a portrait board hands back a portrait video. Reference mode anchors frame one to the base state of the reference world (see scenario-seedance), so a sequence that must open on an exact pose belongs in the chained lane.
Chained per-shot runs. Past the duration cap, when each shot needs its own control, or when the sequence must open on an exact pose: render each boundary pose as a still, then run shot N with image = still N-1 and lastFrameImage = still N, so adjacent shots share a frame both sides agree on. This excludes referenceImages, so the stills are a shot's only identity, and N shots cost N+1 stills and N runs. Each run also has a duration floor (4 whole seconds on 2.5 at authoring time), so N shots cannot total less than N times it, and more cuts than that means fewer shots or more seconds. The disciplines and the repair path are in references/chained-lane.md.
upload_asset (see the scenario skill). Show the board and the key frames to the user before going further.search with target="models", query="seedance", public=true. Hits rank by relevance, not generation, so scan them all for the newest non-deprecated member rather than the first: at authoring time model_bytedance-seedance-2-5 (re-discover each session), which takes the most references and holds identity best. Then model_schema_get for caps.model_run with dry_run=true and parameters={"prompt": "<the timecoded script>", "referenceImages": ["asset_dancer", "asset_board", "asset_key1", "asset_key2"], "duration": 24, "resolution": "1080p", "aspectRatio": "16:9"}; re-estimate after any change.wait=false, then jobs_wait, re-called with pending_job_ids on timeout. A timeout is not a failure and never justifies a second model_run.asset_display returns a link for video, not frames, so pull them locally or with model_scenario-video-to-image-seq (a fixed id: Scenario's single deterministic frame-extraction tool, so discovery would only re-derive it). Expect fewer cuts than scripted: most handoffs render as camera moves, so cut the delivered take at the twelve scripted points.generateAudio: false is the fallback, not the default.max_length, or timecodes past the duration cap: read both off model_schema_get before writing the script, since step 1 comes before discovery; an overrun is a 400, never a trim. Then send the run's scripted length as duration: its default is Auto (-1), which the schema defines only against a reference clip, so a timecoded script sent without it runs for an unstated length.© scenario-labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files (references) in skills/scenario-seedance-storyboard of scenario-labs/skills.
Open the folder on GitHubat commit f6f8ab7
Scenario Seedance Storyboard next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Scenario Seedance Storyboard this skillscenario-labs/skills | 946 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Scroll Promo Site Builderkangarooking/kangarooking-skills | 662 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Seedance 2.0 Storyboard Promptselementsix/elementsix-skills | 311 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Character Design with genmediafal-ai-community/skills | 251 | — | ~1.3k | Automated safety check: Pass | None | |
| Painterly 3D2 Cinema Promptsliucongg/liucong-skills | 248 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Seedance 2.5 Video PlannerAtlasCloudAI/awesome-seedance-2.5-prompts-skills | 234 | — | ~4.3k | Automated safety check: Pass | Custom licence |
kangarooking/kangarooking-skills
Create a scroll-controlled cinematic product website with rich motion (动效网站) from product materials, reference pages or videos, and brand assets.
elementsix/elementsix-skills
Interviews you about a video idea, then writes a timed shot-by-shot prompt for Seedance 2.0 using its image, video and audio reference syntax.
fal-ai-community/skills
Builds consistent characters, reference and expression sheets, outfit variations and character-to-video shots with the genmedia CLI while keeping identity stable.
liucongg/liucong-skills
Expands one sentence into a prompt package for painterly 3D-to-2D short films: story, 15-second segments, characters, scenes, Midjourney storyboards and Seedance video prompts.
AtlasCloudAI/awesome-seedance-2.5-prompts-skills
Plans and generates controllable Seedance videos by choosing a creative route first, from text prompts and storyboards to keyframe pairs, extensions and edits.
LearnPrompt/awesome-seedance
Plan and carry a Seedance video from brief through references, storyboard, generation handoff, shot-level review, and targeted repair.
scenario-labs/skills
A skill your agent uses when drawing or animating with Grease Pencil in Blender 5.x from Python: 2D or 2.5D illustration, frame-by-frame animation, a cutout or part-based 2D character, strokes with…
scenario-labs/skills
A skill your agent uses when grooming hair or fur in Blender with hair curves, such as a character hairstyle, animal fur, procedural fur in geometry nodes, or hair cards and mesh hair for games.
scenario-labs/skills
A skill your agent uses when lighting, rendering or compositing in Blender: light a character, product or hero shot, interior at dusk or night, three-point or motivated lighting, sun and sky, HDRI…
scenario-labs/skills
A skill your agent uses when creating a ChatGPT pet or Codex pet with Scenario: hatching an animated companion from a text idea, a character, mascot or brand cue, or reference photos and art; making…
scenario-labs/skills
A skill your agent uses when animating characters or scenes in Godot 4.7: AnimationPlayer clips and RESET, AnimationTree state machines and blend spaces built in code, Mixamo or glTF import, loop…
scenario-labs/skills
A skill your agent uses when adding or fixing sound in Godot 4.7: audio buses and effects, volume sliders, 'too many sounds', combat audio with hundreds of enemies, sounds clipping or distorting, 3D…
Works with
Categories
A skill your agent uses when a Seedance video must hold continuous movement across shots: dance choreography, fights, sports, or any performance where limbs teleport, feet slide, or motion resets at…. Scenario Seedance Storyboard is an agent skill from scenario-labs/skills. Use when a Seedance video must hold continuous movement across shots: dance choreography, fights, sports, or any performance where limbs teleport, feet slide, or motion resets at every cut, or when turning a storyboard and character sheet into a multi-shot sequence that plays as one take.
Scenario Seedance Storyboard fits situations like: A Seedance video must hold continuous movement across shots: dance choreography; any performance where limbs teleport; motion resets at every cut; turning a storyboard and character sheet into a multi-shot sequence that plays as one take.
Run `npx skills add scenario-labs/skills --skill scenario-seedance-storyboard -a claude-code`. Or copy the skill folder (skills/scenario-seedance-storyboard in scenario-labs/skills) into .claude/skills/scenario-seedance-storyboard in your project. Claude Code loads it when a task matches its description.
Run `npx skills add scenario-labs/skills --skill scenario-seedance-storyboard -a codex`. Or copy the skill folder (skills/scenario-seedance-storyboard in scenario-labs/skills) into .agents/skills/scenario-seedance-storyboard in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add scenario-labs/skills --skill scenario-seedance-storyboard -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scenario-seedance-storyboard, .gemini/skills/scenario-seedance-storyboard, .github/skills/scenario-seedance-storyboard and .opencode/skills/scenario-seedance-storyboard in your project.
Going by SKILL.md and its folder, Scenario Seedance Storyboard needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Scenario Seedance Storyboard is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.6k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Scenario Seedance Storyboard: Scroll Promo Site Builder (kangarooking/kangarooking-skills, 662 stars), Seedance 2.0 Storyboard Prompts (elementsix/elementsix-skills, 311 stars), Character Design with genmedia (fal-ai-community/skills, 251 stars) and Painterly 3D2 Cinema Prompts (liucongg/liucong-skills, 248 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
scenario-labs (a GitHub organization) maintains it in scenario-labs/skills, which has 946 GitHub stars. The repository holds 146 skills in this directory. The repository was last updated on October 10, 2026.
Source: scenario-labs/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.