Claude Skill

reverse-video

Reverse-engineer any reel's editing style from a link - travel and cinematic montages, B-roll and music edits, talking heads, tutorials, product videos. context.dev scrapes the reel or TikTok, then every frame is measured (cuts, shot lengths, transitions, camera moves, framing an

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Download kjagsadvisors-keeran.ai-reverse-video-329ead4.zip · 17 KB

Install

skills CLI npx skills add https://github.com/kjagsadvisors/keeran.ai/tree/main/reverse-video
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install kjagsadvisors-keeran-ai@llmmart
Git git clone https://github.com/kjagsadvisors/keeran.ai.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole kjagsadvisors/keeran.ai collection as a plugin from our marketplace. Git is the plain clone.

README

reverse-video, a Claude Code skill

Paste a link to any reel: a travel montage, a cinematic edit, a talking head, a tutorial. Claude scrapes the video with context.dev, analyzes every single frame, and writes down exactly how it was edited. Then it edits your footage the same way.

What it measures, from every frame:

Rhythm every cut, shot lengths, how long the opening holds, whips, flashes and dips, push-ins and pans
Sound tempo, how many cuts land on the beat, where the drop is and how the cutting speeds up after it, the hook
Look full frame or a 16:9 / 4:3 / 2.39:1 band, the colour grade (blacks, contrast, saturation, warm or teal), palette
Text how much is on screen, where it sits, how big, caps or not, how heavy, which colours, word-by-word builds

You get a STYLE.md with every number, a frame from every shot, and a timeline of cuts, text, beats and loudness. Claude reads it and edits your footage to match: a folder of travel clips and a song becomes a montage cut and graded like the reference; a talking-head take gets its pacing, captions and look.

Install

The easy way: paste the repo link into Claude Code and say "set up the reverse-video skill":

https://github.com/kjagsadvisors/keeran.ai

By hand (Mac):

  1. Copy the reverse-video folder into ~/.claude/skills/.
  2. Install the tools once:
    xcode-select --install
    brew install ffmpeg
    pip3 install opencv-python numpy pillow librosa faster-whisper
    

Connect context.dev

The first time you use the skill, Claude walks you through this. To do it yourself:

  1. Make your free account with this link. The free plan is enough: 1,000 credits a month, and one video link is 1 credit.
  2. Upgrading? Code KEERAN25OFF takes 25% off your first 6 months.
  3. Connect it:
    claude mcp add --transport http context https://mcp.context.dev/mcp
    
    Then type /mcp in Claude Code and sign in to context. In the Claude app: Settings > Connectors > Add custom connector, URL https://mcp.context.dev/mcp.
  4. Check everything with python3 ~/.claude/skills/reverse-video/reverse.py setup.

That's my referral link, so I may earn a commission when you sign up or upgrade through it.

Use it

/reverse-video https://www.instagram.com/reel/...  then edit my-take.mp4 like it
/reverse-video https://www.tiktok.com/@.../video/...  then cut my clips in ~/Travel/Japan to my song like this

Works with Instagram reels and TikToks, or any video file you have.

Copy the style, not the content: never reuse someone else's footage, voice, words or music.

Skill manifest

reverse-video

Paste a link to any reel (a travel montage, a cinematic B-roll edit, a talking head, a tutorial), get its editing style as numbers, then edit the user's own footage to match. Copy the style, never the content.

