Footage Cutlist logo

Footage Cutlist

OrganizationPopular
gooseworks-ai
footage-cutlist

Watch a brand's own product footage (screen recording, product film), pick the moment that proves each line with the user, and render those picks as a product layer — free, local. survey.py turns footage into timestamped contact sheets + scene cuts + motion so the agent can actually look at it; the agent writes a cut list (beat → source window + framing); preview.py draws it as a review sheet the user corrects round by round; cut.py renders the approved list into a silent 1080x1920 layer with the creator's area left as a plate. Also frames footage as a filmed screen (keystone, bezel, handheld drift) with dissolves between beats, and takes still screenshots as sources. Use for any format that shows real product footage beside, between or instead of a creator (split-screen, screen inserts, walkthroughs).

Overview

Publishergooseworks-ai
Repositorygoose-skills
Skill namefootage-cutlist
Stars
1.2K
Forks
216
Bundled files
9
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 9 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by gooseworks-ai on GitHub. Read the source before you install it.

Installation

Install the Footage Cutlist AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/gooseworks-ai/goose-skills/tree/main/skills/ads/capabilities/footage-cutlist
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git /tmp/goose-skills
mkdir -p .claude/skills
cp -r /tmp/goose-skills/skills/ads/capabilities/footage-cutlist .claude/skills/footage-cutlist
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Footage Cutlist in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Footage Cutlist on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Footage Cutlist is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

footage-cutlist

Picking which moment of a customer's footage plays under which line is a judgement, not a formula. A position map ("beat 3 is 40% through the reel, so take the footage 40% through") was measured up to 5.7s off a person's picks on a reference build. So this capability does the free, mechanical parts and leaves the decision to the agent and the user:

StepScriptWho decides
Look at the footagesurvey.pynobody; it just shows it
Choose a window per linethe agent writes cutlist.jsonagent, then the user
Show the choicespreview.pythe user corrects them
Render the approved choicescut.pynobody

All free. ffmpeg + Pillow + numpy only.

Run

bash
python survey.py --video footage.mp4 --out work/survey            # whole clip, ~1 frame/s
python survey.py --video footage.mp4 --out work/s-12 --from 12 --to 18 --every 0.25 --frames
python preview.py --cutlist work/cutlist.json --out work/review.png
python cut.py --cutlist work/cutlist.json --out work/layer.mp4 [--draft]

survey.json lists cuts (scene changes), motion (change per second) and still (runs of 1.5s+ with nothing moving: a dead screen reads as a frozen video). Read the sheets; open a single frame-*.png (from --frames) when you need to read small UI text.

The cut list

json
{
  "size": [1080, 1920], "fps": 30, "seam": 768, "creator_side": "bottom", "bg": "auto",
  "sources": {"demo": "footage/demo.mp4"},
  "beats": [
    {"id": "b1", "start": 0.0, "end": 3.1, "state": "creator", "vo": "..."},
    {"id": "b2", "start": 3.1, "end": 7.4, "state": "split", "vo": "...",
     "source": "demo", "in": 12.0, "fit": "width", "why": "the brand kit fills in at 13.4s"}
  ]
}
  • state: creator (creator full frame), split (footage in the product zone, creator in the other), product (footage full frame).
  • in is where the window starts in the source; out defaults to in + slot (1.0x). A window may play between 0.5x and 2x; it is never looped or frozen to fill a slot.
  • fit: width (whole frame, letterboxed; the default), cover (fill + crop around focus), crop (a source box [x0,y0,x1,y1] in fractions, then fit by width).
  • bg: auto samples the footage's own corner colour so the letterbox and the footage read as one surface; blur; or #rrggbb.
  • look: "screen": frame the footage as a screen filmed at close range (thin bezel, dark room, faint moire, grain, slow handheld drift). crop picks the source region, screen: {rot, keystone, fill, fit, drift} the geometry, mask boxes are blurred in the source (an email, a customer name). Inserts over a creator: keystone ~0.007, rot within ±1°. Walkthroughs: keystone ~0.024, rot -1.5..0, fill ~0.80. Never bigger angles and never alternate them between beats (read as a wonky camera).
  • transition: {"dissolve_frames": 7} (top level): cross-dissolve every beat into the next. A hard cut between two screens reads as an edit; 6-7 frames reads as the camera moving.
  • A source can be a still image (png/jpg/webp): it holds for its slot. Give it look: "screen" so the drift keeps it alive.
  • why: one line on what the window shows. It is printed on the review sheet so the user can see the reasoning, and it makes the agent say what it saw.

