appariciojunior/video-editor-skills

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.

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/appariciojunior/video-editor-skills --skill captions

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

Captions

Goal: people watching on mute can follow; the captions are just there, never in the way.

Source

The verbatim transcript mapped onto the current timeline (follow the creator's trims), not Resolve's own auto-captions (a second, less accurate transcription). Drop words on B-roll (radio lyrics, background talk).

Clean, not verbatim

Captions show what they mean, written correctly:

  1. Stutters: "pro-product" → "product", "da-da," → "da,".
  2. Cut-off words: "es--", "A--" → gone.
  3. Filler sounds: drawn-out "uuum", "hããã", "ééé" → gone. Careful with real words that look like fillers ("um" = "a" in Portuguese, "é" = "is").
  4. Self-corrections: "get a, an appointment" → "get an appointment".
  5. Spoken short forms → correct written forms, if the creator asks. Brazilian Portuguese example: cê/cês → você/vocês, tá → está, tô → estou, tava → estava, tamo → estamos, vamo → vamos, pra/pro → para/para o, né → não é, "o que que" → "o que", "por que que" → "por que", "tu consegue" → "você consegue"; "tão" → "estão" only before a verb in -ndo ("tão bonito" stays). Keep expressions and swear words (fix grammar, not voice). Keep capital letters at sentence starts when you shorten.
  6. Names and spellings checked on the web (transcripts garble product names), and the creator's own name exactly as they write it.
  7. Don't reveal what the creator wants kept secret (a place, a company) even if they say it.

Keep two lists: global rules (word map + phrases) in config, per-video fixes in caption_fixes.json. Apply phrase fixes after the word map.

Lines

  • One line, max 42 characters; a sentence's last word may stretch it to ~50 rather than sit alone.
  • New cue at a pause ≥ 0.6 s, at sentence ends (if the line is already substantial), or after 3.2 s.
  • Min 0.9 s on screen, end 0.25 s after the last word, never overlapping the next.
  • A lone small word after a pause ("que", "vai", "not") joins the next line. Single-word cues are fine only when they stand alone ("Calm down.", "Bye.").
  • First cue starts at 00:00:00,000 (Resolve's import shifts everything relative to the first cue).
  • Write a new file name per version (captions_v3.srt).

Read every cue

Print every line and actually read it before handing it over. Grep for leftover short forms, double punctuation (",,"), lowercase after a full stop, words lost by your own filters. Fix rules, regenerate, read again.

Into Resolve

The creator imports with File > Import > Subtitle (the API places subtitles after the timeline end; a workaround crashed Resolve). Delete the old subtitle clips but keep the track so its style stays.

Style

Record the creator's style once (font, size, position, shadow) from their timeline and save it in config as the house style, e.g. a light sans at size 68, centred ~11% up from the bottom, soft drop shadow. Overlays must stay out of that band (see motion-overlays).

del mismo repositorio

Más Skills

Todos los Skills
appariciojunior
Comunidad

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.

Instalaciones / 1h
1
GitHub Stars
435
Actualizado
23 oct
appariciojunior
Comunidad

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.

Instalaciones / 1h
1
GitHub Stars
435
Actualizado
23 oct
appariciojunior
Comunidad

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. Use when deciding a cut, revising one from feedback, or writing keep.json.

Instalaciones / 1h
1
GitHub Stars
435
Actualizado
23 oct
appariciojunior
Comunidad

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.

Instalaciones / 1h
1
GitHub Stars
435
Actualizado
23 oct