Communitygithub.com

DomCamillo2/VideoEditting

Cut photos or video on audible musical beats, downbeats and phrase changes, or diagnose an edit that feels off beat. Use for music-led timing and transitions; do not equate waveform peaks or automatic markers with verified musical accents.

VideoEditting란 무엇인가요?

VideoEditting is a Claude Code agent skill that cut photos or video on audible musical beats, downbeats and phrase changes, or diagnose an edit that feels off beat. Use for music-led timing and transitions; do not equate waveform peaks or automatic markers with verified musical accents.

지원 대상~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/DomCamillo2/VideoEditting/tree/HEAD/.agents/skills/video-beatcut

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

Cut on the intended beat

Inputs: actual audio file, chosen excerpt(s), target fps, current edit and desired energy. If audio cannot be heard with available tools, analyze provisionally and explicitly leave listening validation open.

  1. Identify intro, verse, chorus/drop, breakdown and ending. Estimate tempo and phase, then check strong kicks/snares and downbeats near the beginning, middle and end. Watch half/double tempo, pickup notes, syncopation and changing tempo. An onset detector finds transients, not necessarily beats or bar starts.
  2. Build a selected marker list, not a cut on every peak. Record source seconds, timeline seconds, accent type, confidence and whether actually listened to. Favor phrase changes for chapter/song changes and the strongest images for musical peaks.
  3. Map trimmed audio correctly. At normal speed: timeline_seconds = audio_start + source_seconds - source_in. With constant playback rate r, divide the source offset by r. For ramps, use the actual time mapping, not a single BPM. Include source trims, repeats and song crossfades.
  4. Quantize each absolute boundary once: for nonnegative times, frame = floor(seconds * fps + 0.5). Preserve rational rates such as 30000/1001. Use exact rational arithmetic through rounding when possible, including half-frame ties. Shot length is the next boundary minus the current boundary; do not repeatedly round incremental beat lengths. Store fps and integer frame boundaries.
  5. Vary holds by story and energy: several beats for atmosphere, shorter phrases for action. Prefer a readable moment over mechanically cutting on every beat. Treat clips below 0.5 seconds as deliberate exceptions to explain, not a default montage strategy.
  6. Set transitions so their perceptual impact lands on the intended accent. A cut, flash peak, mask reveal or landing may have different anchor frames. Overlapping transitions shorten total duration; recompute downstream boundaries. An overlay does not inherently shorten the base track.
  7. Preview the actual encoded segment with music, including a few seconds before and after key cuts. Listen for phase errors, song edits, speed ramps and effects obscuring the accent. Check again at the end of a long section to catch drift. Do not call numerical alignment an independent listening test.

Evidence to deliver

Save a beat table with song_id, source_seconds, timeline_seconds, target_frame, accent_type, confidence, listening_status; a cut table with cut_frame, matched_marker, delta_ms, intentional_offset_reason; and representative review ranges.

Separate frame alignment (nearest frame; theoretical quantization error up to half a frame) from musical correctness (the chosen sound is the intended accent) and editorial quality (the shot holds long enough). A marker-perfect cut can still feel wrong. Finish songs with a phrase ending, intentional tail/fade or suitable authentic sound.

With a VideoEditting checkout, tools/beat_candidates.py proposes local spectral onsets and tempo hypotheses with source-to-timeline mapping. Treat these as unverified candidates, select audible accents, then use tools/editing.py beat-report on the chosen markers. The detector never certifies downbeats. The checkout is optional.

Individual skills in this repo

This repo contains 8 individual skills — each has its own dedicated page.

DomCamillo2/VideoEditting

Mix music, dialogue, authentic location sound and comedic sound effects for an edit. Use for ducking, song transitions, J/L cuts, intelligibility and clean endings; not as a substitute for beat detection or actual listening.

DomCamillo2/VideoEditting

Establish a film or reel brief, including tone, humor, travel type, route and relevant vehicle details. Use when these choices are missing or the user changes direction; skip for a small revision with an established brief.

DomCamillo2/VideoEditting

Reconstruct capture order, trip chapters and road/ferry map segments from photo/video metadata and visible evidence. Use when travel chronology or route labels matter; do not invent exact dates or transport links from filenames alone.

DomCamillo2/VideoEditting

Add playful video gags such as person cutouts, spins, loading effects, face-zoom transitions or tracked scooter flames. Use when humor is requested in the current brief; do not add unsolicited meme edits to a serious film.

DomCamillo2/VideoEditting

Prepare a reviewable preview, verify the final encoded video and hand off a versioned editing project. Use before export or when diagnosing black borders, crop errors, missing assets, drift, color or audio problems; do not claim creative QA from a successful build alone.

DomCamillo2/VideoEditting

Fit portrait photos or videos into landscape edits, or reframe mixed aspect ratios with a blurred copy of the same media. Use to prevent black borders and cropped faces or bodies; not for privacy anonymization or sharpening a blurry subject.

DomCamillo2/VideoEditting

Cull and rank photos or video excerpts, remove repetitive selections, and compare blurry versus sharp takes. Use for bursts, near-duplicates, contact sheets and best-moment selection; never delete source media or judge focus only from a blurred background.

DomCamillo2/VideoEditting

Onboard a new user to the VideoEditting toolkit by choosing all or selected editing skills, assessing useful MCP integrations and setting up approved tools before the film brief. Use for first-time adoption or setup changes, not every editing revision or repository maintenance task.

관련 스킬