Back to search
story-shorts
SkillWorks with Claude CodeGitHub
Use when making faceless vertical (9:16) animated multi-part story videos, e.g. a zombie POV series, with Claude writing the story, Codex generating images, ElevenLabs narration and ffmpeg doing the montage. No paid video model is needed.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/onursamett--story-shorts-skill)HTML
<a href="/listings/onursamett--story-shorts-skill"><img src="/api/listings/onursamett--story-shorts-skill/badge.svg" alt="findsafeskills safety rating" /></a>Install
i
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
cp -r story-shorts ~/.claude/skills/story-shorts # folder name = skill name
Pillow in a virtual environment (if your system Python is locked down):
python3 -m venv .venv && . .venv/bin/activate && pip install Pillow
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 65 lines
- ---
- name: story-shorts
- description: Use when making faceless vertical (9:16) animated multi-part story videos, e.g. a zombie POV series, with Claude writing the story, Codex generating images, ElevenLabs narration and ffmpeg doing the montage. No paid video model is needed.
- ---
- # story-shorts
- Pipeline: story bible -> outline per part -> character sheets -> anchored location images -> narration -> montage -> frame QA -> caption.
- Scripts live in `scripts/` (path below is relative to this skill folder), templates in `templates/`.
- Work in a project folder per part, e.g. `series/part1/` containing `scenes.json`.
- ## 1. Story bible first
- Copy `templates/story_bible_template.md` and fill it in before anything else:
- - a map of locations with the only legal routes between them,
- - ONE timeline with the lighting for each part (state day/night in every image prompt),
- - a cast with fixed one-line descriptions (hair, clothes, one unique accessory).
- Every later step must obey this file. Do not start outlining until the user approves the bible.
- ## 2. Part-by-part outline
- - Each part starts exactly where the previous one ended (first line = short "previously").
- - Explain every move between places; never jump location or time of day.
- - 1-2 locations per part, 60-90 s (12-16 scenes), ends on a cliffhanger.
- - Mostly medium/wide shots; at most 2 extreme close-ups per part.
- - New accounts: no A/B poll in the first parts. Add an A/B choice card only from later parts and pick the winner yourself until comments arrive.
- ## 3. Character reference sheets (6 expressions)
- Put one entry per character in `"refs"` of scenes.json: a full-body front view plus six head close-ups with clearly different expressions (e.g. smile, bored, confused, terrified, crying, determined). Generate them first and let the user approve them:
- `python3 scripts/gen_images.py <folder>` generates refs first (they are the first jobs).
- Engines: Codex (default, ~1 min/image) or `--engine gemini` (Antigravity CLI, a few min/image). If Codex reports a usage limit, switch the remaining files to Gemini, or split the list: one Codex run and one Gemini run on different files can run at the same time (never two Codex runs).
- Put the fixed descriptions in `"cast"`: names in prompts are expanded to them automatically.
- ## 4. Anchor scenes (consistent rooms)
- Give every image a location id: `"loc": "classroom"` (or one scene-level `"loc"`). For each location the FIRST generated frame becomes the anchor and is automatically passed as an extra reference to every later image of the same location, so layout, furniture and lighting stay the same. Use `"anchor": false` on an image that must not use/become an anchor (extreme close-ups, window views, a deliberately different angle of lighting). Make the first frame of each location a clean wide establishing shot, and check it before generating the rest. Check with `--dry-run` first: it prints each job with its resolved refs and anchors and calls nothing.
- ## 5. Shot list (2-3 images per narration line)
- For every image prompt state explicitly:
- - camera position (wide from the back of the room, medium from the front, over the shoulder...),
- - location and light ("bright late-morning daylight, NOT night"),
- - a specific facial emotion,
- - hands simple or out of frame (hands are where image models fail).
- Events seen from another place must be framed from the viewer's position, e.g. "seen from INSIDE the classroom through the window, window frame visible in the foreground". Do not draw an event as if the camera stood next to it when the hero is somewhere else.
- Scene fields: see `templates/scenes_example.json` (`images`, `narration` or `lines`, `chat`, `widgets`, `fx`, `text`, `accent`, `focus`).
- ## 6. Narration
- One narrator reads everything, including phone messages (the chat card appears on screen while the line is read; use `lines` with `"show": k` to reveal k messages). Avoid violent words such as "bites" or "blood": the TTS content filter rejects them (`voice.py` warns about a few). Rephrase ("hurt", "wound", "scratch").
- `export FAL_KEY=...` then `python3 scripts/voice.py run <folder> [--voice Brian]`. Try voices with `python3 scripts/voice.py test "sentence" Brian Daniel`.
- ## 7. Montage
- `python3 scripts/render.py <folder>` (Pillow needed; see README for a venv). Output: `<folder>/<foldername>.mp4`. Options: `--speed 1.12`, `--pill`, `--out`.
- Features: 2 s camera shots, 3-word Impact captions with yellow active word, big keyword at the top, chat card, widgets (counter, bar, pulse, tag, options), fx alarm/flicker, vignette, click-free PCM audio.
- ## 8. Frame QA before delivering
- Look at every image (contact sheet or one by one) and at 2-3 frames of the final video. Check: lighting matches the timeline, location matches the scene, no duplicate frames, no text/letter artifacts, characters match the sheets, hands, nothing sudden like day <-> night. Regenerate bad ones by name: `python3 scripts/gen_images.py <folder> k3_2.png`, then re-render. Never send a video you have not looked at.
- ## 9. Caption / post
- Fill `templates/post_caption_template.md` per part: hook question, 2-3 concrete details, question to the reader, cliffhanger, follow call, 5-8 hashtags, cover text.
- ## Known pitfalls
- - Parallel Codex runs mix up output files: always sequential; the script md5-dedupes and retries once.
- - `codex exec -i X` swallows the prompt: pass images as `--image=path` (the script does).
- - ElevenLabs timestamps come in segments that can split a word: `render.py` merges them.
- - The DIN-style font lacks the "·" glyph: the pill widget draws the dot itself.
- - Image models drift: repeating the location description and the light in every prompt is cheaper than regenerating.
- - Do not generate in the same folder from two jobs at once.
- - Generating images is slow (about 1 min each): run it in the background and tell the user.
README.md · README · 50 lines
- # story-shorts
- A Claude Code skill that turns an idea into faceless, vertical (1080x1920) animated multi-part story videos, for example a zombie POV series. Claude writes the story bible, outline and shot list; Codex generates the images; ElevenLabs (through fal.ai) narrates; ffmpeg + Pillow do the montage with camera moves, word-by-word captions, chat cards and info widgets. No paid video-generation model is used.
- ## Requirements
- - Claude Code
- - Codex CLI, logged in (image generation runs through `codex exec`), and/or
- - Gemini via the Antigravity CLI (`agy`, signed in) for `--engine gemini`: slower (a few minutes per image) but a
- good fallback when Codex hits its usage limit. Images are read from `~/.gemini/antigravity-cli/brain/`.
- - `ffmpeg` and `ffprobe` on PATH
- - Python 3 with Pillow (for `render.py` only)
- - A fal.ai key in the `FAL_KEY` environment variable (for `voice.py` only)
- ## Install as a Claude Code skill
- ```bash
- cp -r story-shorts ~/.claude/skills/story-shorts # folder name = skill name
- ```
- Pillow in a virtual environment (if your system Python is locked down):
- ```bash
- python3 -m venv .venv && . .venv/bin/activate && pip install Pillow
- ```
- ## Quick start
- ```bash
- mkdir -p series/part1 && cp templates/scenes_example.json series/part1/scenes.json
- python3 scripts/gen_images.py series/part1 --dry-run # job list with refs and anchors, calls nothing
- python3 scripts/gen_images.py series/part1 # sequential, resumable (only missing files)
- python3 scripts/gen_images.py series/part1 --engine gemini k8_1.png k8_2.png # Gemini for some files
- export FAL_KEY=... # never commit this
- python3 scripts/voice.py run series/part1 --voice Brian
- python3 scripts/render.py series/part1 # -> series/part1/part1.mp4
- ```
- Image styles: `--style anime2` (default), `anime`, `pixar3d` (or env `STORY_STYLE`). Image model: `--model` or env `CODEX_IMAGE_MODEL`. Narrator voice: `--voice` or env `ELEVEN_VOICE`. Render speed: `--speed` or env `STORY_SPEED`. Fonts: env `FONT_IMPACT`, `FONT_DIN`, `FONT_SANS`.
- ## scenes.json
- See `templates/scenes_example.json`. Top level: `cast`, `refs`, `chat_me`, optional `voices`, `scenes`. Scene: `narration` or `lines`, `images` (`file`, `prompt`, `refs`, `loc`, `anchor`, `setting`), `loc`, `setting`, `chat`, `widgets`, `fx`, `text`, `accent`, `focus`. Timing files keep their original names, `kelime_zamanlari.json` and `satir_zamanlari.json`.
- ## Costs
- - Voice: about $0.10 per 1000 characters on fal.ai ElevenLabs v3 (a 75 s part is roughly 900-1200 characters).
- - Images: generated through your ChatGPT plan via Codex; no per-image fee but it counts against plan limits.
- - ffmpeg/Pillow: free.
- ## Limitations
- - No true character animation: motion is camera pans/zooms and cuts between stills.
- - Image generation is sequential, about 1 minute per image; a 14-scene part with 2-3 images per scene takes roughly 30-45 minutes.
- - Consistency depends on reference sheets and anchors; always check frames before publishing.
- - Narration uses one voice for everything.
- ## License
- MIT, see [LICENSE](LICENSE).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.