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.
Turn a confirmed product or feature brief into a shootable 30–120 second explainer storyboard with a consistent entity roster.
Install Explainer Storyboard
$ npx skills add nodetool-ai/nodetool --skill explainer-storyboard -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nodetool-ai/nodetool explainer-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/nodetool-ai/nodetool.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/system-skills/explainer-storyboard .claude/skills/explainer-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 "explainer-storyboard" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/explainer-storyboard into .claude/skills/explainer-storyboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explainer-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/nodetool-ai/nodetool/tree/main/packages/system-skills/explainer-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 nodetool-ai/nodetool --skill explainer-storyboard -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nodetool-ai/nodetool explainer-storyboard --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/system-skills/explainer-storyboard .agents/skills/explainer-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 "explainer-storyboard" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/explainer-storyboard into .agents/skills/explainer-storyboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explainer-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 nodetool-ai/nodetool --skill explainer-storyboard -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nodetool-ai/nodetool explainer-storyboard --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/system-skills/explainer-storyboard .cursor/skills/explainer-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 "explainer-storyboard" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/explainer-storyboard into .cursor/skills/explainer-storyboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explainer-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/nodetool-ai/nodetool.git --path packages/system-skills/explainer-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 nodetool-ai/nodetool --skill explainer-storyboard -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nodetool-ai/nodetool explainer-storyboard --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/system-skills/explainer-storyboard .gemini/skills/explainer-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 "explainer-storyboard" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/explainer-storyboard into .gemini/skills/explainer-storyboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explainer-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 nodetool-ai/nodetool explainer-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 nodetool-ai/nodetool --skill explainer-storyboard -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/system-skills/explainer-storyboard .github/skills/explainer-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 "explainer-storyboard" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/explainer-storyboard into .github/skills/explainer-storyboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explainer-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 nodetool-ai/nodetool --skill explainer-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 nodetool-ai/nodetool explainer-storyboard --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/system-skills/explainer-storyboard .opencode/skills/explainer-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 "explainer-storyboard" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/explainer-storyboard into .opencode/skills/explainer-storyboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explainer-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.
Facts
- Skill name
explainer-storyboard- GitHub stars
- 560
- Token cost
- ~1.6k tokens
- SKILL.md length
- 878 words
- Files
- 1
- Skills in repo
- 127
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Turn a confirmed product or feature brief into a shootable 30–120 second explainer storyboard with a consistent entity roster.
- Explanatory product videos
- SKILL.md covers Truthful brief, Resolve entities before beats, Teaching arc and Deliverables, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Finished renders
What it does
Explainer Storyboard is an agent skill from nodetool-ai/nodetool. Turn a confirmed product or feature brief into a shootable 30–120 second explainer storyboard with a consistent entity roster. Use for explanatory product videos, not workflows, pipelines, or finished renders.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Media & Creative, covering Comics and storyboards and Video production. The repository describes itself as: Agent-first Creative Workspace. The licence is AGPL-3.0.
When your agent uses it
- Explanatory product videos
- Finished renders
Example prompts
- “/explainer-storyboard”
What it can do on your machine
Read from SKILL.md and the folder at commit 339f069. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Explainer Storyboard loads about 1.6k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 878 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from nodetool-ai/nodetool at commit 339f069, republished under its AGPL-3.0 licence (© nodetool-ai). 878 words, ~1,552 tokens.
Download SKILL.mdSave it as
.claude/skills/explainer-storyboard/SKILL.md (or your agent's skills folder).- name
- explainer-storyboard
- description
- Turn a confirmed product or feature brief into a shootable 30–120 second explainer storyboard with a consistent entity roster. Use for explanatory product videos, not workflows, pipelines, or finished renders.
Explainer Storyboard → Storyboard Agent
Create a complete, shootable explainer beat sheet as a NodeTool storyboard. Work directly through the storyboard and entity capability modules. Do not build a workflow or run a pipeline. Do not render stills, clips, or assemble a timeline unless the user asks.
Truthful brief
Collect these facts before creating a board: product or feature, brand and traits, category, audience, core problem, shift, 2–4 concrete mechanism steps, proof assets, CTA, runtime (30, 60, 90, or 120 seconds), platform, tone, mandatory content, and forbidden claims. The core problem, shift, and mechanism are required. Never invent a capability, integration, metric, screen, or customer. Write [CLIENT INPUT NEEDED] wherever proof is not confirmed.
Resolve entities before beats
Every recurring person, location, product UI, device, metaphor object, brand mark, and visual style is an entity. Start with list_entities; reuse user-provided references and existing entities before generating anything. A real product screenshot is a prop reference and must never be regenerated.
Resolve a style entity first. Generate only missing references, applying that style before generating each other entity. A typical 60-second explainer has 4–7 entities: style, persona, optional location, product UI prop, and metaphor prop. Label generated UI as a mock.
Use create_entity with a dense visual descriptor. The descriptor specifies the exact recurring appearance: character features and wardrobe; location materials and lighting; UI layout, palette, typography, and content boundaries; metaphor geometry and material; or style medium, palette, lighting, and lens. An entity id is the asset id supplied to create_entity.
Teaching arc
Compute timecodes from the selected runtime, rounded to 0.5 seconds. Use this arc:
| Beat | Runtime share |
|---|---|
| Problem | 0–15% |
| Stakes | 15–25% |
| Shift | 25–40% |
| Mechanism 1 | 40–55% |
| Mechanism 2 | 55–68% |
| Outcome / proof | 68–82% |
| CTA | 82–93% |
| Sign-off | 93–100% |
For 30 seconds, combine problem and stakes and use one mechanism beat. For 90–120 seconds, use at most three mechanism beats. Use one concept and one literal metaphor. Put the visual aha at the shift-to-mechanism boundary and leave a deliberate half-beat of silence after it. Voice-over must be at most runtime × 2.2 words.
Deliverables
Produce, in order: three concept directions with a recommendation, the full beat sheet, and an entity roster with id, kind, descriptor summary, and referenced beats. Each direction states its entry problem, metaphor, aha, fit, risk, and referenced entities.
For every beat include timecode, teaching job, framing, visual, action, visible entities, verbatim VO, on-screen text of five words or fewer, exact UI/demo input and output or NONE, sound, music, transition, and why it teaches. Mechanism beats must show the real UI or a labelled mock. Brand marks wait until the shift. Use verbs in VO and nouns on screen. The sign-off echoes the opening problem.
Show full SKILL.md (434 more words)Show less
Persist the board
Create the storyboard with create_storyboard({ name, brief, style, aspect_ratio }). Use board.storyboard_id, never .id. Put the complete brief, chosen direction, and entity roster into brief so the project can be reconstructed later. The exact call shapes and return fields — entity id equals the asset id you passed in, the five edit_storyboard ops, what set_board accepts — are in commercial-beat-sheet § Tool contract; every board skill builds against that one section.
Attach roster ids with edit_storyboard({ storyboard_id, ops: [{ op: "set_board", entity_ids }] }) (set_entities is only an alias for set_board). Resolve the render models in the same op: find_model for text_to_image and image_to_video, each result's .ref on image_model / video_model, and each result's prompting_skill loaded before the shot text is written — the shot action is the prompt the still model reads, with the framing and board style appended.
Add one shot per beat with edit_storyboard and an add_shot op. The dense action field names the teaching job, visible entity names in brackets, on-screen text, and UI demonstration. The render attaches a persona or prop entity to a shot only when its name appears in that shot's text (style and location always apply), so every visible entity must be named in action or motion, or listed on the shot's own entity_ids. On-screen text in action is a note for the cut: it goes on as a text clip after assembly (caption-titles), not into the render prompt.
Stop after the planned board unless the user explicitly requests rendering or a cut. Report the directions, chosen board, and entity roster.
Render (only on request)
Stills first with render_storyboard_stills — they cost cents, and you look at every one with view_image asking what is wrong, then score_image_adherence against the shot text. A persona or UI mock that drifts is fixed at the entity (descriptor or reference), then every shot using it re-renders; a shot that fails on composition is fixed in its action. Clips with render_storyboard_clips; a clip wrong where its still was right is one revise_storyboard_clip. Then assemble_storyboard_timeline.
When the board becomes motion
When a cut is asked for, motion-graphics carries the timeline tool contract and routes to the craft skill for the job: video-audio-continuity for whether the beats render as one clip or under a narration track, caption-titles for the on-screen text and callouts this beat sheet already specifies, frame-composition for where a UI mock sits and whether it survives 9:16, motion-direction to hold one motion language across the mechanism beats, and beat-sync-editing when the cut has to sit on a music bed. The half-beat of silence after the aha is a hold, not a gap — keep it in the cut.
© nodetool-ai, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in packages/system-skills/explainer-storyboard of nodetool-ai/nodetool.
Open the folder on GitHubat commit 339f069
Compare with similar skills
Explainer 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 |
|---|---|---|---|---|---|---|
| Explainer Storyboard this skillnodetool-ai/nodetool | 560 | — | ~1.6k | Automated safety check: Pass | AGPL-3.0 | |
| Scroll Promo Site Builderkangarooking/kangarooking-skills | 662 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Paper Collage Explainer Generatortl2012tl/comfyUI-llama-TE | 241 | 4 repos | ~5.2k | Automated safety check: Pass | None | |
| Video ComposeUtopai-Research/pai-code | 357 | — | ~4.1k | Automated safety check: Pass | Custom licence | |
| Ffmpegrendi-api/ffmpeg-cheatsheet | 1.7k | — | ~1.2k | Automated safety check: Pass | None | |
| Remotion VideoTechNomadCode/AI-Product-Development-Toolkit | 1k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Paper Collage Explainer Generator
tl2012tl/comfyUI-llama-TE
For creators, educators, and social-video editors who need a tactile paper-collage language for narration, knowledge points, opinions, or abstract topics.
Video Compose
Utopai-Research/pai-code
Generates and prompts video clips on the filmmaking canvas. An agent skill from Utopai-Research/pai-code.
Ffmpeg
rendi-api/ffmpeg-cheatsheet
A skill your agent uses when the user asks for FFmpeg or FFprobe commands, video/audio conversion, trimming, resizing, padding, overlays, subtitles, thumbnails, GIFs, storyboards, slideshows…
Remotion Video
TechNomadCode/AI-Product-Development-Toolkit
Make a short video about a product or brand (promo, launch, explainer, demo or social clip) entirely in code with Remotion, from idea to a rendered MP4 with sound.
Video Plan
MagicCube/agentara
Plan short-form video, vlog, travel, lifestyle, documentary, or cinematic social video scripts by negotiating duration, choosing a story arc and visual style, then splitting the film into timed…
More from nodetool-ai/nodetool
All 127 skills in this repoBeat Sync Editing
nodetool-ai/nodetool
Cut a NodeTool timeline to music and shape its pacing — detect the beat grid, place cuts on phrases, pick a cut type, build speed ramps with time remap, and give the piece an arc.
Caption Titles
nodetool-ai/nodetool
Add and animate a consistent text layer on an existing NodeTool timeline.
Color Motion
nodetool-ai/nodetool
Choose and animate colour on a NodeTool timeline, including shape and text gradients, colour grades, 3D LUTs, and dither.
Commercial Beat Sheet
nodetool-ai/nodetool
Write a shootable, precisely timed commercial beat sheet and store it as a NodeTool storyboard, with a consistent entity roster behind every shot.
Elevenlabs Audio Prompting
nodetool-ai/nodetool
Direct ElevenLabs speech, dialogue, sound effects and music — the bracketed audio tags v3 acts on and why the voice decides whether a tag lands, stability as the delivery dial, punctuation instead…
Frame Composition
nodetool-ai/nodetool
Stage the frame on a NodeTool timeline — grids, focal placement, safe areas per aspect ratio, depth layers and parallax, camera moves, and where elements enter and leave.
Related
Categories
Questions about Explainer Storyboard
What does Explainer Storyboard do?
Turn a confirmed product or feature brief into a shootable 30–120 second explainer storyboard with a consistent entity roster. Explainer Storyboard is an agent skill from nodetool-ai/nodetool. Turn a confirmed product or feature brief into a shootable 30–120 second explainer storyboard with a consistent entity roster.
When should I use Explainer Storyboard?
Explainer Storyboard fits situations like: explanatory product videos; finished renders.
How do I install Explainer Storyboard in Claude Code?
Run `npx skills add nodetool-ai/nodetool --skill explainer-storyboard -a claude-code`. Or copy the skill folder (packages/system-skills/explainer-storyboard in nodetool-ai/nodetool) into .claude/skills/explainer-storyboard in your project. Claude Code loads it when a task matches its description.
How do I install Explainer Storyboard in Codex?
Run `npx skills add nodetool-ai/nodetool --skill explainer-storyboard -a codex`. Or copy the skill folder (packages/system-skills/explainer-storyboard in nodetool-ai/nodetool) into .agents/skills/explainer-storyboard in your project. Codex loads it when a task matches its description.
Can I use Explainer Storyboard in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nodetool-ai/nodetool --skill explainer-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/explainer-storyboard, .gemini/skills/explainer-storyboard, .github/skills/explainer-storyboard and .opencode/skills/explainer-storyboard in your project.
What does Explainer Storyboard need to run?
SKILL.md names no scripts, command-line tools or credentials: Explainer Storyboard is instructions for the agent only.
Does Explainer Storyboard access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Explainer Storyboard safe to install?
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.
What licence does Explainer Storyboard use?
Explainer Storyboard is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Explainer Storyboard use?
About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Explainer Storyboard?
Skills that share tags, products or a category with Explainer Storyboard: Scroll Promo Site Builder (kangarooking/kangarooking-skills, 662 stars), Paper Collage Explainer Generator (tl2012tl/comfyUI-llama-TE, 241 stars), Video Compose (Utopai-Research/pai-code, 357 stars) and Ffmpeg (rendi-api/ffmpeg-cheatsheet, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Explainer Storyboard?
nodetool-ai (a GitHub organization) maintains it in nodetool-ai/nodetool, which has 560 GitHub stars. The repository holds 127 skills in this directory. The repository was last updated on October 10, 2026.
Source: nodetool-ai/nodetool on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.