# Davinci Resolve Editor

> Safe DaVinci Resolve Studio editing through davinci-resolve-mcp or the official Resolve Python API. Use when Codex must inspect Resolve state, create or revise projects and timelines, import approved media, place source ranges, apply authorized LUTs or effects, prepare rendering, and verify gaps, tracks, source bounds, frame origin, and actual write success.

- **Type:** Skill
- **Install:** `agentstack add skill-liuluhaixiu-davinci-autoedit-agent-davinci-resolve-editor`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [liuluhaixiu](https://agentstack.voostack.com/s/liuluhaixiu)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [liuluhaixiu](https://github.com/liuluhaixiu)
- **Source:** https://github.com/liuluhaixiu/DaVinci-AutoEdit-Agent/tree/main/skills/davinci-resolve-editor

## Install

```sh
agentstack add skill-liuluhaixiu-davinci-autoedit-agent-davinci-resolve-editor
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# DaVinci Resolve Editor

Operate only from an approved blueprint. Read `references/mcp-operations.md` for
the tool map and `references/verification.md` before delivery.

For deeper operations, load only the relevant bundled reference:

- `references/compound-tool-reference.md`
- `references/prompt-patterns.md`
- `references/page-capabilities.md`
- `references/keyboard-shortcuts.md`

## Connect

1. Confirm Resolve Studio is open and external scripting is set to `Local`.
2. Call `resolve -> get_version`.
3. If the tool is unavailable, distinguish missing registration from a server
   failure. An MCP config file alone is not proof of connection.
4. Offer blueprint-only delivery or the official Python API fallback.

Install the upstream MCP server when the user approves configuration:

```bash
npx davinci-resolve-mcp setup
```

## Write Contract

Before changing Resolve, state:

- project and timeline name
- tracks to create or modify
- media and derivative paths
- color, audio, subtitle, and render operations

Obtain explicit approval. Use a new project or duplicated timeline for
substantial revisions. Preserve existing user tracks, audio, grades, and
manual work unless the user explicitly authorizes modification.

## Build

- Import only blueprint media.
- Convert seconds to frames using the actual project FPS.
- Set source in/out and record frame deliberately.
- Keep source ranges within probed bounds.
- Use explicit track roles rather than assuming A1/A2/A3 universally.
- Add BGM, LUTs, stabilization, retiming, audio processing, and renders only
  when the current request authorizes them.
- Apply LUTs to verified camera/color-space groups and read back the node LUT.

## Resolve API Boundaries

- Resolve writes are stateful; wait and retry in a fresh project/timeline when
  a batch partially fails.
- Derive frame origin from actual timeline items.
- Still-image duration may differ by Resolve version; use approved pre-rendered
  still video for frame-exact delivery.
- Resolve 19 may reject item volume writes and does not expose complete
  Fairlight sidechain automation. Measurement is not a successful write.
- Never report an unsupported or rejected operation as completed.

## Verify

Read back and report:

- active project and timeline
- item counts by track
- timeline start frame/origin
- gaps, overlaps, and one-frame errors
- each source path and source range
- source group/camera duration ratios
- adjacent repeated source, including section boundaries
- missing or offline media
- LUT/effect/property readback
- render settings and job status, when requested

A failed report or a report for an older timeline is not delivery.

Export or report enough timeline information for the parent pipeline to compare
the finished cut with the approved script: clip time ranges, source paths,
track roles, markers, captions, and narration/dialogue placement. Do not make
pickup-shot recommendations from the blueprint alone when a finished timeline
exists.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [liuluhaixiu](https://github.com/liuluhaixiu)
- **Source:** [liuluhaixiu/DaVinci-AutoEdit-Agent](https://github.com/liuluhaixiu/DaVinci-AutoEdit-Agent)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-liuluhaixiu-davinci-autoedit-agent-davinci-resolve-editor
- Seller: https://agentstack.voostack.com/s/liuluhaixiu
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.