Beats must tile the timeline from 0 with no gaps. cut.py refuses a list that does not.

Rules that were learned the hard way

  1. Watch the whole thing before choosing anything. Look at every sheet of the whole-clip survey first. The moment that proves a line is often not where the recording's order suggests.
  2. Never commit a window from a 1fps glance. Re-survey that range at --every 0.25 and look at every frame. A click, a page load or a half-typed field lives between the samples, and it is exactly what a user then points out ("you didn't look at the video properly").
  3. The line must be true of the footage while it is said. If a line says "it pulls your brand colours", the colours must be on screen during that line, not a second later. Name what is visible in why.
  4. Never crop footage that has copy in it. Cropping a UI panel into a narrower zone slices through words. Default to fit: width; use crop only to isolate a small subject, and check the review sheet for cut-off text.
  5. Avoid dead screens. A window inside a still run reads as the video having stopped. Start it where something moves, or shorten it.
  6. A screen region should be roughly the box's shape. A 9:16 box is filled by a source region of ~0.6-0.8 aspect: crop fewer COLUMNS at full height. A wide, short crop floats in black. For a complete panel with copy, use fit: width and let the room fill.
  7. Watch for a third party inside the footage. A customer logo row or another company's name in the recording ends up in the ad. Crop above it or mask it.
  8. Don't reuse footage. cut.py warns when two beats overlap in the same source: it reads as a loop.
  9. After the takes exist, re-check. Line timing moves when the real voice is aligned (align_beats.py). Re-run preview.py + cut.py on the aligned list and look again.

Going back and forth with the user

Expect several rounds. Each round:

  1. Show review.png (and a --draft layer if they want to see motion).
  2. The user names beats: "b4 is wrong, use the part where the report loads."
  3. Re-survey just that stretch densely, find the moment, and change only that beat's window. Say what you changed and why.
  4. Re-render the review sheet and show it again.

Picking is free, so take as many rounds as the user needs. Never spend on the creator until the user has approved the cut list.

Product-photo motion and caption review

A real product photo can use look: "photo". This is a dedicated contain/pan/zoom treatment without a screen bezel. photo accepts start/end scale (0.85–1.0), start/end pan pairs (-1–1), a normalized content box, and normalized protected source rectangles. An optional crop must contain every protected product/text rectangle. The selected region remains visible throughout motion. Use photo.box to reserve space above/below the seam for a qualification. Review first/middle/last frames; preview and render share the photo framing function. Existing plain stills and screen looks remain supported.

Before showing the cutlist, generate a footprint with caption-burn's bundled footprint.py, using the final style, anchor and font. Pass that JSON to preview's caption-footprint option. The amber band is the union of the actual rendered caption groups for that beat. Rebuild it after copy/timing/style changes. If it covers qualifying text, adjust photo.box, crop or layout, then inspect the final captioned video. Do not reduce or hide the qualification to make the claim fit.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Footage Cutlist AI skill do?

Watch a brand's own product footage (screen recording, product film), pick the moment that proves each line with the user, and render those picks as a product layer — free, local. survey.py turns footage into timestamped contact sheets + scene cuts + motion so the agent can actually look at it; the agent writes a cut list (beat → source window + framing); preview.py draws it as a review sheet the user corrects round by round; cut.py renders the approved list into a silent 1080x1920 layer with the creator's area left as a plate. Also frames footage as a filmed screen (keystone, bezel, handhe...

Why use Footage Cutlist on TypingMind?

Because you install it once and use it with any model. Footage Cutlist is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Footage Cutlist in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/gooseworks-ai/goose-skills/tree/main/skills/ads/capabilities/footage-cutlist. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Footage Cutlist?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Footage Cutlist?

As many as you like. As long as a model supports skills, you can use Footage Cutlist with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Footage Cutlist AI skill free?

Yes. It is published on GitHub by gooseworks-ai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