references/editing

Determines pacing, cut points, transitions, and beat-sync rules for video assembly.

38|4|Updated Jul 29, 2026
One-click install
npx skills add https://github.com/6174/recut --skill references-editing-6174
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: references/editing
Source: https://github.com/6174/recut/tree/main/service/skills/recut-director/references/editing
Command: npx skills add https://github.com/6174/recut --skill references-editing-6174

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires librosa, scipy, numpy, and includes references (resource) and assets (resource) components.

What problem does it solve? Deciding how to cut footage together—how fast to cut, where to place each cut, which transition to use, and how to align cuts to music—is the core judgment problem of video editing, and doing it without standards produces slideshow-like, metronomic results. ## Core Features & Use Cases - Pacing and Shot-Count Planning: Derives shot counts from target durations using cutting registers (ASL tables), anchor/shortest-shot distribution, and median-below-mean checks. - Cut Motivation and Transition Selection: Enforces motivated cuts (action, look, sound, idea, emptiness, impact) and a transition table covering hard cuts, match cuts, dissolves, whips, J/L cuts, cutaways, and empty-frame bridges. - Music Beat-Sync Discipline: Fits a beat grid from the BGM with librosa, pins cuts to integer beats, and requires a post-render verification loop with a 3-frame error threshold. - Use Case: When assembling a 30-second vertical short from AI-generated clips, use this Skill to set the segment pacing, choose transitions that repair continuity gaps, and lock every cut to the music's beat grid. ## Quick Start Use the editing skill to plan the cut points, pacing, and transitions for my 30-second vertical video with a strong-beat soundtrack.

Frequently Asked Questions about references/editing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide where to place cuts in a video edit?▼

Place cuts based on motivation: cut on action, on a look, on sound, on an idea, on emptiness, or on impact. Every cut must advance information, shift attention, hand off motion, reveal a reaction, or serve emotion; unmotivated cuts read as decorative and should be removed.

How to sync video cuts to music beats?▼

Fit a beat grid by running librosa beat tracking on the BGM and least-squares fitting the beat sequence to get beat length and phase. Pin all cuts to integer beats, then re-measure the rendered audio and verify every cut lands within 3 frames of its designed beat.

What is a good average shot length for short vertical videos?▼

Feed and vertical content typically uses a 0.7–2.0 second average shot length, with hooks allowing 0.2–0.5 second punctuation cuts. Information segments should return to 3–6 or 5–12 seconds so ideas have time to land, and the median shot length should sit below the mean.

When should I use a dissolve instead of a hard cut?▼

Use a dissolve only as an honest repair for continuity gaps that cannot be fixed, such as mismatched light levels or shifted textures. Hard cuts are the default; dissolves consume running time and imply time passage, so never dissolve between two shots continuous in time.

Why does my edit feel like a slideshow?▼

The slideshow feeling comes from the cut, not the footage. Enforce the eight anti-slideshow rules: overlap motion across cuts, break shot size or angle by at least two rungs, keep one continuous audio bed, vary shot lengths, and never open two consecutive shots on static frames.

How much extra footage should AI-generated clips have for editing?▼

Generate 1.5 seconds longer than the needed cut for simple shots and 2.5 seconds for character performance or dialogue. Discard the first 8 frames and last 12 frames of every generated clip before evaluating content, since heads ramp in and tails drift.