social-video-hooks
Skill18 starsChanged 48 days agoMITView on GitHub
Write short-form video hooks and beat sheets for Reels, TikTok, Shorts, and similar feeds. Use when planning an opening, improving retention, or giving a creator precise shooting instructions.
In this repository10 other files it gives its agents.
- brand-filmSkill
- brand-grid-videoSkill
- creator-videoSkill
- feature-videoSkill
- narrated-product-filmSkill
- silent-product-demoSkill
- ui-component-clipSkill
- ui-tutorial-videoSkill
- video-brand-systemSkill
- video-thumbnailsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Distinctive: line 13
Visible test: start a comparison or challenge the viewer can follow.
- Distinctive: line 16
Direct question: ask something the intended viewer can answer from experience.
- Distinctive: line 28
Place the proof before a long explanation.
- Distinctive: line 33
Every spoken line can be performed naturally.
- Distinctive: line 35
No beat is held past the point where the viewer has understood it.
≈ “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
Social video hooks
Make the opening understandable in one second: show a meaningful action or result, say why it matters, and use on-screen text only when it adds clarity. The visual, spoken line, and title should support the same idea without repeating the same words.
Choose the hook
- Result first: show the finished outcome before the process.
- Visible test: start a comparison or challenge the viewer can follow.
- Specific problem: show a familiar frustration in its real setting.
- Surprising action: begin with behavior that creates a question the rest of the clip answers.
- Direct question: ask something the intended viewer can answer from experience.
Choose one primary hook. Add a second visual or text cue only when it clarifies the premise. Do not promise a result the video cannot show.
Write a timed beat sheet
For each beat, give the exact spoken words, the camera or screen action, and what new information the viewer gets. Example:
| Time | Say | Show | New information |
| 0:00 | “Can this finish before my coffee?” | Start the task and timer | The test begins |
Place the proof before a long explanation. Change framing or introduce new evidence when the current image has finished making its point. A cut, caption, or zoom is useful only if it advances understanding. Finish with one call to action that follows from the video.
Check the script
- The opening makes sense with sound off and with sound on.
- Every spoken line can be performed naturally.
- The visuals prove the main claim.
- No beat is held past the point where the viewer has understood it.
- The call to action is clear and proportionate to what was shown.
Deliver the beat sheet and a short shot list. If a promised result requires data or footage that is missing, flag it before treating the script as shoot-ready.
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.

