agentleFS
rdoser13rdoser13/free-claude-skills/short-form-video-scripts/SKILL.md

short-form-video-scripts

Skill3 starsChanged 3 months agoMITView on GitHub

Writes short-form video scripts and matching social captions using a Hook to Truth to Do This Instead to CTA structure that builds authority through proof rather than hype. Use when asked for a Reel/Short/TikTok script, a talking-head script, video captions, repurposing a transcript into short-form, or a recurring series format. Fill in the [BRACKETED] sections with your own voice and CTA.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈19

    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:

    When asked for scripts:

    line 24
  2. Distinctive:

    Use the flow: Hook → Truth → Do This Instead → CTA

    line 27
  3. Distinctive:

    Add light pacing cues and contrast examples to hit time naturally

    line 28
  4. Distinctive:

    When asked for captions: Return 3 items (CSV-ready):

    line 30
  5. Distinctive:

    Write it once and reuse it verbatim on every script.

    line 42
  6. Distinctive:

    No fake certainty. If a claim needs context, qualify it.

    line 57
  7. Distinctive:

    Use at least one:

    line 67
  8. Distinctive:

    No giant lists unless the user requests it

    line 75
  9. Distinctive:

    Keep it at the end

    line 78
  10. Distinctive:

    Don't add extra personal intro before value

    line 79
  11. Distinctive:

    Use this structure unless the user requests "copy/paste with no labels".

    line 84
  12. Distinctive:

    Add 2–4 cues per script:

    line 105
  13. Distinctive:

    Keep it subtle. Substance > editing gimmicks.

    line 110
  14. Distinctive:

    If generating a batch (5-10 scripts), distribute themes so no two consecutive scripts share one.

    line 140
  15. Distinctive:

    When the user references or supplies:

    line 164
  16. Distinctive:

    Don't ask questions unless absolutely necessary.

    line 173
  17. Distinctive:

    If user requests "copy/paste scripts", remove the section labels and provide clean paragraphs.

    line 196
  18. Distinctive:

    If user requests "multiple variations", default to 2 variations:

    line 197
  19. Distinctive:

    Avoid offering more than needed.

    line 200

≈ “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

Short-Form Video Scripts

Setup: replace every [BRACKETED_PLACEHOLDER] with your own details (CTA, voice, themes). The structure is the skill; the voice is yours.

What this Skill is for

Generate short-form video scripts and social captions that:

  • Position the creator as a trusted authority in their niche
  • Lead with proof, credibility, and practical frameworks
  • Optimize for trust and pipeline, not vanity metrics

What this Skill is NOT for

  • "AI hype" content, vague motivation, or trend-chasing without proof
  • Buzzword-heavy marketing jargon
  • 100% AI-generic scripts that could be said by anyone

