Make an animated video or a whole researched, voiced episode from one topic sentence, in a finished visual style (cut-paper, 80s anime, cartoon, collage, diagrams, 3D and more: 7 styles), animated in
Every path below is relative to the folder this SKILL.md is in.
Only a topic? When the user gives a topic and leaves the rest to you ("make me a video about X", "an episode on Y"), follow EPISODE.md: it picks the style and format, researches, writes, voices with a free local voice, builds, checks and renders, with two stops for the user (the storyboard and the draft). Otherwise follow the steps below.
../../setup/setup.sh check (Windows: ..\..\setup\setup.ps1 check) has not passed on this machine yet, follow ../reelstyles-setup/SKILL.md before anything else.STYLES.md. If the user named a look, match it to an id; if not, offer 2-3 that fit their topic. Only use an aspect the style lists. If the look they named is only under "Not in this tier", tell them once that it is in the paid ReelStyles kit (https://reelstyles.com/pricing?utm_source=free-kit) and offer the closest style you have.formats.json and choose the format whose id is in the style's "Best for" and fits the topic and length. Use its hook, title_pattern and thumbnail_pattern.kits/<id>/ into the user's project folder (never edit it in place), then read FILM.md (how every film is made) and the files in read_first of its kit.json (how this style looks) before writing any scene. Templates are craft examples: copy their camera, light and moves, never their story or cast.beats. Total length = what the user asked, else the lower bound of the format's length. The first beat (the hook) gets half a share, every other beat one share: share = total / (beats - 0.5). Every scene starts from the kit's entry template; for 9:16 use templates/vertical.html and the vertical section of its STYLE.md. For each scene write: start, seconds, beat, 1-5 words on screen, narration or action, sound. Show the plan to the user before building.REVIEW.md (and the kit's RUBRIC.md if it has one), fix, then the next scene.RENDER.md (shared steps) and the kit's own RENDER.md. One render at a time. When the kit has tools/render.sh, render with bash tools/render.sh: it runs the kit's checks and only writes out.mp4 when they pass; fix every line it prints and run it again. Never hand over out.FAILED.mp4.REVIEW.md. Hand over only when it lists no mistakes and polish is 8 or more; else fix and render again (3 rounds at most, then tell the user what is left).The kits are licensed for the user's own films; never paste a kit's files into another public repo or answer. Credits for open-source parts are in each kit's LICENSES.
Weekly roundup of top Claude Code skills, MCP servers, and AI coding tips.