All skills
Writing
Reel script from a topic
A topic becomes a hook, a 20-second script and a caption.
The demo uses fictional data. The output shown is what the skill produced on that sample input.
Try it in 3 steps
- 01
Copy the folder, or just SKILL.md, into .claude/skills/ in your project (or into ~/.claude/skills/ to use it everywhere).
- 02
Open Claude Code and ask for it by name, for example: Use the reel-script-writer skill on my files.
- 03
Check the result. Skills write a new file and never overwrite yours.
See the sample run
Sample input · input.md
Topic: Why a houseplant droops after repotting and what to do about it Audience: busy beginners with a few houseplants, ages 25 to 40 Platform: Instagram Reels Tone: friendly, plain, no drama Facts I can stand behind: - Repotting stresses the roots, so some drooping is common. - A new pot only 2 to 3 cm wider is enough. - Overwatering is the usual reason a plant keeps declining after repotting. - Wait about a week before fertilizing. CTA keyword: PLANT What viewers get: my one-page repotting checklist
Sample output · output.md
# Reel script: Drooping after repotting ## Hook (6 words) Your plant isn't dead. It's stressed. ## Script (54 words, about 22 seconds) ``` Repotted your plant and it started drooping? That's usually root stress, not a death sentence. Mistake one: a pot far too big. Go only 2 to 3 cm wider. Mistake two: overwatering to make up for it. Water lightly, then wait for the top soil to dry. And skip fertilizer for about a week. ``` ## On-screen text - Drooping after repotting? - Mistake 1: pot too big - Mistake 2: overwatering - Skip fertilizer for a week ## Caption Some drooping after repotting is common. Roots need calm, not extra care. Comment PLANT and I'll send you my one-page repotting checklist. #houseplants #plantcare #repotting #plantbeginners ## Claims check | Claim in script | Supported by input | |---|---| | Drooping is root stress | Repotting stresses the roots | | 2 to 3 cm wider | Pot only 2 to 3 cm wider is enough | | Overwatering | Usual reason a plant keeps declining | | No fertilizer for a week | Wait about a week before fertilizing |
The skill · SKILL.md
---
name: reel-script-writer
description: Turns a topic and an audience into a short-video script pack: a hook, a roughly 20-second script, on-screen text and a caption with a comment-keyword CTA. Use when someone needs a reel, short or TikTok script from a topic they know well.
---
# Reel Script Writer
Topic and audience in, a ready-to-record 20-second script pack out.
## When to use
- You have a topic and know who it is for, and you want a short vertical-video script.
- You want honest, plain scripts without hype.
## Inputs
- Topic (one sentence) and audience (who, how experienced). Ask if either is missing.
- Facts the creator can stand behind. If none are given, ask; do not fill the gap.
- Optional: platform, tone, the CTA keyword and what the viewer receives for commenting.
## Steps
1. Read the input and list the facts you may use. Anything not listed is off limits.
2. Write the hook: 8 words or fewer, one clear tension or promise of the topic itself.
3. Write the script as short lines, one idea per line, spoken aloud. Target 45 to 55 words in total (about 20 seconds at 2.5 words per second). Start by naming the viewer's problem, give 2 or 3 concrete points, end on one calm takeaway.
4. Count the words and report them.
5. Write 3 to 5 on-screen text overlays, each 6 words or fewer, matching the script order.
6. Write the caption: 1 to 2 sentences, then the CTA "Comment KEYWORD and I'll send you ...", then at most 5 hashtags.
7. Add a Claims check table: each factual claim in the script next to the input fact that supports it.
## Output
Write `reel-script.md` next to the input in this layout:
`# Reel script: <title>`, `## Hook (N words)`, `## Script (N words, about N seconds)` as a plain-text block, `## On-screen text`, `## Caption`, `## Claims check`.
## Rules
- Never invent facts, numbers, results or quotes. Use only what the input supplies.
- No income or result promises ("you will earn", "in 7 days you will ..."). No fake scarcity or fake deadlines.
- Keep claims honest and modest; mark anything uncertain as "unverified" in the Claims check.
- Ask before assuming a missing audience, fact or CTA.
- Write results to a new file, never overwrite the input or an earlier script.
- Keep private data local. Legal, medical, tax and financial claims are out of scope: flag them for a professional and do not advise.
Skills help you read and organise. They are not legal, medical, tax or financial advice.


