blitzreels-clipping — Claude Code skill: what it does, how to install
blitzreels-clipping drives a short clip end to end: source intake, transcription, range selection, framing, captions, QA and export.
MIT 125 installs ★ 5 updated 2026-10-07
npx skills add blitzreels/agent-skills --skill blitzreels-clipping -a claude-codeWhat blitzreels-clipping does
The skill keeps a clip moving through a fixed set of states, from intake and transcription to range selection, framing, captions, a quality pass, repair and the final export. A public link from YouTube, Instagram, TikTok, X, Facebook or Google Drive works as input, as does a direct video URL or an asset ID inside the workspace.
Calls go through the bundled MCP tool clips_create. Without it the agent can look up the current contract with blitzreels agent-context --command "clips create" --json or the /clips operations in the OpenAPI spec. Every clip is created with a caller-generated idempotency key, and the agent then follows next_action or polls with clips_get for batches.
Layout gets checked against the footage: the tutorial option suits flattened screen-share with a facecam, while interviews and podcasts take automatic, split or focus. Repair is limited to whatever the current state offers, and the low-level media, transcript, timeline and preview operations come into play only when managed state reports a block. Export costs money, so it waits for your approval and an export-ready state.
What it helps with
- cut vertical clips out of a long recording
- pick a moment when the choice is left to the model
- reframe screen-share footage with a facecam inset
- burn in captions and check them on a preview
- resume a clip that stopped on a blocking state
Example prompts for the agent
- Pull a few vertical clips from this YouTube link and show me the candidate ranges with their hooks.
- Take the interview from Google Drive, use the split layout and add captions.
- The clip is stuck — read
next_actionand repair it from the current state.
How to install blitzreels-clipping
1Skills CLI (Vercel)
npx skills add blitzreels/agent-skills --skill blitzreels-clipping -a claude-code2Manually: put the files in place
~/.claude/skills/blitzreels-clipping/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/blitzreels-clipping/
1Skills CLI (Vercel)
npx skills add blitzreels/agent-skills --skill blitzreels-clipping -a codex2Manually: put the files in place
.agents/skills/blitzreels-clipping/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add blitzreels/agent-skills --skill blitzreels-clipping -a cursor2Manually: put the files in place
.cursor/skills/blitzreels-clipping/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install blitzreels/agent-skills skills/blitzreels-clipping2Manually: put the files in place
.github/skills/blitzreels-clipping/SKILL.md1Skills CLI (Vercel)
npx skills add blitzreels/agent-skills --skill blitzreels-clipping -a gemini-cli2Platform CLI
gemini skills install https://github.com/blitzreels/agent-skills --path skills/blitzreels-clippingManually: put the files in place
.devin/skills/blitzreels-clipping/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add blitzreels/agent-skills --skill blitzreels-clipping -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about blitzreels-clipping
How to install blitzreels-clipping in Claude Code?
Run npx skills add blitzreels/agent-skills --skill blitzreels-clipping -a claude-code. The skill lands at ~/.claude/skills/blitzreels-clipping/SKILL.md.
What does blitzreels-clipping do?
It takes a long recording through intake, transcription, moment selection, framing, captions, a QA pass, repair and export. You get back clip and project IDs, the chosen range, the applied layout, the QA result and where the file was saved.
What does it need in order to run?
A source as a supported public video URL or a workspace asset ID, plus one of the surfaces: the clips_create MCP tool, blitzreels agent-context or the /clips OpenAPI operations. Export is paid and starts only after you approve it.
Source text
SKILL.md · MIT
--- name: blitzreels-clipping description: Create, select, reframe, repair, caption, or export short clips from long-form media, including supported YouTube, Instagram, TikTok, X, Facebook, Google Drive, and direct video URLs. --- # BlitzReels Clipping Use the managed clip **state machine**. It owns ingest, transcription, selection, layout, captions, QA, repair, and export sequencing. ## Steps 1. Resolve the source as a supported public video URL or workspace asset ID and resolve selection intent. Use a provided time range or suggestion; use automatic best selection only when choice is delegated. Complete when source and selection mode are explicit. 2. Choose the available surface. Prefer the bundled MCP `clips_create` tool; otherwise discover the current contract with `blitzreels agent-context --command "clips create" --json` or the OpenAPI `/clips` operations. Complete when required inputs, mutation effects, and state fields are known. 3. Create with a caller-generated idempotency key. Complete when the response contains a clip ID, project ID, state, and `next_action`. 4. For MCP batches, follow `batch.polling` with `clips_get`. For managed API clips, follow `next_action`: poll, reselect, repair, export, or stop. Complete each transition only when the next response advances or reaches a terminal state. 5. When the user retained selection choice, present available alternatives with title, hook, range, duration, and score; reselect the approved ID or range. Complete when the chosen selection is persisted. 6. Validate layout intent. Tutorial layout is for flattened screen-share plus facecam footage. Interview and podcast footage use automatic, split, or focus layouts. Complete when applied layout and content type agree. 7. Review QA previews and warnings; run only the repair action offered by current state. Complete when QA passes or the state reports a specific unresolved block. 8. Start a paid export only after user approval and an export-ready state. Poll to terminal and verify output duration, aspect ratio, captions, framing, and download location. ## Manual branch Use low-level project media, transcript, timeline, caption, and preview operations only when managed state reports a specific block requiring manual control. Return to the managed clip after the repair instead of rebuilding its state machine with low-level calls. ## Completion Return clip and project IDs, selected range, applied layout, QA result, warnings, export status, and download location. If blocked, return `next_action`, the exact blocking state, and the user choice or system state required. Completion requires a verified terminal output or an explicit managed-state blocker.
© blitzreels · MIT · blitzreels/agent-skills