Individual skill
StoryFilm
Turns a story markdown file into a narrated animated film, a new reading format where the listener is read to and sees the story as it is told: beats from paragraphs, a bible so every character and place looks the same in every shot, one painting per beat in one style, Fish Audio narration in the story's voice with word timings, a HyperFrames film with camera moves, dissolves, scene breaks, a caption line and title cards, read back and verified. USE WHEN animated reading, story film, film this story, animate this story, illustrated audiobook, narrated story video, turn this story into a movie, storyboard this story, paint the shots, render the story film. NOT FOR the principal's own recordings, argument-first video essays, one-off motion graphics (Remotion), single illustrations (Art), writing the story itself (WriteStory).
LifeOS/install/skills/StoryFilm/SKILL.md
Source commit b7efec97d8c3885feee285bee468c35602fb0606
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.
Repository context
- Repository stars (not skill ratings)
- 19,759
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- augmentation Repository topic
- productivity Repository topic
- humans Repository topic
- ai-harness Repository topic
- intent-engineering Repository topic
- personal-ai Repository topic
- coding Repository topic
- lifeos Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Intents/Full.mddoc · 4,857 bytesIntents/Produce.mddoc · 11,103 bytesIntents/Storyboard.mddoc · 4,664 bytesReferences/StoryboardSchema.mddoc · 2,020 bytesSKILL.mdcore · 7,996 bytesSKILL.mdcore · 7,996 bytesSetup.mddoc · 4,818 bytesTools/.gitignoreasset · 14 bytesTools/Build.tsruns · 6,757 bytesTools/Characters.tsruns · 5,117 bytesTools/FilmComposition.tsruns · 8,171 bytesTools/FilmRuntime.tsruns · 4,322 bytesTools/FilmTimeline.tsruns · 13,054 bytesTools/Intake.tsruns · 5,157 bytesTools/Lib.tsruns · 17,189 bytesTools/Motion.tsruns · 3,120 bytesTools/Narrate.tsruns · 23,332 bytesTools/Paint.tsruns · 10,424 bytesTools/Run.tsruns · 11,422 bytesTools/SerifFont.tsruns · 6,975 bytesTools/Setup.tsruns · 3,129 bytesTools/Shots.tsruns · 5,512 bytesTools/StoryboardLint.tsruns · 5,015 bytesTools/Verify.tsruns · 24,625 bytesTools/bun.lockasset · 9,365 bytesTools/package.jsonruns · 642 bytesTools/tsconfig.jsonasset · 400 bytes
Read excerpt
# StoryFilm
A story goes in; a verified film of it comes out. One creative stage (the storyboard) and a deterministic tail (bible, shots, narration, render, verification, critique, delivery).
## Ideal State
- A story file becomes a film a viewer accepts as one made thing: the same faces first frame to last, each painting fitting its beat, the caption in step with the voice.
- Every film is read back before anyone sees it: `Out/verify.json` green and complete, the Assay video eval set (`video-eval`) passed in the verify stage as `Intents/Produce.md` declares it, the review sheets looked at, and the ArtDirection critique passed on the exact bytes delivered.
- Nothing reaches the principal as a first draft: the film and its sheets land in the downloads folder only through `Run.ts --deliver`, after a passing critique and a Proof receipt.
- Expensive stages run once per change: the storyboard is reviewed and linted before any painting, and every later stage is hash-cached so an edit redoes only what it touched.
- Nothing leaves review: the skill has no upload or publish path.
## Intent Routing