shorts-script
Write, check, score or rewrite a YouTube Shorts script in the user's Script.txt house format (a claim-first hook, a question with the answer withheld, one step per line, an everyday comparison for every number, a late reframe, a 165 wpm budget, an ending that can loop back into the hook), with a checker script that scores drafts. Use whenever the user wants a script, hook or voiceover text for a short or reel, gives a topic "for a short", or points at a Script.txt or draft to check, tighten, shorten or fix, even without naming the skill. Not for shot lists, animation or video editing.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/masje1--shorts-script)HTML
<a href="/listings/masje1--shorts-script"><img src="/api/listings/masje1--shorts-script/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Copy this folder to `~/.claude/skills/shorts-script`. Needs Python 3 and `pip install num2words`.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 50 lines
- ---
- name: shorts-script
- description: Write, check, score or rewrite a YouTube Shorts script in the user's Script.txt house format (a claim-first hook, a question with the answer withheld, one step per line, an everyday comparison for every number, a late reframe, a 165 wpm budget, an ending that can loop back into the hook), with a checker script that scores drafts. Use whenever the user wants a script, hook or voiceover text for a short or reel, gives a topic "for a short", or points at a Script.txt or draft to check, tighten, shorten or fix, even without naming the skill. Not for shot lists, animation or video editing.
- ---
- # Shorts script
- Harper's taste, taught by his own shorts: `references/approved/` holds five he likes (`notes.md` says why each works) and `references/rejected.md` what he threw out and why. Imitate the shape, never the phrases or the facts. A brief that gives its own structure wins over the defaults here.
- ## Script.txt format
- ```
- <Title>
- <line 1>
- <line 2>
- ...
- <last line>
- (N lines, about X s at 165 words per minute)
- ```
- - One beat per line (each line becomes one shot); fragments fine.
- - Numbers spelled out as said ("seventeen kilometres per second"); years and names with numbers stay digits (2024, Voyager 1). Metric, British spelling.
- - No labels, notes or stage directions in the file. Footer exactly as the checker prints it.
- - The last line may end on "…" or ":" and run straight into line 1 when the seam reads naturally. Never a CTA, outro or closing question.
- ## Eight rules
- 1. Line 1 is the claim, concrete from the first word: not a scene-setter, no greeting, no "did you know".
- 2. Line 2 makes it a question the viewer wants answered. The answer is withheld; each line after it is one step of the how and follows from the last.
- 3. Every big number gets an everyday comparison (17 km/s = twenty times a sniper rifle bullet). No room for the comparison: cut the number, never leave it bare.
- 4. Name each thing plainly and keep calling it that: no synonyms, no decoration.
- 5. A signpost ("Let me explain", "here's the crazy part") only where the next line is the real turn or answer; two at most.
- 6. A late line reframes it (what it means, what is surprising). Never a recap.
- 7. Budget at 165 wpm (an estimate, not a reading pace): Harper's approved scripts run 101-135 words, 34-42 s on screen. Take the target in seconds from the brief (45 if none): 45 s is about 110-135 words. Over budget: cut whole facts.
- 8. End on the idea, or loop back into line 1 when it reads naturally.
- Write it so a ten-year-old follows it, told as a story: each line adds something new and follows from the last.
- ## Workflow
- 1. Read `references/approved/*.txt`, `references/approved/notes.md` and `references/rejected.md` before drafting.
- 2. Research 3-6 facts (NASA, ESA, journals, major outlets); unverifiable: cut or flag. Round as people speak. When the brief gives a `research.md` or figures, use them and check every comparison against them.
- 3. Draft in the format. Take the hook shape the idea already has (a flat claim, "this is X, but...", a myth flip, "X, but not Y"); never a template, and never the skeleton of the last script.
- 4. Run `python <skill>/scripts/check_script.py "<path>/Script.txt" --target <seconds from the brief, 45 if none> [--summary] [--json]` (`-` reads stdin; `pip install num2words` if missing). Fix every FAIL; fix each WARN or say why not. Rule IDs are in `references/rules.md`: search for an ID, don't read it whole.
- 5. Critique once, in this context, fix what you find, and don't show it. Does line 1 hit, or set a scene? Does line 2 undo line 1? Is anything called by two names? Does a signpost only announce more setup? Does every number land a comparison? Does each line follow from the last? Could a ten-year-old follow it? Could it be made from the last script by swapping nouns? Time-sensitive facts get a ready-to-paste after-date line.
- 6. Save to the path the brief gives, else `Script.txt` in the working folder.
- ## Editing or checking a draft
- Run the checker, list problems worst first (rule ID, the quoted line, the fix), then edit that draft, changing as little as needed and keeping Harper's voice and facts. Never redo the research or rewrite the whole script. Give both scores.
- ## Reply
- The script (or its path); checker result and kept WARNs with reasons; each fact and its source, flagging anything unverified; the loop seam if there is one (last line + line 1); two alternative hooks of different shapes. About 300 words around the script.
README.md · README · 58 lines
- # shorts-script
- A Claude skill that writes, checks and rewrites YouTube Shorts scripts for one specific voice: the "harper." space and science channel. A script is 34-42 s of spoken lines, told so a ten-year-old follows it. It opens on a concrete claim, asks the question the viewer wants answered, builds the answer one step per line, gives every number an everyday comparison, and ends on a reframe.
- The taste is the point, not a setting: `references/approved/` holds five of the channel's own shorts, `references/approved/notes.md` says why each works, and `references/rejected.md` lists what the author threw out and why.
- ## Reads
- - A topic or brief ("a short on how Voyager still has power, 52-56 s, spend most of it on the generator"), optionally with a research file of figures to use.
- - Or an existing `Script.txt` to check, tighten or fix. A fix edits that draft; it never redoes the research or the whole script.
- ## Writes
- `Script.txt` (or the path the brief gives): a title, a blank line, one spoken line per line, and a footer exactly as the checker prints it. Numbers are spelled out as said (years stay digits), British spelling, no labels or stage directions. The last line may run on into line 1 when the seam reads naturally; never a call to action.
- Sample brief: *a short on how Voyager still has power, no solar panels, about 54 s.* Sample output:
- ```
- How Voyager still has power
- Voyager's three generators have worked for forty-nine years with no moving parts.
- So where does the electricity come from?
- Not solar panels. At Neptune, sunlight is like a desk lamp at the far end of a football field.
- The generators run on plutonium, whose atoms keep breaking apart and giving off heat.
- That keeps one side of each generator near a thousand degrees, four times hotter than your oven.
- The other side faces space, seven hundred degrees cooler but still hotter than boiling water.
- Between them sit hundreds of pairs of metal strips.
- In each pair, one end is hot, one is cold, and that gap pushes electricity through the metal.
- But only six per cent of the heat becomes power, enough for eight old light bulbs at launch.
- The plutonium is fading, so Voyager has less than half its launch power.
- So for now, the cold of empty space is what keeps Voyager alive.
- (11 lines, about 57 s at 165 words per minute)
- ```
- ## Install
- Copy this folder to `~/.claude/skills/shorts-script`. Needs Python 3 and `pip install num2words`.
- ## The checker
- ```
- python scripts/check_script.py Script.txt --target 45 [--summary] [--json]
- ```
- `--target` is the length in seconds from the brief (45 if none). FAIL means fix it, WARN means fix it or say why not, TIP is a nudge. Rule IDs are explained in `references/rules.md`. The checker only measures what code can see (length, hook, signpost count, repeated openers, spelling of numbers, the ending); whether line 1 really hits, or whether a signpost earns its place, is judged by the skill's critique pass against the examples.
- ## Tests and evals
- - Tests: `python -m unittest discover -s scripts -p "test_*.py"`. They pin the checker's rules and check that none of the five approved scripts FAILs.
- - Evals: `evals/` holds five cases (a prompt, input files and graders each): new scripts, a fix of a flawed draft, a draft with forced signposts.
- ## Layout
- ```
- SKILL.md the workflow and eight rules
- references/approved/ five approved scripts + notes.md
- references/rejected.md what was thrown out, and why
- references/rules.md what each checker rule ID means
- scripts/ check_script.py and its tests
- evals/ test cases
- ```
- ## What it does not do
- Shot lists, animation, video editing, or sourcing real footage. It makes the script and nothing else.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.