davinci-resolve-video-editor

Files (27)

• SKILL.md
• openai.yaml · agents/
• manifest.json
• ai-human-footage-qc.md · references/
• direct-visual-analysis.md · references/
• editing-principles-from-guide.md · references/
• effects-inventory.md · references/
• external-audio-generation.md · references/
• music-led-editing.md · references/
• non-destructive-revisions.md · references/
• resolve-api-v21-notes.md · references/
• resolve-master-workflow.md · references/
• ui-click-map.json · references/
• video-composition-story-workflow.md · references/
• analyze_music_timing.py · scripts/
• apply_timeline_luts.lua · scripts/
• create_shot_audit_sheet.py · scripts/
• create_timeline.py · scripts/
• generate_elevenlabs_voice.py · scripts/
• generate_resolve_master_lua.py · scripts/
• generate_resolve_revision_lua.py · scripts/
• inventory_resolve_effects.py · scripts/
• package_skill.py · scripts/
• prepare_resolve_media_plan.py · scripts/
• qc_render.py · scripts/
• resolve_env.py · scripts/
• resolve_ui_click_map.py · scripts/

SKILL.md (first lines)

# DaVinci Resolve Video Editor

## Operating Rules

- Keep Resolve as the source of truth. External tools may analyze, transcode, generate, or mix assets; place final editable assets in a Resolve timeline before calling the work complete.
- Back up the project before bulk edits and duplicate the current timeline for revisions. Do not overwrite an approved version unless explicitly requested.
- Build story-driven edits from a brief, shot audit, and beat sheet. Do not let equal-duration automation replace editorial judgment.
- Check every Resolve API return value. Treat `False` and `nil` as real failures.
- Apply Resolve AI selectively. Never run Smart Reframe, stabilization, Voice Isolation, or subtitles across a timeline without a content-specific reason.
- Prefer prepared per-beat intermediates over flattening a complete edit into one MP4.
- Render from Resolve when possible, then run technical and visual QC on that render.
- Report music licensing and commercial-use uncertainty for ads and sponsored content.

## First Checks

1. Confirm Resolve is running and local scripting access is enabled.
2. Prefer the installed scripting docs over memory:
   - Windows: `%PROGRAMDATA%\Blackmagic Design\DaVinci Resolve\Support\Developer\Scripting\README.txt`
   - macOS: `/Library/Application Support/Blackmagic Design/DaVinci Resolve/Developer/Scripting/README.txt`
   - Linux: `/opt/resolve/Developer/Scripting/README.txt`
3. Use `scripts/resolve_env.py` for Python connections. Use `fuscript.exe -l lua` on Windows when Python ABI behavior is uncertain.
4. Probe exact methods with a small script when signatures or Studio-only availability matter.

## Reference Routing

Read only the references needed for the task:

- Ads, reels, trailers, cinematic or story-led edits: `references/video-composition-story-workflow.md`.
- Shot selection and direct frame understanding: `references/direct-visual-analysis.md`.
- Color, audio, captions, accessibility, and delivery craft: `references/editing-principles-from-guide.md`.
- Prepared media, final timelines, track layout, and QC: `references/resolve-master-workflow.md`.
- Music replacement, BPM analysis, beat-sync, and commercial tracks: `references/music-led-editing.md`.
- Duplicating timelines and replacing music/graphics safely: `references/non-destructive-revisions.md`.
- Exact Resolve 21 API notes and render pitfalls: `references/resolve-api-v21-notes.md`.
- External voice or generated music: `references/external-audio-generation.md`.
- Generated presenters, reference-to-video, avatars, facial artifacts, and lip sync: `references/ai-human-footage-qc.md`.
- OpenRouter visual analysis and cost/privacy controls: use the optional `openrouter-media` skill when installed.
- Installed effects/transitions and UI-only parameters: `references/effects-inventory.md` and `references/ui-click-map.json`.

## Core Workflow

