DaVinci Resolve MCP skills

The domain skills mostly act as routers: for one post-production job they name the Resolve MCP tools to call, the repo guides to read and the traps to avoid, either in a running Resolve or offline on project files. They cover color grading, cutting and variants, conform and relink, Fairlight audio and loudness, render setup and deliverable QC, Fusion comps, media-pool ingest and read-only footage analysis, plus an index skill and a session-start check. Two workflow skills are fuller recipes: resolve-rough-cut builds a gapless vertical rough-cut timeline from a folder of raw clips, and resolve-tighten-recording removes dead air from one long take into a variant timeline after a review step. It needs DaVinci Resolve with scripting enabled (Studio directly, the free edition only through an in-app bridge), Python and ffmpeg, and the MCP server installs with one npx command.

• 01From the README

  The install command quoted from the repository README.

  $ npx davinci-resolve-mcp setupCopy

• 02skills CLI, for Claude Code, Codex and others

  The open skills CLI from Vercel Labs installs a skill from a GitHub repo into the folder each agent expects. It asks which skills and which agents you want, and it installs for the current project unless you add the -g flag, which installs for your user account. Add --list to see what a repo contains before you install anything.

  $ npx skills add https://github.com/samuelgursky/davinci-resolve-mcp/tree/main/.agents/skillsCopy

• 03Claude Code, skills folder

  Copy the skill's folder, the one that holds SKILL.md, into ~/.claude/skills/ to use it in every project on your machine, or into .claude/skills/ in a repository to use it there and share it by committing it. Claude Code picks up changes to these folders during a session. If the folder did not exist when the session started, run /reload-skills.

• 04Claude Code, plugin marketplace

  Some repos publish a plugin marketplace, a .claude-plugin/marketplace.json file. Add it in Claude Code, then install a plugin from it with /plugin install plugin-name@marketplace-name. Plugins can bundle hooks and MCP servers along with skills, so read the details panel before you confirm.

  $ /plugin marketplace add samuelgursky/davinci-resolve-mcpCopy

• 05Codex, skills folder or $skill-installer

  Codex reads skills from .agents/skills in your working folder and its parent folders up to the repository root, and from $HOME/.agents/skills for every repository. Copy the skill's folder into one of them, or run $skill-installer inside Codex and ask it to install from the repo. Codex detects new skills automatically and needs a restart only if one does not appear.

The first command is quoted from the author's README. The others are the standard ways to install a skill from a GitHub repository. They are templates and may not apply here, for example if the repo has no plugin marketplace, so follow the README first.