appariciojunior/video-editor-skills

rough-cut

Editorial rules for choosing what to keep in talking-head footage (retakes, false starts, spoken notes to the editor, fillers) and the keep-list / moments formats that a planner script turns into frame-exact cuts.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/appariciojunior/video-editor-skills --skill rough-cut

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

Rough cut: what stays

You decide what stays, by word index. A planner script decides where each cut lands (pads, waveform checks, pause shortening, frame snapping). Never do its job by hand.

The brief creators give: remove retakes and silences, keep it feeling like a natural vlog. Not a jump cut every second.

Read first

The manifest, then every clip's word list in order. Each token: {i, text, start, end, type} with type word or audio_event ("(laughs)", "[lighter click]"). Read it as a story before deciding anything.

Rules

  1. Retakes: keep the best complete take, usually the last. Never keep a take that trails off. Cut the restart cue with it ("let me do that again", a swear at themselves).
  2. False starts: cut an abandoned sentence plus its restart cue.
  3. Spoken notes to the editor ("editor, roll the video here", "this slide is a video"): cut them and write each as a note moment → becomes a pink marker on the join where it was.
  4. Fillers stay. It's a vlog. Only cut a filler that is clearly dead air on its own. Stumbles inside a word stay (cutting them makes a visible jump).
  5. Keep their voice: asides, jokes, a laugh, a deliberate pause before a point.
  6. Pauses are not your job. Give whole thoughts as one range; the planner shortens long pauses.
  7. Keep recorded order unless asked.
  8. Unsure? Keep it and flag it. A wrong cut is invisible to the creator; a flagged keep is a 5-second decision. Typical flags: near-identical lines in a row (deliberate repetition or retake?), self-corrections, a joke about "starting this three times".

keep.json

json
{
  "segments": [
    {"clip": "C0001", "from": 12, "to": 57, "why": "opening, second take"},
    {"clip": "C0002", "broll": true, "in": 0.0, "out": 4.0, "why": "camera goes into the bag"}
  ],
  "flags": [{"clip": "C0001", "at": 141, "note": "kept a stumble, check it"}],
  "summary": "3-6 lines in plain words"
}

from/to are inclusive word indices. B-roll segments are by seconds (see broll). Optional per range: lead_in / tail seconds of room (see vlog-pacing).

moments.json

json
{"moments": [
  {"type": "note", "clip": "C0001", "from": 1964, "to": 1994, "label": "VIDEO: product demo", "note": "Roll the demo here. They said: '…'"},
  {"type": "punch", "clip": "C0001", "from": 812, "to": 818, "label": "the line that lands"}
]}
  • note: covers the cut words; the marker goes on the join.
  • punch: a real punchline (conclusion, payoff, strong opinion), about one every 2–3 minutes. The picture pushes in to 115% for that line only, then goes back.

After planning

Read the review file once: struck-through text must be only what you meant to cut. Report: raw vs cut length, pieces, every retake removed (timestamp + gloss), every note, every flag.

Revisions

Creators speak in timeline times ("cut 02:14 to 02:20"). Map to word indices with the review file, edit the keep-list, re-plan, rebuild as a new version, and report only what changed.

dallo stesso repository

Altri Skills

Tutti gli Skills
appariciojunior
Community

captions

Clean, readable burned-in style subtitles from the verbatim transcript - stutters and fillers removed, spoken slang written correctly, one short line at a time, names checked, every line read by Claude before import into DaVinci Resolve. Use for "subtitles", "captions", "legendas", or when the creator reports wrong words in the captions.

Installazioni / 1h
1
GitHub Stars
435
Aggiornato
23 ott
appariciojunior
Community

motion-overlays

Brand motion graphics for creator videos - a Remotion component kit (key phrases, lists, lower thirds, journeys, big words…) timed to the creator's words from a beats sheet, rendered as transparent ProRes and placed on V2+ in DaVinci Resolve, with face-safe and caption-safe layouts. Use for "overlays", "motion graphics", "make it interesting", "graphics", or when overlays cover the face or fight the captions.

Installazioni / 1h
1
GitHub Stars
435
Aggiornato
23 ott
appariciojunior
Community

resolve-scripting

Practical DaVinci Resolve Studio scripting knowledge for building edits from code - timelines from a template, frame-exact appends, zoom, grades, custom frame sizes, subtitles, renders, and the traps that silently fail or crash Resolve 21. Use when writing or debugging any script that talks to Resolve.

Installazioni / 1h
1
GitHub Stars
435
Aggiornato
23 ott
appariciojunior
Community

video-editor-setup

Sets up an AI first-pass video editing workspace for DaVinci Resolve Studio with Claude Code - folders, tools, API keys handled safely, the Resolve template, and which small scripts to build first. Use for "set up my video editor", "start the video editing system", or before the first /edit-video when no workspace exists yet.

Installazioni / 1h
1
GitHub Stars
435
Aggiornato
23 ott