0xsline/multi-clips-to-reels
Turn multiple product shots, event footage, travel clips, gameplay moments, UGC/product footage, B-roll, or mixed media into social-ready reels, highlights, recaps, or montage-style short videos from existing project media.
npx skills add https://github.com/0xsline/OpenChatCut --skill multi-clips-to-reels
Use this workflow when multiple raw clips or assets carry the output. The task is to select, sequence, and package the strongest footage into one or more reels, highlights, recaps, or short videos.
This is a OpenChatCut-native workflow. Use the current project, source assets, asset-frame inspection, AV/script context, and OpenChatCut editing tools. Use the current timeline when it already contains relevant cuts or for final verification; do not depend on timeline screenshots as the primary way to understand raw source clips. Do not depend on external download, transcription, ffmpeg, or auto-crop pipelines unless the user explicitly asks for an external source that is not already in the project.
open_media_reel: uploaded clips/photos and a loose goal.script_or_storyboard: supplied script, timestamps, shot list, scene notes, or exact copy.asset_pack_promo: product/event/place assets with logos, screenshots, QR codes, audio, or brand constraints.highlight_selection: many clips where the main work is selecting the strongest visual moments.<widget> after loading widget-forms. Use text fields for open-ended fields like premise, audience, product/context, or goals; use single/multi choice fields for bounded choices like platform, count, duration, captions, or music.script_or_storyboard, preserve the user's scene order, copy, timestamps, and claims while mapping each source asset to the requested shot. For asset_pack_promo, lock the product/place/event identity and reserve fixed-role assets for brand, proof, or CTA moments. For open_media_reel and highlight_selection, select and sequence the strongest moments instead of averaging every asset.read_script for the speech/script overview, view_asset_frames for specific source frames and frame-block analysis to select high points or verify what happens on screen. Select for strength, variety, continuity, and fit to the requested platform.10. If the user gave enough constraints and asked to create directly, proceed after stating the plan. If the material is varied or the requested count is high, create or preview the first strongest reel before batching the rest.
11. Edit around a viewer-facing arc: hook, context, escalation or proof, payoff. For a pure highlight reel, the payoff can be the strongest final moment or a satisfying recap beat.
12. Package for the target platform: aspect ratio/crop, title text, styled captions, music/beat sync, light motion graphics, transitions, speed ramps, or zooms only when they improve rhythm or clarity.
13. QA before reporting done: strongest shot first, clear sequence purpose, distinct outputs, no unsupported claims, platform fit, requested count/duration, timeline names, and export readiness.
When presenting a plan, use this compact shape:
open_media_reel, script_or_storyboard, asset_pack_promo, or highlight_selectionread_script, source frames, or visual-analysis notesWhen creating clips, report timeline names, durations, packaging applied, assumptions, and what to review first.
Take 0xsline/multi-clips-to-reels from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.