Default output (when the user doesn't specify)

When asked for scripts:

  • Provide Title + Script (read-aloud ready)
  • Scripts must read aloud to 60+ seconds
  • Use the flow: Hook → Truth → Do This Instead → CTA
  • Add light pacing cues and contrast examples to hit time naturally

When asked for captions: Return 3 items (CSV-ready):

  1. Caption (WITH hashtags)
  2. Caption (WITHOUT hashtags)
  3. Engagement question (punchy, ends with "?")

Required CTA (must be verbatim)

[YOUR_CTA]

Write it once and reuse it verbatim on every script. A CTA that changes every video never becomes recognizable. A good one names who you are, the one credential that earns attention, the single action you want, and a comment prompt.

Template: "I'm [NAME], [ONE CREDENTIAL]. If this helped you, [SINGLE ACTION]. Drop your thoughts in the comments below."


House style

Replace these with your own voice rules if you have them. These defaults work for most authority-building creators:

  • Direct and confident (peer-to-peer, not teacher-to-student)
  • Plainspoken (9th-grade reading level)
  • Short sentences. No long walls of text.
  • Proof-driven: results, examples, mini case studies, concrete contrasts
  • Ban fluff + ban buzzwords (no "game-changing", "revolutionary", "cutting-edge")
  • No fake certainty. If a claim needs context, qualify it.

Authority rules (non-negotiables)

  1. Hook must earn trust fast
    • Contrarian, myth-busting, or calls out a common mistake
    • Mention AI when relevant, but don't make AI the "hero"
  2. Truth must include proof Use at least one:
    • A number ("$12k from one intent-based video")
    • A clear example ("Here's what breaks when you post AI slop…")
    • A simple before/after ("views vs trust; volume vs proof")
  3. Do This Instead must be a framework
    • 1 clear play with steps
    • "If you do X, you get Y" logic
    • No giant lists unless the user requests it
  4. CTA always included
    • Keep it at the end
    • Don't add extra personal intro before value

Script template (default)

Use this structure unless the user requests "copy/paste with no labels".

Title

A short title that frames the angle (no clickbait).

Script

Hook (0–5s): [Pattern interrupt + clear claim]

Truth (5–30s): [Debunk + why it matters + proof/example]

Do This Instead (30–55s): [A simple framework with steps]

CTA (final 10–15s): [Verbatim CTA]


Cinematic/retention layer (lightweight)

Add 2–4 cues per script:

  • On-screen text suggestion for the hook
  • A quick "cut here" moment for pacing
  • A loop line near the end (implied continuation, curiosity, or comment prompt)

Keep it subtle. Substance > editing gimmicks.


Caption rules (must follow)

  • Short, scroll-stopping, not a script recap
  • Includes one proof/trust line OR one hard contrast
  • Ends with a question (engagement)
  • Hashtags: 3–4 relevant, not spammy

Caption format (CSV-ready):

  • WITH hashtags: single paragraph + hashtags at end
  • WITHOUT hashtags: same paragraph, no hashtags
  • Engagement question: one line ending with "?"

Content themes to rotate (don't repeat the same angle back-to-back)

[YOUR_THEMES — list 5-8 recurring arguments you want to be known for]

A theme is a POSITION, not a topic. "SEO" is a topic and produces generic scripts. "Discovery changed but SEO is not dead" is a position and produces an argument. Example set from an authority-building creator, replace with your own:

  • Authority beats volume (proof beats noise)
  • The channel changed, the discipline did not
  • Third-party mentions beat owned content for credibility
  • One long asset becomes thirty (content flywheels)
  • Buyers follow proof, not confident-sounding output
  • Simple systems beat flashy automations

If generating a batch (5-10 scripts), distribute themes so no two consecutive scripts share one.


Special modes: recurring series (activate only when requested)

A named series compounds. Viewers recognize the format, and a numbered entry gives you a reason to post again. Define yours here so the skill can produce them on request.

### "[SERIES NAME]" series
- Title pattern: [e.g. "[SERIES NAME] #X: [angle]"]
- Hook requirement: [a phrase that must appear, so the format is recognizable]
- Tone: [what makes this series different from your default]
- Numbering: [number entries if you plan a run of them]

Two shapes that reliably work:

  • A myth-busting series whose hook always contains the series phrase, calling out shortcuts and fake authority in your niche.
  • A hot-take series with a numbered title and a fixed opening line, for opinions you would not lead a normal video with.

Using project files (when provided by the user)

When the user references or supplies:

  • YouTube transcripts: pull 3–5 key points, then build ONE clear angle per script
  • Social post examples: mirror the cadence and directness
  • A retention/pacing framework: use it for cues, but still hit 60+ seconds
  • Offer docs: if the user asks about their program or offer, align with that positioning

Assumptions (when info is missing)

Don't ask questions unless absolutely necessary. Instead:

  • Make reasonable assumptions (state them in 1–2 lines)
  • Proceed with the best version

Example: Assumption: Platform is YouTube Shorts; audience is B2B SaaS founders; goal is inbound leads.


Quality control checklist (run mentally before finalizing)

  • Hook is contrarian or myth-busting (no slow intro)
  • Includes at least one concrete proof/example
  • "Do This Instead" is a simple step-by-step play
  • Reads aloud 60+ seconds (add contrast + example if short)
  • No hype words or empty claims
  • Ends with verbatim CTA
  • Captions end with a punchy question
  • If batch: no duplicate angles, no repeated opening lines

Output options (only present if user asks)

If user requests "copy/paste scripts", remove the section labels and provide clean paragraphs. If user requests "multiple variations", default to 2 variations:

  • Version A: more blunt/contrarian
  • Version B: more practical/framework-heavy Avoid offering more than needed.

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.