cartoon-studio
Skill0 starsChanged 5 days agoMITView on GitHub
Make a vertical 2.5D animated short, with flat 2D characters inside lit 3D Blender sets, telling a true story. Use for history or science shorts, animated explainers or story episodes.
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- motion-designSkill
- promo-reelSkill
- review-loopSkill
- talking-head-editSkill
- word-captionsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Review: run the review-loop skill plus: does every character sit on the floor?
- Very specific: line 33
Only claims that are in sources.md go on screen.
- Distinctive: line 35
If anything could be mistaken for real footage, remind the user about the platform's AI-content label.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cartoon Studio (2.5D shorts)
Format: 1080x1920, 30 fps, 55-70 sec. Round-headed, thick-outlined, flat-colored 2D characters standing inside warmly lit 3D sets with depth of field. One narrator, one true story, a new shot roughly every 2 seconds.
Episode folder
ep-<slug>/
script.md sources.md shotlist.md cues.md
assets/ episode.blend captions/ review/ out/Pipeline
- Pitch: 5 true stories that fit "The [object] that [did something surprising]" or "Why [thing] always [does X]". One line each, why both a 12- and a 50-year-old would retell it, 2 sources each. Wait for the pick.
- Script: 150-170 words, short spoken sentences. Line 1 is the hook and makes a promise; a twist around second 40; the last line pays off the hook. Every factual claim gets a source in
sources.md. Wait for approval and remind the user to check the sources. - Shot list: one shot per idea, 1.5-3 sec: id, words covered, duration, SET, CAMERA (framing + push-in/dolly/static + reason), CHARACTER (pose, expression), PROP (hero object is always 3D), SOUND (only for physical events). Reuse 3-5 sets. Key beats in global frame numbers at 30 fps. Falling objects obey physics (~30 cm fall ≈ 7-8 frames).
- Sets (Blender): with a Blender MCP server, work through it and look through each camera after every pass; otherwise run Blender headless (
blender -b … --python build.py) and render stills to check. Three passes, stop after each: BLOCK (grey primitives, all cameras placed) → LIGHT (one motivated key, warm practicals, HDRI fill, no 3-point studio lighting) → DRESS (worn, varied materials, small props, depth of field focused where the character stands). Render at exactly 1080x1920. - Hero prop: real-world scale, bevelled edges, wear in crevices, 6-angle look sheet before placing.
- Characters: separate SVG parts (head, body, arms, legs, costume), flat color, one thick dark outline, no gradients. Expression set as separate files (eyes: neutral/wide/narrow/closed/side; mouth: closed/small/wide/frown/grin; extras). Export 2x PNG, import as planes with an emission/shadeless shader so set lights never shade them, add a soft contact shadow under the feet.
- Acting: per shot write thought, anticipation (eyes move ~4 frames first), action (on which word), hold (8-12 frames). No idle bouncing; mouths change only on stressed words.
- Voice + captions: the user's own voice when possible. Word timestamps and captions via the
word-captionsskill. Cuts line up with words. Sound effects incues.mdon the same frame numbers as picture events; align the transient, not the file start. Voice on top, music under, music resolves on the last frame. - Review: run the
review-loopskill plus: does every character sit on the floor? Is any character lit like a 3D object? Is every on-screen claim insources.md? - Deliver:
ffprobemust show 1080x1920, 30/1 and the planned duration.
Hard rules
- Render at size; never crop or upscale.
- Characters never get realistic shading; sets are always richly lit.
- Only claims that are in
sources.mdgo on screen. - Learn the grammar of a format, never copy another channel's characters, designs or scripts.
- If anything could be mistaken for real footage, remind the user about the platform's AI-content label.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

