reel-script
Skill0 starsChanged 11 days agoMITView on GitHub
Turn one idea into an Instagram Reel the user can film today: three hooks of different types, the spoken script in their voice, on-screen text, a shot list and a length estimate. Then the caption, the keyword DM that sends the full recipe or guide as a Saypage page, and publishing through Saypage when the user asks. Use for requests like "script my next video", "I need an opening line", "help me film this recipe", "what do I say in my Reel".
4 other projects use a version of this.
Adopted by
Most recently taken up by
- fliqrlabs/instagram-creator-skillstheir own version, first seen Nov 1, 2026
- imtamiliniyan/claude-video-skillstheir own version, first seen Oct 25, 2026
- RahmanBuildsAI/ravyn-reel-kittheir own version, first seen Oct 25, 2026
- m-binimran/creator-packtheir own version, first seen Jun 14, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- RahmanBuildsAI/ravyn-reel-kit★ 9same name
- fliqrlabs/instagram-creator-skills★ 5same name
- imtamiliniyan/claude-video-skills★ 4same name
- m-binimran/creator-pack★ 3same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- carousel-postSkill
- comment-repliesSkill
- content-calendarSkill
- dm-writingSkill
- funnel-reviewSkill
- instagram-captionSkill
- natural-voiceSkill
- offer-finderSkill
- opportunity-scanSkill
- performance-reviewSkill
- profile-reviewSkill
- reel-analysisSkill
- reel-funnelSkill
- repurpose-contentSkill
- sales-planSkill
- saypageSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Start from something concrete the user lived or made: the dish that failed and why, the minutes saved, the price, the customer's reaction.
- Distinctive: line 18
If there is nothing behind the idea yet, say so rather than writing around it.
- Distinctive: line 25
Write each hook twice: the spoken line and the on-screen line (shorter, readable in one glance).
- Distinctive: line 41
Check each hook before showing it:
- Distinctive: line 50
When all three fail, rewording will not save them: go back to step 1 for a stronger fact.
- Distinctive: line 54
Write it as a list of beats, each one a line the user says plus what the camera shows:
- Distinctive: line 61
Write the way the user speaks on camera, in their words: if a sentence would need two takes, cut it in half.
- Distinctive: line 71
Write the text cards apart from the spoken lines: six words per card at most, the hook card already on screen in the first frame, and …
- Distinctive: line 74
Keep text and faces inside the middle 4:5 area of the 1080×1920 frame: the feed shows Reels cropped to 4:5, and Instagram's buttons and …
- Very specific: line 92
When this Reel is meant to sell, reel-funnel builds the whole path and tests it.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Reel script
People decide whether to keep watching almost at once, from the opening frame and line; after that, a picture that keeps changing holds them. This skill writes the words and the shots; the user films. Publishing happens only if they ask.
1. Find what the Reel is really about
Start from something concrete the user lived or made: the dish that failed and why, the minutes saved, the price, the customer's reaction. A topic alone ("pasta", "my morning routine") is not enough: ask in a single message what happened, with what number or result. If there is nothing behind the idea yet, say so rather than writing around it.
Learn the voice before writing (see natural-voice): with Saypage connected, read a few of
the user's own captions; otherwise ask for one or two Reels they recorded.
2. Three hooks, three different types
Write each hook twice: the spoken line and the on-screen line (shorter, readable in one glance). Pick three types that genuinely fit the idea, not three rewordings of one.
| Type | Example | Works when | Falls flat when |
| Result first | "Twelve minutes, one pan, crispiest gnocchi I've made." | the payoff is visible | the result looks ordinary |
| The mistake | "I salted pasta water wrong for ten years." | the fix is simple and surprising | nobody makes that mistake |
| The contradiction | "Stop rinsing your rice. Unless it's for sushi." | there is a real exception | it is contrarian for nothing |
| The number | "€2.20 a croissant, and here's where it goes." | the number is unexpected | the number is generic |
| Before / after | the burnt tart, then the perfect one | the change shows in one frame | it needs explaining |
| Their question | "Someone asked how I keep basil fresh a week." | a real comment asked it | it is invented |
| Behind the counter | "What bakeries don't tell you about 'fresh' bread." | the user knows the inside | it is a vague tease |
| The test | "I tried the 3-ingredient bread so you don't have to." | the verdict is honest | the ending is obvious |
| Mid-action | starts with the pour, the crack, the sizzle | the action itself is the hook | the first second is static |
| The stakes | "If you reheat rice like this, read this first." | the risk is real | it is fear for clicks |
Check each hook before showing it:
- Concrete: a number, a name, or something you can see.
- Fast: about eight words at most, so it is said in three seconds or less.
- Matched: the first frame shows what the line says.
- Open: it raises a question the video answers.
- Straight in: the content starts at once, without hellos, names, logos or "in this video".
Show the three with what passed and what did not, and say which one you would film and why. When all three fail, rewording will not save them: go back to step 1 for a stronger fact.
3. The script
Write it as a list of beats, each one a line the user says plus what the camera shows:
- Beat 1 is the chosen hook, said over its first frame.
- Beat 2 tells the viewer what they get by staying ("and it costs less than a coffee").
- The next beats carry one step, fact or turn each, with a new shot every few seconds.
- The last beat shows the result the hook promised, then gives the single ask.
Write the way the user speaks on camera, in their words: if a sentence would need two takes, cut it in half.
- Estimate length at about 2.5 words a second. Most useful Reels land between 20 and 40 seconds; go longer only when every beat earns its place.
- A last shot that echoes the first (the same plate, the same word) makes viewers more likely to watch it again.
- Never invent a number, a result or a customer. Leave
[your number]and ask.
4. On-screen text and shots
- Write the text cards apart from the spoken lines: six words per card at most, the hook card already on screen in the first frame, and subtitles for everything said, for the people watching with the sound off.
- Keep text and faces inside the middle 4:5 area of the 1080×1920 frame: the feed shows Reels cropped to 4:5, and Instagram's buttons and caption sit on the edges.
- A shot list: one line per beat with what is on screen (close-up of the dough, hands, the result, the price tag).
- The cover: the frame that reads at thumbnail size in the profile grid (a 3:4 crop).
5. The ask, and the page behind it
Close on a single ask, spoken and on screen. When the Reel promises more than fits (the full recipe, the menu, the guide, prices), make it a keyword: "Comment RECIPE and I'll send you the full recipe." Then, with Saypage:
- Offer to build that page, made for this Reel (the
saypageskill:get_page_guidefirst), and to create the comment-to-DM automation once the Reel is posted, with the user's approval. This is what turns the Reel's views into followers and customers: the commenters get what they asked for in seconds, from the user. On the Free plan both are built and previewed, and go live with a plan that includes them ("Plans" in thesaypageskill). - When this Reel is meant to sell,
reel-funnelbuilds the whole path and tests it. - The keyword rules are in
instagram-caption; write the caption with that skill too.
6. Publishing (only if the user asks)
Publishing needs can_publish_posts in get_account, which is optional and off by
default. With it on, the user uploads the edited video (request_upload_link in chat
apps, start_video_upload with a shell), then, after they approve the final caption:
publish_instagram_video with kind: "reel", cover_frame_ms or cover_image for the
cover, and trial: "manual" or "auto" to try it first as a trial Reel shown to
non-followers. Set ai_generated when it shows realistic AI-made people or voices. Saypage
deletes an unpublished video after an hour, and a published one cannot be stopped.
Output
The three scored hooks, then the script in a code block, the on-screen cards with their timing, the shot list, and a summary:
Hook Result first: "Twelve minutes, one pan, crispiest gnocchi I've made."
Length about 28 s, 9 beats
Ask Comment GNOCCHI -> recipe page by DM (page: to build)
Next caption with instagram-captionDoes 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.