1. Write a concise creative brief: viewer, promise, emotion, platform, aspect ratio, duration, CTA, and brand constraints.
2. Audit source media. Run `scripts/create_shot_audit_sheet.py` when best moments are unknown, then inspect the contact sheet directly.
3. Build a beat sheet with exact source ranges, narrative roles, speed decisions, graphic slots, AI actions, and audio cues.
4. Choose the audio driver before final timing: voice, music, natural sound, or hybrid.
5. Prepare Resolve-safe segments when originals have HEVC/timecode/rotation/trim instability or when exact short beats are required.
6. Build or revise the Resolve timeline with named tracks, markers, and editable stems.
7. Run a creative rough-cut critique before polishing effects or codecs.
8. For generated humans, judge audio and facial motion separately and define a product B-roll fallback before accepting the shot.
9. Apply selective AI, color correction, grade, graphics, sound design, and captions.
10. Save, render, and run QC. Fix editorial failures in the Resolve timeline, not only in the exported file.

## Prepared Master Workflow

Use a JSON edit plan with `project`, `timeline`, `width`, `height`, `fps`, `segments`, `overlays`, `audio`, and optional `markers`/`ai`.

Each video segment may use:

- `start`: source start in seconds.
- `duration`: output timeline duration in seconds.
- `speed`: playback multiplier; `2.0` uses twice as much source and outputs a 2x segment.
- `source_duration`: optional explicit source take duration.
- `video_filter`: optional FFmpeg filter fragment for controlled preprocessing.
- `timeline_start`, `track`, `role`, and `name`.

Prepare and build:

```powershell
python scripts/prepare_resolve_media_plan.py plan.json --output-dir work/resolve_ready
python scripts/generate_resolve_master_lua.py work/resolve_ready/resolve_media_manifest.json `
  --output-lua work/build_master.lua `
  --backup-dir work/backups `
  --ai-intellisearch `
  --smart-reframe-indices 4,5,6 `
  --stabilize-indices 4,5,6
& "C:\Program Files\Blackmagic Design\DaVinci Resolve\fuscript.exe" -l lua work/build_master.lua
```

Only pass item indices that visibly benefit. The generated builder does not create subtitles or enable Voice Isolation automatically.

## Non-Destructive Revisions

Use `scripts/generate_resolve_revision_lua.py` for music, graphic, caption, logo, or stem replacements on an existing timeline. The revision plan must name the exact source timeline, tracks to clear, replacement assets, track names, markers, backup directory, and optional render settings.

```powershell
python scripts/generate_resolve_revision_lua.py revision.json --output-lua work/revise.lua
& "C:\Program Files\Blackmagic Design\DaVinci Resolve\fuscript.exe" -l lua work/revise.lua
```

Duplicate first, clear only listed tracks, preserve unrelated tracks, import full source assets into the Media Pool when useful, and leave editable sources disabled beside the approved final mix.

## Music-Led Editing

- Analyze a supplied or generated track before changing picture timing:

```powershell
python scripts/analyze_music_timing.py track.mp3 --output-json work/music_timing.json
```

- Prefer a coherent 4/8/16-bar section with a build, drop, sustained energy, and clean CTA exit.
- Align major visual beats to strong musical events first: hook, reveal, DJ/person moment, speed ramp, payoff, CTA.
- Snap minor cuts to quarter- or half-beats only when the image supports the faster rhythm.
- Do not stretch a recognizable commercial song to force an unrelated edit grid. Revise cut timing or select a better source section.
- Keep music-only, sound-design, ambience, and final-mix assets on separate named tracks. Use the approved final mix for render parity and keep sources disabled.

## Resolve AI Policy

- `AnalyzeForIntellisearch`: use for source organization and search; safe to run broadly when useful.
- `SmartReframe`: use only after target aspect ratio is fixed and only on clips with meaningful subject movement/crop risk.
- `Stabilize`: use only on visibly shaky clips; reject warping or aggressive crops.
- `RemoveMotionBlur`: use only when motion blur hurts clarity.
- `VoiceIsolation`: use only on real dialogue/voice tracks, never on a music-led final mix.
- `CreateSubtitlesFromAudio`: use for dialogue accessibility. Remove test subtitle tracks before final render if graphic captions already exist.
- `GenerateSpeech`: use for requested narration or a clearly labeled guide voice, not as automatic decoration.

## Generated Human Footage

- Run dense frame QC across every visible speaking interval. A few representative frames cannot approve a synthetic close-up.
- Preserve native picture/audio sync while the mouth is visible. Do not retime them independently.

From ruota/open-sinapseed, MIT.

More from ruota/open-sinapseed