reel-script
Skill4 starsChanged 4 months agoMITView on GitHub
Write a short-form voiceover script in the "paper-reel" style for faceless motion-graphics reels (cream grid, punch-color cards, taped proof cards). Picks from several narrative shapes (reveal, listicle, story, before/after, data-led, showdown) based on what the idea actually is, instead of forcing every topic through one fixed arc. Give it a topic, a raw idea, notes, or a link and it returns a beat-by-beat script, each beat tagged with the pr_card / pr_punch / pr_proof kind it maps to, ready to record as VO and drop into a broll_plan.json. Trigger on "write a reel script", "script this idea", "turn this into a reel", "write me a hook for X", or when the user hands over a topic/notes for a short-form video.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- saypage-ai/saypage-plugintheir own version, first seen Nov 1, 2026
- fliqrlabs/instagram-creator-skillstheir own version, first seen Nov 1, 2026
- RahmanBuildsAI/ravyn-reel-kittheir own version, first seen Oct 25, 2026
- m-binimran/creator-packtheir own version, first seen Jun 14, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- RahmanBuildsAI/ravyn-reel-kit★ 9same name
- fliqrlabs/instagram-creator-skills★ 5same name
- m-binimran/creator-pack★ 3same name
- saypage-ai/saypage-plugin★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- make-videoSkill
- motion-design-editSkill
- video-edit-longformSkill
- video-editSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 6 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
Before writing a word, decide what kind of idea this is.
- Distinctive: line 44
If the idea genuinely fits two shapes, pick the one that needs fewer forced beats — don't hedge by blending both.
- Very specific: line 75
BEFORE — the old way, concrete and specific (not "it was hard" — what exactly was hard) → pr_card
- Very specific: line 76
AFTER — the new way, concrete contrast → pr_card
- Distinctive: line 112
Every line must be sayable in one breath: If a sentence needs a breath in the middle, split it into two beats.
- Distinctive: line 115
Don't recycle phrasing across scripts: If a line you're about to write echoes a line from a script you wrote earlier in this conversation …
- Distinctive: line 143
Write the beats for that shape, following the voice rules.
- Distinctive: line 144
After the script, note total estimated VO duration (rough: ~2.3 words/sec spoken) so the user knows if it's in the 30–60s band.
- Very specific: line 145
Don't render anything or touch any render pipeline — this skill only writes the script.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/reel-script
Writes a voiceover script for a faceless short-form reel in the paper-reel
style (cream grid + orange punch cards + taped proof-card aesthetic). The
output is timed prose meant to be read aloud as VO, not slides — every beat
is short enough to say in one breath and tagged with which graphic kind it
becomes downstream (pr_card / pr_punch / pr_proof, the Remotion kinds
already wired into the paper-reel render pipeline).
The single biggest failure mode of this skill is sameness — every idea coming out with the same hook/credibility/reframe/3-tips/CTA shape, regardless of what the idea actually is. That's not a structure, it's a straitjacket. Fix: diagnose what KIND of idea this is first, pick the narrative shape that actually fits it, and vary the hook style every time.
When to use
- User gives a topic, a raw idea, rough notes, an article, or a link and wants it turned into a short-form script.
- User asks for "a hook for X" or "script this like the reel you showed me."
- User is prepping VO to record before a
pr_*render pass.
Step 1 — diagnose the idea, don't default
Before writing a word, decide what kind of idea this is. That decision picks the shape (below), which picks the beat count and order. Don't reuse last script's shape just because it worked before.
| If the idea is... | Use shape |
| A myth, a misconception, a surprising truth ("everyone thinks X, actually Y") | A — Reveal |
| A list of tools/mistakes/tips with no single narrative thread | B — Listicle |
| Something that happened to you or someone specific, with a beginning/middle/end | C — Story |
| A workflow, tool, or way of doing things that got replaced by a better one | D — Before/After |
| A stat, trend, or market shift that's surprising on its own | E — Data-led |
| Two options/approaches being weighed against each other | F — Showdown |
If the idea genuinely fits two shapes, pick the one that needs fewer forced beats — don't hedge by blending both.
Step 2 — the shapes
Each shape lists its beats in order. Beat count and presence of credibility/reframe beats varies by shape — don't import beats from shape A into a different shape out of habit.
A — Reveal (myth-bust / reframe)
- HOOK — the counter-intuitive claim →
pr_punch - CREDIBILITY — one stat/fact that makes the claim believable →
pr_proof - REFRAME — the twist that turns the claim into a lesson →
pr_punch(boxed) - TIPS (2–4) — one teachable idea each →
pr_cardper tip - CTA →
pr_card
B — Listicle
- HOOK — frames the count and the stakes ("3 things nobody tells you about X") →
pr_punchorpr_card - ITEM 1..N (3–5 items) — each is self-contained: the insight AND its proof in one beat, no separate credibility beat →
pr_cardper item,eyebrow: "0N" - CTA →
pr_card(No REFRAME beat — the list itself is the payoff.)
C — Story
- HOOK — cold open on a moment, not a claim ("It's 2am. The render just failed for the sixth time.") →
pr_punchorpr_proof - SETUP — the stakes/context in one line →
pr_card - TURN — what changed, the decision, the twist →
pr_punch(boxed) - LESSON — what it means for the viewer, generalized from the specific story →
pr_card - CTA →
pr_card
D — Before/After
- HOOK — the promise of the change ("I deleted my video editor. Then I made more videos than ever.") →
pr_punch - BEFORE — the old way, concrete and specific (not "it was hard" — what exactly was hard) →
pr_card - AFTER — the new way, concrete contrast →
pr_card - HOW — the one mechanism that made the shift possible →
pr_prooforpr_card - CTA →
pr_card
E — Data-led
- HOOK — the stat stated cold, no preamble ("300 million to 5.2 billion. Six months.") →
pr_prooforpr_punch - CONTEXT — why this number is surprising / what it's being compared against →
pr_card - IMPLICATION — what it means for the viewer specifically, not just "the industry" →
pr_punch(boxed) - SUPPORT (1–2 beats) — a second data point or example →
pr_card - CTA →
pr_card
F — Showdown
- HOOK — frames the two options ("Timeline editing vs. one folder and a prompt.") →
pr_punch - OLD WAY — its real pain point, specific →
pr_card - NEW WAY — the alternative, specific →
pr_card - WHY IT WINS (1–2 beats) — concrete reasons, not vibes →
pr_card - CTA →
pr_card
Step 3 — vary the hook, every time
Reusing the same hook style back-to-back is the fastest way to make two different scripts feel identical. Before writing the hook, pick a style you haven't used in your last script (if you don't know what was used last, just don't default to "bold claim" every time — it's the easiest trap):
- Bold claim — "I deleted my video editor. Then I made more videos than ever."
- Contrarian reframe — "Everyone thinks X. Actually, Y."
- Question — "What if your editor could brand itself?"
- Cold-open scene — "It's 2am. The render just failed for the sixth time."
- Stat-first — "300 million to 5.2 billion. Six months."
- POV — "POV: you just fired your video editor."
Voice rules (apply to every shape)
- Staccato, confident, no filler. Short sentences. Cut "so," "basically," "honestly," "I think" — state things directly.
- Numbers, not adjectives. "300 million to 5.2 billion" beats "grew massively."
- Every line must be sayable in one breath. If a sentence needs a breath in the middle, split it into two beats.
- Total length: 30–60s of spoken VO (~75–160 words) for a first pass, unless the user asks for longer. Longer needs more beats/items, not padding.
- A correction/contrast moment ("not X. Y.") is a spice, not a requirement. Use it where it genuinely fits one beat, skip it entirely if it doesn't — don't force one into every script just because it worked once.
- Don't recycle phrasing across scripts. If a line you're about to write echoes a line from a script you wrote earlier in this conversation (same opening word, same sentence shape), rewrite it.
Output format
State which shape you picked and why (one line), then write the script as labeled beats in that shape's order, each on its own block, tagged with its target kind:
Shape: <A/B/C/D/E/F — name> — <one-line reason this idea fits it>
HOOK (pr_punch)
"<line>"
<next beat name> (<kind>)
"<line>"
...
CTA (pr_card)
"<line>"Process
- If the user gave a topic/notes/link, work from that directly — don't ask clarifying questions unless the input is too thin to find a real angle (e.g. just "AI" with nothing else). A genuinely thin prompt is worth one clarifying question; anything with a real angle, just write it.
- Diagnose the idea against the table in Step 1 and commit to one shape — resist defaulting to Reveal just because it's the most familiar.
- Pick a hook style per Step 3, favoring one you haven't used recently.
- Write the beats for that shape, following the voice rules.
- After the script, note total estimated VO duration (rough: ~2.3 words/sec spoken) so the user knows if it's in the 30–60s band.
- Don't render anything or touch any render pipeline — this skill only writes the script. Handoff is: user records VO from this script, then a separate pass builds the
broll_plan.jsonand renders.
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.

