agentleFS
alebgl77alebgl77/claude-inc/skills/reels-scripting/SKILL.md

reels-scripting

Skill21 starsChanged 4 months agoMITView on GitHub

Scripts 15–60 second short videos (Reels, TikTok, Shorts) in a timestamped two-column VISUAL | AUDIO/VO format — verbal + visual hook in the first two seconds, a retention beat every 3–5 seconds, pattern interrupts at drop points, on-screen captions, a loop-friendly ending, and a CTA — two script variants per idea. Use when the user says "script a Reel about...", "turn this post into a TikTok", "I need a 30-second Short", or "people drop off my videos — fix the script".

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write the double hook for 0–2s: a verbal line that opens a loop AND a visual that shows motion — action mid-frame, a prop, a text punch.

    line 21
  2. Distinctive:

    Place pattern interrupts at the predicted drop points (~3s, ~8s, then every ~7s): zoom punch, location cut, B-roll insert, whip to a text …

    line 26
  3. Distinctive:

    Never both, and never a five-second outro.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 3 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Reels Scripting — Reel Writer

"Script your Reels"

When to use

  • "Script a Reel about <topic>." / "I need a 30-second Short for this launch."
  • Repurposing a post, thread, or newsletter into vertical video.
  • "People drop off after three seconds" — retention surgery on an existing idea.
  • Batch-scripting a week of shorts from one pillar piece.

Workflow

  1. Lock the premise: one idea, one payoff, a target length (15 / 30 / 60s), and a platform. If the payoff doesn't fit the runtime, split it into two videos now.
  2. Write the double hook for 0–2s: a verbal line that opens a loop AND a visual that shows motion — action mid-frame, a prop, a text punch. Never a static talking head saying "hey guys, today I want to talk about".
  3. Beat out the middle: one new beat every 3–5 seconds — a fact, a cut, an angle change, a prop reveal, an on-screen number. Timestamp every beat.
  4. Place pattern interrupts at the predicted drop points (~3s, ~8s, then every ~7s): zoom punch, location cut, B-roll insert, whip to a text card.
  5. Script the on-screen captions in 3–5 word chunks synced to the VO, keywords capitalised, kept clear of platform UI at the top and bottom of frame.
  6. Engineer the ending: land the payoff, then EITHER a loop line that feeds back into the opening frame OR a one-beat CTA (follow / comment a keyword / save). Never both, and never a five-second outro.
  7. Produce two variants with different hooks and structures — story-led vs list-led — that deliver the same payoff.
  8. Attach the shoot list: locations, props, B-roll shots, text cards, and a one-line edit-complexity estimate.

Output format

## Reel: <working title> — <length>s — <platform>
Premise: <one idea> | Payoff: <what the viewer walks away with>

### Variant 1 — <angle>
| TIME | VISUAL | AUDIO / VO |
|------|--------|------------|
| 0:00–0:02 | <shot + on-screen text> | "<verbal hook>" |
| 0:02–0:06 | <beat> | <VO line> |
| 0:06–0:10 | <interrupt: zoom / cut / B-roll> | <VO line> |
| ... | <one row per beat> | ... |
| <end> | <loop frame or CTA card> | "<closing line>" |
Captions: <chunking + safe-zone note>
CTA: <exact wording, or "loop — no CTA">

### Variant 2 — <angle>
<same table, different hook and structure>

### Shoot list
- Locations: <...> | Props: <...>
- B-roll: <shots>
- Text cards: <copy>
- Edit complexity: low | medium | high — <why>

Quality bar

  • 0–2s has BOTH a verbal loop-opener and visual motion — zero dead-air intro.
  • No stretch longer than five seconds without a new beat or interrupt.
  • Every VISUAL cell is shootable as written: shot, prop, and text specified.
  • Captions chunked at five words or fewer and inside platform safe zones.
  • The ending loops or CTAs in one beat, and the payoff pays what the hook promised.
  • Runtime is honest: the VO read aloud fits the target length.

Example

Invocation: "30-second Reel: the three pricing mistakes freelancers make."

Produces: two timestamped two-column scripts. Variant 1 opens on a torn-up invoice with the VO "This invoice cost me $9,000", hits beats at 0:04 / 0:09 / 0:15 / 0:22 for the three mistakes, and loops the close back to the invoice. Variant 2 opens contrarian ("Raise your rate. Today.") and runs as a fast list with text-card interrupts. Both ship with caption chunks, exact CTAs, and a shoot list — invoice prop, desk B-roll, two text cards, edit complexity low.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.