agentleFS
Sign inStart free
Ootto-AIOotto-AI/claude-content-skills/skills/reel-scripter/SKILL.md

reel-scripter

Skill417 starsChanged 3 months agoMITView on GitHub

Turn an idea or hook into a full 30-45 second reel script — hook, value beats, payoff, and CTA, with on-screen text. Use when the user says "reel script", "video script", "script this", "write a reel", "short-form script", or "turn this idea into a video".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Tip: Read it out loud and cut 20%.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Reel Scripter

Turn one idea (or hook) into a tight, postable 30-45s reel script.

When to use

You have a hook or topic and need the whole script — what to say, in what order, with the on-screen text and a CTA that earns the follow.

What you'll need

The idea or hook, the platform (Reels / TikTok / Shorts), the audience, and the goal (follows / saves / DMs / link clicks). Optional: your brand voice.

Instructions

Collect the inputs, then run this prompt:

You are my short-form video scriptwriter. Write a [30/45]-second [Reels/TikTok/Shorts] script.

Idea / hook: [idea or hook]
Audience: [who it's for]
Goal: [follows / saves / DMs / clicks]
Voice: [your tone — e.g. punchy, warm, expert-next-door]

Structure:
1. HOOK (0-3s) — stop the scroll, restate the promise.
2. CONTEXT (3-8s) — name the problem or stakes.
3. VALUE (8-30s) — 3 fast, concrete beats. Show, don't lecture.
4. PAYOFF + CTA (last 5s) — the takeaway + one specific action.

Output a two-column script: [SPOKEN line] | [ON-SCREEN text]. Keep spoken lines to ~140 words total. Add a 1-line B-roll/visual suggestion per beat. End with 2 alternate CTAs.

Obsidian memory tip: With your vault connected (Filesystem MCP), ask Claude to "match the pacing and structure of my best-performing reels in my vault." It scripts in your proven format, not a generic one.

Tip: Read it out loud and cut 20%. Short-form rewards tight.

Built by Ootto — the AI autopilot that connects your tools once and runs the busywork for you, automatically. Book a demo →

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.

Check your setup, free