Onboarding (first run, and any time context.dev isn't connected)

reverse.py sits next to this file: python3 <skill>/reverse.py ....

  1. Check the tools. Run python3 <skill>/reverse.py setup. It checks ffmpeg, the Xcode command line tools, the Python packages and builds the on-device text reader (bin/vision). For each !! line, show the fix it prints and offer to run it. Mac only: the text and face reader is Apple Vision.
  2. Check context.dev. Look at your own tools: context.dev's tools are named web-scrape, get-usage and so on, under a server called context (or a connector named Context.dev). If they're there, skip to step 4.
  3. Walk them through it, in this order, with these exact links:
    • "First, make a free context.dev account: https://link.context.dev/keeran-jagadesan. The free plan gives you 1,000 credits a month, and one video link costs 1 credit."
    • "If you ever upgrade, code KEERAN25OFF takes 25% off your first 6 months."
    • "That's Keeran's referral link, so he may earn a commission if you sign up or upgrade through it."
    • Connect it. In Claude Code, offer to run this for them (ask first):
      claude mcp add --transport http context https://mcp.context.dev/mcp
      
      then tell them to type /mcp, pick context and sign in with the account they just made. In the Claude app: Settings > Connectors > Add custom connector, URL https://mcp.context.dev/mcp.
    • A new connector shows up after Claude Code restarts. Tell them to restart and paste their link again. Always use the link above, never the bare context.dev address, and always say it's a referral link.
  4. Confirm it works. Call context.dev's get-usage (it costs no credits) and tell them how many credits they have. Then go on to step 1 below with their link.

If they don't want to connect context.dev, they can still use a video file they already have: skip step 1 below.

Every run

1. Get the video

Link context.dev call You get
Instagram reel or post (/reel/, /p/) web-scrape formats.parse, parseParams: {type: "prebuilt", parser: "instagram-post"} video_url, caption, views, likes, comments, posted date
TikTok video same, parser tiktok-video video_url (downloads without cookies), counts, music
A creator's page parser instagram-profile or tiktok-feed, then pick the post their latest posts with counts
A file the user has skip this step
python3 <skill>/reverse.py fetch "<video_url>" study

Save the parser's caption and counts to study/post.json. The video_url expires after a few hours, so fetch right away.

2. Take it apart

python3 <skill>/reverse.py analyze study/video.mp4 -o study

About 20 seconds for a 30-second reel. It reads every frame and writes:

  • STYLE.md: rhythm (cuts, shot lengths, opening hold, transitions: hard cut, whip, flash, dip; camera moves: push-in, pull-out, pan; tempo, cuts on the beat, where the drop is and how the cutting speeds up after it, loudness, words per second), text on screen (how much, how big, how far down, caps, weight, colours, word-by-word builds), look (framing: full frame or a 16:9 / 4:3 / 2.39:1 band and where it sits; the grade: black point, contrast, saturation, warmth, shadow and highlight tint; palette, faces), the hook, a shot list with each shot's length, transition in, move and energy, and a text track. Add --no-words for a reel with no talking.
  • shots.jpg (one frame per shot), timeline.png (cuts, text, beats, loudness on one strip), style.json, detail.json, frames.csv (every frame's numbers).

3. Look, then write the read

Open shots.jpg, timeline.png and a strip of the video (ffmpeg -i study/video.mp4 -vf "fps=2,scale=144:-1,tile=11x5" -frames:v 1 study/strip.jpg). The numbers can't tell a phone filming a laptop from a screen recording, or a meme from B-roll. You can. Fill in "The read" at the bottom of STYLE.md:

  • Format: what the video is, shot by shot (talking head, split screen, phone filming a screen, B-roll over voice).
  • Hook: what happens in the opening hold, on screen and said.
  • What makes it feel like itself: the three or four choices that carry it.
  • To copy it on a new clip: a recipe with the measured numbers.

Treat the text readings as hints: OCR picks up words inside screenshots too. Check the caption numbers against the strip.

4. Edit the user's footage the same way

Ask what they're working with, then write an edit plan from the read before you touch anything.

A montage (travel, cinematic, B-roll, music-driven). They give you a folder of clips and a song.

  • Shot list: copy the reference's shot count and lengths, scaled to their song's tempo, so cuts land on their beat the way the reference's do (the measured share on the beat). Hold the opening as long as the reference does; if the cutting speeds up after the drop, find their song's drop and do the same.
  • Fill each slot with their clip that fits: wides where the reference has wides, people where it has people, the strongest shot on the drop. Pull the best moment of each clip, not its first second.
  • Framing: same as the reference (a 16:9 band in a 9:16 frame at the measured height, a 2.39:1 letterbox, or full frame). Never mix framings inside one reel.
  • Grade: match the numbers (black point, contrast, saturation, shadow and highlight tint, warmth) with the user's own colour tools or ffmpeg (eq, curves, colorbalance). Log or flat footage gets a normal conversion first.
  • Transitions and moves: the same kinds in the same places (whips where it whips, push-ins where it pushes in).
  • Text: their own words, in the reference's position, size and case.

A talking head or tutorial. They give you a take.

  • Opening hold, then the measured cut rhythm as punch-ins or B-roll cuts, captions in the measured position, size, case, weight and colours, the same amount of text on screen, the same end card. For logos and screenshots the edit needs, use the b-roll skill.

Then edit with whatever they use: their own Claude editing skill, Remotion, HyperFrames, ffmpeg, or export the plan as a cut list for CapCut, Premiere or Resolve. Show the plan first, then the render next to the reference.

Rules

  • Copy the style, not the content. Never reuse the creator's footage, face, voice, words, music file, logo or watermark. Captions are the user's own words.
  • The download is for study. Don't repost it or put it in the user's edit.
  • Numbers come from the measurement. If something wasn't measured (the font's name, the music track), say so.
  • A measurement is one video. Say so before you call something "their style".
Files (keeran.ai)
  • .gitignore 18 B · in bundle
  • README.md 2.7 KB
    # reverse-video, a Claude Code skill
    
    Paste a link to any reel: a travel montage, a cinematic edit, a talking head, a tutorial. Claude scrapes the video
    with [context.dev](https://link.context.dev/keeran-jagadesan), analyzes every single frame, and writes down exactly
    how it was edited. Then it edits your footage the same way.
    
    What it measures, from every frame:
    
    | | |
    |---|---|
    | Rhythm | every cut, shot lengths, how long the opening holds, whips, flashes and dips, push-ins and pans |
    | Sound | tempo, how many cuts land on the beat, where the drop is and how the cutting speeds up after it, the hook |
    | Look | full frame or a 16:9 / 4:3 / 2.39:1 band, the colour grade (blacks, contrast, saturation, warm or teal), palette |
    | Text | how much is on screen, where it sits, how big, caps or not, how heavy, which colours, word-by-word builds |
    
    You get a `STYLE.md` with every number, a frame from every shot, and a timeline of cuts, text, beats and loudness.
    Claude reads it and edits your footage to match: a folder of travel clips and a song becomes a montage cut and graded
    like the reference; a talking-head take gets its pacing, captions and look.
    
    ## Install
    
    **The easy way:** paste the repo link into Claude Code and say "set up the reverse-video skill":
    
    ```
    https://github.com/kjagsadvisors/keeran.ai
    ```
    
    **By hand (Mac):**
    
    1. Copy the `reverse-video` folder into `~/.claude/skills/`.
    2. Install the tools once:
       ```bash
       xcode-select --install
       brew install ffmpeg
       pip3 install opencv-python numpy pillow librosa faster-whisper
       ```
    
    ## Connect context.dev
    
    The first time you use the skill, Claude walks you through this. To do it yourself:
    
    1. Make your free account with [this link](https://link.context.dev/keeran-jagadesan). The free plan is enough:
       1,000 credits a month, and one video link is 1 credit.
    2. Upgrading? Code **KEERAN25OFF** takes 25% off your first 6 months.
    3. Connect it:
       ```bash
       claude mcp add --transport http context https://mcp.context.dev/mcp
       ```
       Then type `/mcp` in Claude Code and sign in to `context`. In the Claude app: Settings > Connectors > Add custom
       connector, URL `https://mcp.context.dev/mcp`.
    4. Check everything with `python3 ~/.claude/skills/reverse-video/reverse.py setup`.
    
    That's my referral link, so I may earn a commission when you sign up or upgrade through it.
    
    ## Use it
    
    ```
    /reverse-video https://www.instagram.com/reel/...  then edit my-take.mp4 like it
    /reverse-video https://www.tiktok.com/@.../video/...  then cut my clips in ~/Travel/Japan to my song like this
    ```
    
    Works with Instagram reels and TikToks, or any video file you have.
    
    Copy the style, not the content: never reuse someone else's footage, voice, words or music.
    
  • reverse.py 33.6 KB
    Loading…
  • SKILL.md 7.6 KB
    ---
    name: reverse-video
    description: Reverse-engineer any reel's editing style from a link - travel and cinematic montages, B-roll and music edits, talking heads, tutorials, product videos. context.dev scrapes the reel or TikTok, then every frame is measured (cuts, shot lengths, transitions, camera moves, framing and letterbox bands, the colour grade, on-screen text, faces, tempo, cuts on the beat, the drop, loudness, the hook) into a STYLE.md, so Claude can edit the user's own footage the same way. Use when someone pastes a reel/TikTok/video link and wants "edit mine like this", "copy this editing style", "how was this edited", "reverse engineer this video", "break down this reel", or wants to match a creator's pacing, grade, captions or look.
    ---
    
    # reverse-video
    
    Paste a link to any reel (a travel montage, a cinematic B-roll edit, a talking head, a tutorial), get its editing
    style as numbers, then edit the user's own footage to match. Copy the style, never the content.
    
    ## Onboarding (first run, and any time context.dev isn't connected)
    
    `reverse.py` sits next to this file: `python3 <skill>/reverse.py ...`.
    
    1. **Check the tools.** Run `python3 <skill>/reverse.py setup`. It checks ffmpeg, the Xcode command line tools, the
       Python packages and builds the on-device text reader (`bin/vision`). For each `!!` line, show the fix it prints
       and offer to run it. Mac only: the text and face reader is Apple Vision.
    2. **Check context.dev.** Look at your own tools: context.dev's tools are named `web-scrape`, `get-usage` and so on,
       under a server called `context` (or a connector named Context.dev). If they're there, skip to step 4.
    3. **Walk them through it, in this order, with these exact links:**
       - "First, make a free context.dev account: **https://link.context.dev/keeran-jagadesan**. The free plan gives you
         1,000 credits a month, and one video link costs 1 credit."
       - "If you ever upgrade, code **KEERAN25OFF** takes 25% off your first 6 months."
       - "That's Keeran's referral link, so he may earn a commission if you sign up or upgrade through it."
       - Connect it. In Claude Code, offer to run this for them (ask first):
         ```bash
         claude mcp add --transport http context https://mcp.context.dev/mcp
         ```
         then tell them to type `/mcp`, pick `context` and sign in with the account they just made. In the Claude app:
         Settings > Connectors > Add custom connector, URL `https://mcp.context.dev/mcp`.
       - A new connector shows up after Claude Code restarts. Tell them to restart and paste their link again.
       Always use the link above, never the bare context.dev address, and always say it's a referral link.
    4. **Confirm it works.** Call context.dev's `get-usage` (it costs no credits) and tell them how many credits they
       have. Then go on to step 1 below with their link.
    
    If they don't want to connect context.dev, they can still use a video file they already have: skip step 1 below.
    
    ## Every run
    
    ### 1. Get the video
    
    | Link | context.dev call | You get |
    |---|---|---|
    | Instagram reel or post (`/reel/`, `/p/`) | `web-scrape` `formats.parse`, `parseParams: {type: "prebuilt", parser: "instagram-post"}` | `video_url`, caption, views, likes, comments, posted date |
    | TikTok video | same, parser `tiktok-video` | `video_url` (downloads without cookies), counts, music |
    | A creator's page | parser `instagram-profile` or `tiktok-feed`, then pick the post | their latest posts with counts |
    | A file the user has | skip this step | |
    
    ```bash
    python3 <skill>/reverse.py fetch "<video_url>" study
    ```
    Save the parser's caption and counts to `study/post.json`. The `video_url` expires after a few hours, so fetch
    right away.
    
    ### 2. Take it apart
    
    ```bash
    python3 <skill>/reverse.py analyze study/video.mp4 -o study
    ```
    About 20 seconds for a 30-second reel. It reads every frame and writes:
    - `STYLE.md`: rhythm (cuts, shot lengths, opening hold, transitions: hard cut, whip, flash, dip; camera moves:
      push-in, pull-out, pan; tempo, cuts on the beat, where the drop is and how the cutting speeds up after it,
      loudness, words per second), text on screen (how much, how big, how far down, caps, weight, colours, word-by-word
      builds), look (framing: full frame or a 16:9 / 4:3 / 2.39:1 band and where it sits; the grade: black point,
      contrast, saturation, warmth, shadow and highlight tint; palette, faces), the hook, a shot list with each shot's
      length, transition in, move and energy, and a text track. Add `--no-words` for a reel with no talking.
    - `shots.jpg` (one frame per shot), `timeline.png` (cuts, text, beats, loudness on one strip), `style.json`,
      `detail.json`, `frames.csv` (every frame's numbers).
    
    ### 3. Look, then write the read
    
    Open `shots.jpg`, `timeline.png` and a strip of the video (`ffmpeg -i study/video.mp4 -vf "fps=2,scale=144:-1,tile=11x5"
    -frames:v 1 study/strip.jpg`). The numbers can't tell a phone filming a laptop from a screen recording, or a meme from
    B-roll. You can. Fill in "The read" at the bottom of `STYLE.md`:
    - **Format:** what the video is, shot by shot (talking head, split screen, phone filming a screen, B-roll over voice).
    - **Hook:** what happens in the opening hold, on screen and said.
    - **What makes it feel like itself:** the three or four choices that carry it.
    - **To copy it on a new clip:** a recipe with the measured numbers.
    
    Treat the text readings as hints: OCR picks up words inside screenshots too. Check the caption numbers against the strip.
    
    ### 4. Edit the user's footage the same way
    
    Ask what they're working with, then write an edit plan from the read before you touch anything.
    
    **A montage (travel, cinematic, B-roll, music-driven).** They give you a folder of clips and a song.
    - Shot list: copy the reference's shot count and lengths, scaled to their song's tempo, so cuts land on their beat
      the way the reference's do (the measured share on the beat). Hold the opening as long as the reference does; if
      the cutting speeds up after the drop, find their song's drop and do the same.
    - Fill each slot with their clip that fits: wides where the reference has wides, people where it has people, the
      strongest shot on the drop. Pull the best moment of each clip, not its first second.
    - Framing: same as the reference (a 16:9 band in a 9:16 frame at the measured height, a 2.39:1 letterbox, or full
      frame). Never mix framings inside one reel.
    - Grade: match the numbers (black point, contrast, saturation, shadow and highlight tint, warmth) with the user's
      own colour tools or ffmpeg (`eq`, `curves`, `colorbalance`). Log or flat footage gets a normal conversion first.
    - Transitions and moves: the same kinds in the same places (whips where it whips, push-ins where it pushes in).
    - Text: their own words, in the reference's position, size and case.
    
    **A talking head or tutorial.** They give you a take.
    - Opening hold, then the measured cut rhythm as punch-ins or B-roll cuts, captions in the measured position, size,
      case, weight and colours, the same amount of text on screen, the same end card. For logos and screenshots the
      edit needs, use the `b-roll` skill.
    
    Then edit with whatever they use: their own Claude editing skill, Remotion, HyperFrames, ffmpeg, or export the plan
    as a cut list for CapCut, Premiere or Resolve. Show the plan first, then the render next to the reference.
    
    ## Rules
    
    - Copy the style, not the content. Never reuse the creator's footage, face, voice, words, music file, logo or
      watermark. Captions are the user's own words.
    - The download is for study. Don't repost it or put it in the user's edit.
    - Numbers come from the measurement. If something wasn't measured (the font's name, the music track), say so.
    - A measurement is one video. Say so before you call something "their style".
    
  • vision.swift 1.3 KB · in bundle

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.