Skill Seekers Builder
yusufkaraaslan/Skill_Seekers
Detects the type of a knowledge source and uses the Skill Seekers MCP tools to turn docs, repos, PDFs or videos into packaged AI skills.
Walk through a version bump and release for the DaVinci Resolve MCP server — version selection, every file that needs updating, required validation, tag, and GitHub Release.
Install Release Check
$ npx skills add samuelgursky/davinci-resolve-mcp --skill release-check -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install samuelgursky/davinci-resolve-mcp release-check --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/samuelgursky/davinci-resolve-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-check .claude/skills/release-check && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-check" agent skill from https://github.com/samuelgursky/davinci-resolve-mcp/tree/main/.agents/skills/release-check into .claude/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/samuelgursky/davinci-resolve-mcp/tree/main/.agents/skills/release-checkType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add samuelgursky/davinci-resolve-mcp --skill release-check -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install samuelgursky/davinci-resolve-mcp release-check --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samuelgursky/davinci-resolve-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/release-check .agents/skills/release-check && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-check" agent skill from https://github.com/samuelgursky/davinci-resolve-mcp/tree/main/.agents/skills/release-check into .agents/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add samuelgursky/davinci-resolve-mcp --skill release-check -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install samuelgursky/davinci-resolve-mcp release-check --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samuelgursky/davinci-resolve-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/release-check .cursor/skills/release-check && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-check" agent skill from https://github.com/samuelgursky/davinci-resolve-mcp/tree/main/.agents/skills/release-check into .cursor/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/samuelgursky/davinci-resolve-mcp.git --path .agents/skills/release-check--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add samuelgursky/davinci-resolve-mcp --skill release-check -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install samuelgursky/davinci-resolve-mcp release-check --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samuelgursky/davinci-resolve-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/release-check .gemini/skills/release-check && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-check" agent skill from https://github.com/samuelgursky/davinci-resolve-mcp/tree/main/.agents/skills/release-check into .gemini/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install samuelgursky/davinci-resolve-mcp release-checkInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add samuelgursky/davinci-resolve-mcp --skill release-check -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/samuelgursky/davinci-resolve-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/release-check .github/skills/release-check && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-check" agent skill from https://github.com/samuelgursky/davinci-resolve-mcp/tree/main/.agents/skills/release-check into .github/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add samuelgursky/davinci-resolve-mcp --skill release-check -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install samuelgursky/davinci-resolve-mcp release-check --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samuelgursky/davinci-resolve-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/release-check .opencode/skills/release-check && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-check" agent skill from https://github.com/samuelgursky/davinci-resolve-mcp/tree/main/.agents/skills/release-check into .opencode/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-check- GitHub stars
- 3.4k
- Token cost
- ~373 tokens
- SKILL.md length
- 182 words
- Files
- 2
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Walk through a version bump and release for the DaVinci Resolve MCP server — version selection, every file that needs updating, required validation, tag, and GitHub Release.
- Works in 4 steps: Read docs/process/release-process.md in… → Follow it top to bottom: version… → Report progress against that doc's own… → …
- Tasks that involve MCP servers
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Release Check is an agent skill from samuelgursky/davinci-resolve-mcp. Walk through a version bump and release for the DaVinci Resolve MCP server — version selection, every file that needs updating, required validation, tag, and GitHub Release.
Its SKILL.md is about 370 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol and GitHub. The repository describes itself as: MCP server integration for DaVinci Resolve Studio. The licence is MIT.
When your agent uses it
- Tasks that involve MCP servers
Example prompts
- “/release-check”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Read docs/process/release-process.md in full, current from disk — not
- Follow it top to bottom: version selection, every file under "Files To
- Report progress against that doc's own sections as you go, so the user can
- If the doc's content is genuinely ambiguous or conflicts with the current
What it can do on your machine
Read from SKILL.md and the folder at commit 94c7a88. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release Check loads about 373 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 182 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from samuelgursky/davinci-resolve-mcp at commit 94c7a88, republished under its MIT licence (© samuelgursky). 182 words, ~373 tokens.
Download SKILL.mdSave it as
.claude/skills/release-check/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- release-check
- description
- Walk through a version bump and release for the DaVinci Resolve MCP server — version selection, every file that needs updating, required validation, tag, and GitHub Release.
- disable-model-invocation
- true
Release Check
CLAUDE.md is explicit: this repository does not maintain a separate release
checklist here or anywhere else — docs/process/release-process.md
is the single source of truth for version bumps, validation, tags, and GitHub
Releases. This skill does not restate that checklist; restating it would
create a second copy that can drift from the original.
Steps
- Read
docs/process/release-process.mdin full, current from disk — not from memory of a prior run. It changes as the release process hardens. - Follow it top to bottom: version selection, every file under "Files To Update," the "Required Validation" section, and the tag/GitHub Release steps at the end.
- Report progress against that doc's own sections as you go, so the user can
see which step you're on. Do not invent extra steps or skip any listed
file — the doc calls out drift guards (
test_api_limitations_doc,test_panel_docs_drift, etc.) that fail CI if a listed file is missed. - If the doc's content is genuinely ambiguous or conflicts with the current repo state, stop and ask rather than guessing — this is release engineering on a published package, not exploratory work.
© samuelgursky, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/release-check of samuelgursky/davinci-resolve-mcp.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 94c7a88
Compare with similar skills
Release Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Check this skillsamuelgursky/davinci-resolve-mcp | 3.4k | — | ~373 | Automated safety check: Pass | MIT | |
| Skill Seekers Builderyusufkaraaslan/Skill_Seekers | 15k | — | ~760 | Automated safety check: Pass | MIT | |
| MCP Apps Builderawslabs/cli-agent-orchestrator | 1.4k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Releasejgravelle/jcodemunch-mcp | 2.7k | — | ~6.5k | Automated safety check: Pass | Custom licence | |
| Open PRArcadeAI/arcade-mcp | 1k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Triage Security Advisoriesactivepieces/activepieces | 25k | — | ~3.9k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
MCP Apps Builder
awslabs/cli-agent-orchestrator
Load the official MCP Apps builder skills (create-mcp-app, migrate-oai-app, add-app-to-server, convert-web-app) from github.com/modelcontextprotocol/ext-apps.
Release
jgravelle/jcodemunch-mcp
Publishing a jMunch release (jcodemunch-mcp, jdocmunch-mcp, jdatamunch-mcp, jragmunch-cli), reviewing/merging/closing PRs, and responding to the community.
Open PR
ArcadeAI/arcade-mcp
Prepare arcade-mcp changes for review by verifying intended behavior, filling the repository PR template, and creating or updating the PR.
Triage Security Advisories
activepieces/activepieces
Triage the GitHub privately-reported vulnerability backlog for Activepieces — pull repository security advisories from the Security tab, scope-check against SECURITY.md, deeply validate each…
MCP Client
coleam00/second-brain-skills
Universal MCP client for connecting to any MCP server with progressive disclosure.
More from samuelgursky/davinci-resolve-mcp
All 14 skills in this repoResolve MCP
samuelgursky/davinci-resolve-mcp
Orientation and index for DaVinci Resolve MCP work — grading, editing, conforming, delivery, media analysis, and .drp/.drt/.drx file work, live in a running Resolve or offline with none open.
Resolve Rough Cut
samuelgursky/davinci-resolve-mcp
Assembling a short-form social rough cut from raw behind-the-scenes or vlog footage in the DaVinci Resolve MCP.
House Style
samuelgursky/davinci-resolve-mcp
The editorial and finishing preferences this project's work is judged against — cut rhythm, shot selection, delivery conventions, and the corrections that have already been given.
Resolve Audio
samuelgursky/davinci-resolve-mcp
Audio and Fairlight work in the DaVinci Resolve MCP. An agent skill from samuelgursky/davinci-resolve-mcp.
Resolve Color
samuelgursky/davinci-resolve-mcp
Color grading and look work in the DaVinci Resolve MCP. An agent skill from samuelgursky/davinci-resolve-mcp.
Resolve Conform
samuelgursky/davinci-resolve-mcp
Conforming, relinking, and finishing prep in the DaVinci Resolve MCP.
Related
Works with
Categories
Questions about Release Check
What does Release Check do?
Walk through a version bump and release for the DaVinci Resolve MCP server — version selection, every file that needs updating, required validation, tag, and GitHub Release. Release Check is an agent skill from samuelgursky/davinci-resolve-mcp. Walk through a version bump and release for the DaVinci Resolve MCP server — version selection, every file that needs updating, required validation, tag, and GitHub Release.
When should I use Release Check?
Release Check fits situations like: tasks that involve MCP servers.
How do I install Release Check in Claude Code?
Run `npx skills add samuelgursky/davinci-resolve-mcp --skill release-check -a claude-code`. Or copy the skill folder (.agents/skills/release-check in samuelgursky/davinci-resolve-mcp) into .claude/skills/release-check in your project. Claude Code loads it when a task matches its description.
How do I install Release Check in Codex?
Run `npx skills add samuelgursky/davinci-resolve-mcp --skill release-check -a codex`. Or copy the skill folder (.agents/skills/release-check in samuelgursky/davinci-resolve-mcp) into .agents/skills/release-check in your project. Codex loads it when a task matches its description.
Can I use Release Check in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add samuelgursky/davinci-resolve-mcp --skill release-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-check, .gemini/skills/release-check, .github/skills/release-check and .opencode/skills/release-check in your project.
What does Release Check need to run?
SKILL.md names no scripts, command-line tools or credentials: Release Check is instructions for the agent only.
Does Release Check access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Release Check safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Release Check use?
Release Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Check use?
About 373 tokens (SKILL.md is roughly 1.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Release Check?
Skills that share tags, products or a category with Release Check: Skill Seekers Builder (yusufkaraaslan/Skill_Seekers, 15k stars), MCP Apps Builder (awslabs/cli-agent-orchestrator, 1.4k stars), Release (jgravelle/jcodemunch-mcp, 2.7k stars) and Open PR (ArcadeAI/arcade-mcp, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Check?
samuelgursky (a GitHub user) maintains it in samuelgursky/davinci-resolve-mcp, which has 3,448 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 9, 2026.
Source: samuelgursky/davinci-resolve-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.