shorts-writer
Skill5 starsChanged 45 days agoMITView on GitHub
Write short video scripts in the style of a developer-focused tech shorts channel. Use when the user asks to write a short, create a short video script, or make a script for a short about a tool, technique, or concept.
In this repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- delegateSkill
- finish-featureSkill
- new-projectSkill
- prune-context-fileSkill
- questionsSkill
- reddit-firecrawl-supportSkill
- reference-led-websitesSkill
- say-as-meSkill
- short-edit-beaconSkill
- short-editSkill
- shortSkill
- site-designSkill
- sync-docsSkill
- title-researchSkill
- title-scoreSkill
- tweetSkill
- verifySkill
- video-scriptSkill
- wdytSkill
- website-reference-curatorSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Before writing, read all files in the references/ directory inside this skill to absorb the tone, rhythm, and structure of existing scripts.
- Distinctive: line 10
Start with a hook that subverts an assumption the audience already has — the pattern is "everyone thinks or does X, but what they don't …
- Distinctive: line 12
No punctuation at the end of lines
- Distinctive: line 17
No section headers — one flowing script
- Very specific: line 22
Write the script directly.
- Very specific: line 24
After saving, if ~/.config/voice-clone/reference.wav exists, offer once to voice the script with the say-as-me skill.
≈ “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.
Files
Before writing, read all files in the references/ directory inside this skill to absorb the tone, rhythm, and structure of existing scripts. Use those as your style guide, not this description.
Rules
- Start with a hook that subverts an assumption the audience already has — the pattern is "everyone thinks or does X, but what they don't know is Y". Don't use those exact words every time, but keep that contrast
- One idea per line, short and punchy
- No punctuation at the end of lines
- Lowercase throughout
- Name the tool or product mid-script, not in the opening line
- Give an honest take on any limitations or annoying things
- End with "subscribe for more" and a short relevant sign-off
- No section headers — one flowing script
- Scripts must be no more than 30 lines (excluding blank lines)
Output
Write the script directly. Create a new directory named after the topic inside the user's current working directory and save the script as a .md file inside it.
After saving, if ~/.config/voice-clone/reference.wav exists, offer once to voice the script with the say-as-me skill. Don't generate audio unless the user says yes; it costs a few cents.
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
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.