davinci-export
/davinci-export
Eksportuje z DaVinci Resolve gotowe klipy i montaże, ponownie renderuje poprawki i sprawdza pliki dostawcze oraz napisy.
- Autor
- amartinez1558 ↗
- Repozytorium
- davinci-workflow-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 09.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 09.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Eksportuje z DaVinci Resolve gotowe klipy i montaże, ponownie renderuje poprawki i sprawdza pliki dostawcze oraz napisy.
Oryginalny opis (EN)
Use when exporting smaller graded clips or a finished timeline from DaVinci Resolve, re-exporting manual revisions, selecting render jobs, and checking encoded delivery files and captions.
Jak działa
- Establish the delivery contract
- Preserve the current edit
- Stage, check, then publish
Podgląd SKILL.md
--- name: davinci-export description: Use when exporting smaller graded clips or a finished timeline from DaVinci Resolve, re-exporting manual revisions, selecting render jobs, and checking encoded delivery files and captions. metadata: version: '0.1.4' --- # Export and delivery Make the requested deliverable from the current approved timeline, verify it, then publish it. Consult [workflow contract](../../docs/workflow-contract.md) for broader coordination when available; the safeguards below also apply to standalone use. ## Establish the delivery contract - Distinguish separate smaller clips from a single edited film. For already graded source clips, preserve their grade, source frame rate, audio, and intended clip boundaries unless the user requests a change. Do not impose a story timeline's rate on this batch. - A film timeline can have a separately confirmed rate, such as exact 24 fps. Check the actual timeline and requested output; distinguish fractional rates from integer rates and avoid changing the timeline rate as an export shortcut. - For a short follow-up such as “export,” carry forward the established delivery contract and later corrections, inspect the latest live edit, and proceed. Ask only for materially missing choices; do not force a technical questionnaire on a nontechnical editor. - Establish resolution, aspect ratio, codec/container, size/quality goal, output destination, version name, and caption delivery from the brief or approved precedent. There is no universal bitrate, GOP, frame-rate, audio, or render-mode recipe. - Make burned-in versus separate captions explicit. An SRT beside a clean video does not satisfy a requested captioned viewing copy. A filename containing `captioned` is not evidence that captions are visible. ## Preserve the current edit 1. Inspect the live project and active timeline before any export. Save a checkpoint/project backup and snapshot current sources, in/out points, transforms, fades, enabled states, track structure, audio offsets/mix, subtitles, and graphics. Use this live state when the user has made manual changes; do not rebuild from a stale edit plan. 2. Inspect the render queue and current render configuration. Set only the needed settings, then read them back through the available API and native Deliver UI where necessary: timeline/range, single versus individual clips, destination, naming, rate, dimensions, codec, audio, captions, proxy/optimized media, and render-cache use. Verify render-mode enumerations against the installed API and inspect the queued job: single-clip intent must produce one expected filename and full timeline range. Do not copy an old integer or assume a job-list readback uses the setter's numeric type. Check early output for unintended numbered individual files; stop only the owned job and isolate partial results before correcting it. 3. Verify actual linked media and any offline sources. Disabling “use proxy media” does not make a timeline of manually imported working files an all-original conform. Report the actual source mix. 4. Add and record only the intended job IDs, and start those jobs explicitly using the installed API's supported form or native UI. Do not clear the queue or render unrelated jobs. If a call times out, inspect job status and existing output before retrying to avoid duplicate work. ## Stage, check, then publish - Use a visible staging destination such as `staging/`; do not create dot-prefixed hidden staging folders. Prefer staging outside Dropbox sync when practical to avoid uploading temporary renders. Preserve an existing delivered version and its companions before replacement. Check storage headroom for intermediates and backup files; never delete source originals to make an export fit. - Verify job success and nonempty output, then probe dimensions, frame rate, frame count/duration, audio streams/channels, and expected filenames/count for clip batches. Compare against source/timeline expectations, including intentional retiming. - Recheck newly added or slipped source ranges for color interpretation, action/motion and synchronized audio even after an earlier finishing milestone. A prior version’s QC does not cover new frames; preserve the user’s edits and report issues outside the requested export scope. - Decode the full deliverable for technical errors when feasible. Inspect decoded frames at intro/outro fades, graphics, changed shots, transitions, and representative caption intervals. Check that burned captions actually appear, remain readable, and clear lower thirds; native subtitle positioning can differ in the rendered output. - Validate intentional black intervals against the brief instead of treating every black frame as a coverage failure. For a music-only lead-in, verify its exact duration, music presence, subsequent picture fade and narration/caption onset. Confirm requested caption styling in the final encode as well as the native settings. - If an authorized external caption burn or final encode is used, reuse the current project's proven compositor/settings when suitable, keeping content and version paths separate from reusable logic. Verify the final result against the native render, preserve cue timing, and check intentionally omitted title-duplicate cues. Retain editable captions and a sidecar when requested. - Measure the actual final encoded audio against the requested true-peak ceiling; record loudness separately. Check representative listening and lip sync, and state when full human review was not performed. - Compare native and encoded pictures with the same source/proxy preference, grade and frame; separate body and caption regions when only the final copy has burned captions. Match external cues against the live track and native sidecar where available, accounting for timeline start timecode. - Compare the live timeline with the pre-export snapshot to catch accidental changes during rendering. Save the delivered milestone and a short QC record tied to the exact final file, optionally including a checksum for replacement/sync verification. - Publish the checked file and matching companions only after QC passes. For a cloud-backed destination, verify the final local file and the provider's sync/upload state when available; file existence alone proves neither remote availability nor successful upload. Report unverified cloud state honestly. After QC, move the deliverable and required companions into `output/` (or the agreed final destination) and verify them at their final paths. If publication requires copying, verify the destination before deleting the staged copies. As part of delivery, remove this task’s unneeded generated staging assets and diagnostics, then remove empty staging folders; report any retained files and why. Keep originals, backups, proxies and intermediates still linked by the project. Do not delete a folder wholesale merely because it is named staging, and do not clean unrelated or pre-existing files without authorization. Previous delivered output versions are separate from temporary staging. Ask whether the user wants to clean them up, naming the candidate versions and their sizes; keep them until the user approves the specific cleanup. Do not treat a new export as permission to delete older delivered versions. Report the final path, version, format, size, caption mode, checks performed, and remaining placeholders or review limits. Do not describe decoding or sampled frames as a full editorial, listening, or calibrated-color approval.
Wersje
W bazie nie ma innych skilli o nazwie davinci-export.
Migawka bazy z 13.11.2026 · wersja paczki 8d4d12c3afab (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100davinci-edit
Składa i poprawia dokumenty, relacje z wydarzeń, promo i montaże muzyczne w DaVinci Resolve: tempo, dobór ujęć, dialogi i napisy. - 95auto-editor-export
Eksportuje montaż z auto-editor do Premiere, DaVinci Resolve, Final Cut Pro lub Kdenlive jako projekt, osobne klipy i pliki osi czasu. - 100davinci-media
Importuje, porządkuje, rozpoznaje, tworzy proxy i ponownie łączy materiał w DaVinci Resolve, z zapisami postępu projektu i uwzględnieniem miejsca na dysku. - 90resolve-delivery
Przygotowuje renderowanie i kontroluje gotowe pliki w DaVinci Resolve względem specyfikacji: wideo, głośność i kompletność. - 98davinci-resolve
Pomaga montować w DaVinci Resolve: ustawienia projektu, osi czasu, korekcję kolorów, Magic Mask, napisy i eksport pod media społecznościowe. - 90davinci-resolve
Obsługuje DaVinci Resolve przez MCP: montaż, color grading, Fusion, dźwięk, renderowanie i pliki projektów offline.