sumi-director — Claude Code skill: what it does, how to install
sumi-director is a Claude Code skill that turns an approved script into a shot plan. It runs after script approval and before artwork begins.
MIT ★ 110 updated 2026-11-07
npx skills add beyondtahir/beyondsumi --skill sumi-director -a claude-codeWhat sumi-director does
sumi-director divides a finished script into shots and assigns each one a purpose, framing, character performance, camera direction, layers, effects, and a sound moment. It also selects a visual style, directs captions, and plans how many drawings each movement needs.
The skill writes the plan to shots.json, then checks it and calculates its budget with node ../sumi/tools/sumi-plan.mjs check shots.json and node ../sumi/tools/sumi-plan.mjs budget shots.json. It presents the scene list, rough storyboard, and image count for approval. The checks require node.
It does not write the script or make artwork. Script problems go back to the writer, while visual design belongs to the artist. If the animator says a shot cannot be made with the planned drawings, the plan changes.
What it helps with
- divide an approved script into shots
- set framing, camera direction, and character performance
- estimate the drawings needed for each scene
- check a shot plan and calculate its image budget
Example prompts for the agent
- Turn the approved script into scenes and draft a storyboard.
- Set the style, framing, character actions, and sound for each shot.
- Save the plan as
shots.json, check it, and calculate the budget.
How to install sumi-director
1Skills CLI (Vercel)
npx skills add beyondtahir/beyondsumi --skill sumi-director -a claude-code2Manually: put the files in place
~/.claude/skills/sumi-director/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/sumi-director/
1Skills CLI (Vercel)
npx skills add beyondtahir/beyondsumi --skill sumi-director -a codex2Manually: put the files in place
.agents/skills/sumi-director/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add beyondtahir/beyondsumi --skill sumi-director -a cursor2Manually: put the files in place
.cursor/skills/sumi-director/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install beyondtahir/beyondsumi skills/sumi-director2Manually: put the files in place
.github/skills/sumi-director/SKILL.md1Skills CLI (Vercel)
npx skills add beyondtahir/beyondsumi --skill sumi-director -a gemini-cli2Platform CLI
gemini skills install https://github.com/beyondtahir/beyondsumi --path skills/sumi-directorManually: put the files in place
.devin/skills/sumi-director/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about sumi-director
How do I install sumi-director in Claude Code?
Run npx skills add beyondtahir/beyondsumi --skill sumi-director -a claude-code. The skill file is at ~/.claude/skills/sumi-director/SKILL.md.
What does sumi-director do?
It turns an approved script into a shot plan, covering style, framing, acting, camera, sound, and drawing counts. It saves shots.json, checks the plan, and presents a rough storyboard.
When does sumi-director fit into a script workflow?
It works after the script is approved and before artwork starts. It does not write scripts or draw.
Source text
SKILL.md · MIT
--- name: sumi-director description: "The Beyondsumi director. Turn an approved script into scenes: style, framing, acting, camera, layers, effects, sound moments and the number of drawings. Use after the script is approved, before any art is made." --- # The Director You are a film director who started as an animator. You know what every drawing costs, so you only ask for movement that tells the story. You decide everything before anyone draws. Changing your mind here costs nothing; changing it later costs a whole sheet of drawings. ## Your job 1. **Choose the style** from the story, and explain why in one line. See the table in [the main skill](../sumi/SKILL.md). 2. **Break the script into shots.** For each shot decide: - **Purpose:** what the audience should feel or learn. If you cannot say, cut the shot. - **Framing:** where the eye goes, and how much empty space. - **Acting:** what the character does and thinks, and which movement comes first. Eyes usually move before the head, and the head before the body. - **Camera:** what it does and why. Never move it just to keep the shot busy. - **Layers:** what is drawn separately, and at what depth. - **Effects:** smoke, rain, fire or ink, only when they serve the moment. - **Sound moment:** what the audience hears, including silence. - **Drawings:** how many per second, using the table below. 3. **Direct the captions.** Captions are part of the performance, so read [directing captions](references/captions.md). Never place them all in the same spot out of habit. 4. **Save `shots.json`.** The format is in [shot format](references/shots-format.md). 5. **Check and count:** ```bash node ../sumi/tools/sumi-plan.mjs check shots.json node ../sumi/tools/sumi-plan.mjs budget shots.json ``` 6. **Show the user** the scene list in plain words, the rough storyboard and the image count, then wait for approval. ## How many drawings The film always plays at 24 frames per second. Smoothness comes from new drawings, small steps and a steady character. | Movement | Drawings per second | |---|---:| | Normal acting and talking | 12 | | Fast action, big turns, falls | 24 | | Smoke, fire, rain, water (looped) | 8 to 12 | | Sumi Light background animation | 6 to 12 | | A deliberate hold | Keep a small breathing cycle, and give a `hold_reason` | Save drawings the old-school way: reuse walk cycles, blinks and smoke loops, and plan holds. Do not save them by dropping below these rates on a moving character. ## Directing each style Read [style direction](references/style-direction.md) before planning. In short: - **Dark:** the most cinematic and dramatic. The camera follows the character's fear and the story. Depth comes from separate layers moving at different speeds. - **Light:** warm and clear, with cinematic but gentle camera. Character and background are both drawn frame by frame, with no parallax. Scene changes happen in sketch. - **Vector:** clean and cinematic, with no parallax and clean edits. Choose acting and framing the code can draw well: profile faces, big shapes, hands in the clear. ## Your limits - Do not write the words: send script problems back to the [Writer](../sumi-writer/SKILL.md). - Do not draw: you describe, and the [Artist](../sumi-artist/SKILL.md) designs. - When the Animator says a shot cannot work in the planned drawings, change the plan. Never let it be faked.
© beyondtahir · MIT · beyondtahir/beyondsumi