ig-reel

Q: How do I install ig-reel?

Run npx skills add https://github.com/jakeschincariol/instagram-agent-skill --skill ig-reel in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ig-reel/ (personal) or .claude/skills/ig-reel/ (project).

by jakeschincariolMedia & Creative

Write an Instagram Reel from a raw idea - hook options off 26 formulas, the spoken script, the on-screen text, and a timed beat sheet - in the user's own voice and scored before they shoot it. Use whenever the user wants a Reel, a short-form video script, a hook, a voiceover, "make a reel about X", "what should I say in this video", or is about to record and does not have the first line yet.

Installs: 572
Last 24h: +47
Trending rank: #3518
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/jakeschincariol/instagram-agent-skill --skill ig-reel

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads ig-reel automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

ig-reel

Turns one raw idea into a Reel that somebody finishes.

Two tools live in this folder and they both actually run. Use them. Do not eyeball the hook and do not guess at the length.

python3 hookscore.py hooks.txt              # rank your hook options
python3 hookscore.py --hook "one line"      # score a single one
python3 beats.py script.txt --target 30     # timed beat sheet before you shoot

Before you write

Read ~/.claude/instagram/voice.md if it exists. That is the user's voice profile: how they talk on camera, what they never say, who they are talking to. If it does not exist, ask for three of their own reels, transcribe or read them, infer the voice, and write the file. A script in the wrong voice is unusable, because they have to say it out loud.
Read hooks.json in this folder. 26 formulas, each with a template, a filled example, the on-screen version, what it is for, and how it gets ruined. Four of them are in there because they kept turning up in real hooks, not because they completed a pattern.
If the idea is thin, do not pad it. Ask one batched question: what happened, to whom, and what did it cost or return. A Reel needs one specific true thing. Get it before writing.
If ~/.claude/instagram/swipe.md exists, read it. /ig-viral writes that file, and it is the user's own evidence about which formulas are working in their niche right now. It beats the defaults in this file.

The shape

A Reel is decided in the first two seconds and kept by the next five.

0:00 - 0:02   HOOK        the claim. Spoken line and on-screen line, written
                          separately. Motion in the first frame, not a static face.
0:02 - 0:07   THE STAKE   why this matters to the person watching. One line.
0:07 - ...    THE BODY    one idea per beat, and the frame changes every beat.
LAST 3s       THE PAYOFF  deliver what the hook promised, then the single ask.
LAST LINE     THE LOOP    echo one word from the hook so the replay lands clean.

Length: 15 to 45 seconds is the working range. Reels run to 3 minutes and almost nobody should use it. Under 7 seconds the loop counts inflate and nothing else does.

The loop

1. Pick three hooks, not one. Run the idea through hooks.json, choose three formulas that genuinely fit it, and write the spoken line plus the on-screen line for each. Different formulas, not three rewrites of one.

2. Score them. Put the three spoken lines in a file, one per line, and run hookscore.py. Show the user the ranking. If the top one is under 50, you do not have the hook yet and no amount of editing fixes that.

3. Write the script on the winning hook. Plain spoken language, the way the user actually talks. Contractions. Short lines. No sentence they would have to rehearse.

4. Time it. Run beats.py script.txt --target {length}. Fix every flag: a hook past 3 seconds, any beat over 4 seconds, a run of beats with nothing concrete in them, no loop. Re-run until it is clean.

5. Humanize it. Run the script through /ig-human before showing it. A written-sounding line is obvious the moment someone says it out loud.

6. Print the block. The script in a fenced block, the on-screen text as a separate list with timings, and then:

REEL READY
hook:       #3 Nobody Tells You, scored 86 STRONG
length:     28.4s across 9 beats at 165 wpm
on-screen:  6 cards
humanizer:  4 artefacts stripped, human score 81 PASS
caption:    run /ig-caption next

Reply "yes" to log it, or tell me what to change.

7. Never publish. This skill produces a script. The user shoots it and posts it. On "yes", append to ~/.claude/instagram/log.md with the date, the hook formula used and the first line, so /ig-audit has a history later.

On-screen text is a separate script

Write it separately, every time. It is read before it is heard.

Six words or fewer per card. It is being read at arm's length by someone who is not listening yet.
The hook card is up at frame 1, not after a beat of silence.
Keep it inside the safe zone. On a 1080x1920 frame, nothing above y=230 or below y=1440, and keep the right 230 pixels clear. The interface sits on top of everything outside that box: the caption, the action rail, the audio strip.
Never put the hook where the caption sits. That is the bottom of the frame and it is covered.
Burn in captions for the body. Most people watch muted first.

Rules that make the difference

One idea per Reel. If the script has two, you have two Reels. Say so.
Numbers over adjectives. "$4,200" beats "a lot". If the user has not given a number, ask for one rather than writing around the hole.
Cut the intro. No greeting, no "in this video", no name, no logo sting. The video starts at the sentence you would normally reach at second six.
Change the frame every beat. A static shot for 8 seconds is where people leave, and beats.py will flag it.
One ask at the end. Comment a keyword, save it, or follow. One.
Never fabricate. No invented metrics, clients, revenue or outcomes under the user's name, even as a placeholder. If a number is needed and unknown, leave {{your number}} in the script and flag it.
Do not write a script around a trending audio the user cannot use. If the idea needs the user's own voice, say so.

Example

/ig-reel we cut proposal time from 5 hours to 20 minutes with one template

HOOKS  (scored)
  86  STRONG  #5  Time Collapse   "Proposals used to take me five hours. Twenty minutes now."
                                  on screen: 5 HOURS -> 20 MIN
  71  STRONG  #1  Cost Confession "I billed four hours a week for formatting. For two years."
                                  on screen: 2 YEARS WASTED
  54  OK      #9  The Steal       "Steal the proposal template that did it."
                                  on screen: STEAL THIS

Shooting #5: the ratio is believable, it reads in one glance on screen,
and the number is yours.

FAQ

What does the ig-reel skill do?

How do I install ig-reel?

Run npx skills add https://github.com/jakeschincariol/instagram-agent-skill --skill ig-reel in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ig-reel/ (personal) or .claude/skills/ig-reel/ (project).

Which AI agents can use ig-reel?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is ig-reel safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains ig-reel?

It is published by jakeschincariol in jakeschincariol/instagram-agent-skill. It has 572 recorded installs.