Agent skill

Release

by vellum-ai in vellum-ai/vellum-assistant

Cut a new release: create the release branch (staging bake), then dispatch the production Release run on that branch.

MITAuto-check passed

Install Release

skills CLI

$ npx skills add vellum-ai/vellum-assistant --skill release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install vellum-ai/vellum-assistant release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release .claude/skills/release && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "release" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/.claude/skills/release into .claude/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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

$skill-installer install https://github.com/vellum-ai/vellum-assistant/tree/main/.claude/skills/release

Type 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.

skills CLI

$ npx skills add vellum-ai/vellum-assistant --skill release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install vellum-ai/vellum-assistant release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/release .agents/skills/release && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "release" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/.claude/skills/release into .agents/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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.

skills CLI

$ npx skills add vellum-ai/vellum-assistant --skill release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install vellum-ai/vellum-assistant release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/release .cursor/skills/release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "release" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/.claude/skills/release into .cursor/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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

$ gemini skills install https://github.com/vellum-ai/vellum-assistant.git --path .claude/skills/release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add vellum-ai/vellum-assistant --skill release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install vellum-ai/vellum-assistant release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/release .gemini/skills/release && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "release" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/.claude/skills/release into .gemini/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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.

GitHub CLI

$ gh skill install vellum-ai/vellum-assistant release

Installs 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).

skills CLI

$ npx skills add vellum-ai/vellum-assistant --skill release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/release .github/skills/release && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "release" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/.claude/skills/release into .github/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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.

skills CLI

$ npx skills add vellum-ai/vellum-assistant --skill release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install vellum-ai/vellum-assistant release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/release .opencode/skills/release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "release" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/.claude/skills/release into .opencode/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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
GitHub stars: 1.4k
Token cost: ~801 tokens
SKILL.md length: 345 words
Files: 1
Skills in repo: 108
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Cut a new release: create the release branch (staging bake), then dispatch the production Release run on that branch.

Works in 5 steps: Pull latest main and show the payload → Cut the release branch (staging bake) → Dispatch the production release → …
Calls git and gh

What it does

Release is an agent skill from vellum-ai/vellum-assistant. Cut a new release: create the release branch (staging bake), then dispatch the production Release run on that branch.

Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Slack. The repository describes itself as: An AI Assistant that’s easy to setup, does your work 24/7, knows your preferences and gets better over time. The licence is MIT.

Example prompts

“/release”

Requirements

Docker

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Pull latest main and show the payload
Cut the release branch (staging bake)
Dispatch the production release
Verify
Report

What it can do on your machine

Read from SKILL.md and the folder at commit 33cc983. 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
Shell commands in SKILL.md call:
- git
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
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 loads about 801 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 345 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~31
When it runs · the whole SKILL.md, loaded when a task matches: ~801

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 vellum-ai/vellum-assistant at commit 33cc983, republished under its MIT licence (© vellum-ai). 345 words, ~801 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).

name: release
description: Cut a new release: create the release branch (staging bake), then dispatch the production Release run on that branch.

Cut a new release. Releases are a two-step process:

Branch cut → staging bake: create-release-branch.yml computes the version from the bump type, deletes any stale release/v<X.Y.Z> branch, cuts a fresh one from main HEAD with the version-bump commit, and pushes it. That push triggers a Release run on the branch which is a staging deploy (push-triggered and main-dispatched Release runs are always staging).
Production: dispatching release.yml on the release/v<X.Y.Z> branch runs the full production release — tag, GitHub Release, DMG sign/notarize/publish, npm packages, Docker Hub images, iOS TestFlight, platform dependency bump, and the merge-back of the release branch to main.

Step 1 is a manual workflow_dispatch of create-release-branch.yml (the Tue/Thu 7:52am ET cron is disabled). A human performs step 2 after the staging bake is green. A release/v<X.Y.Z> branch with no corresponding GitHub Release means a cut was never promoted. Re-running step 1 refreshes it from current main.

The user may pass $ARGUMENTS as the bump type for step 1: patch, minor, major, or hotfix (patch cut from the latest release tag's commit instead of main, pushed [skip ci] for manual cherry-picks). Default to patch.

Steps

1. Pull latest main and show the payload

bash

git checkout main && git pull
git describe --tags --abbrev=0
git log --oneline "$(git describe --tags --abbrev=0)"..origin/main | head -20

Confirm with the user before proceeding unless they already asked for the release explicitly.

2. Cut the release branch (staging bake)

bash

gh workflow run create-release-branch.yml \
  --repo vellum-ai/vellum-assistant \
  --ref main \
  --field bump=<patch|minor|major|hotfix>

Then wait for the branch cut and find the staging Release run its push triggered:

bash

gh run list --workflow="Create Release Branch" --limit 1
gh run list --workflow=Release --branch "release/v<X.Y.Z>" --limit 1

The version appears in the branch name; the staging run takes ~15-20 minutes. Wait for it to succeed — it is the CI bake for the exact release payload. If it fails, fix main and re-run this step (it recuts the branch from main HEAD).

3. Dispatch the production release

bash

gh workflow run release.yml \
  --repo vellum-ai/vellum-assistant \
  --ref "release/v<X.Y.Z>"

The only dispatch input is the optional slack_user_id (--field slack_user_id=U…) for the release notification; omit it when unknown.

4. Verify

The production run takes ~20 minutes. When it completes:

bash

gh release list --limit 1        # v<X.Y.Z> should be Latest
git fetch --tags && git tag -l "v<X.Y.Z>"
git log --oneline origin/main -1 # merge-back commit "Release v<X.Y.Z>"

If the merge-back to main failed, the run's Slack notification includes the manual-merge command.

5. Report

Output:

The version number and a link to the production run
Confirmation that the GitHub Release, tag, and merge-back all landed

Files

Just SKILL.md in .claude/skills/release of vellum-ai/vellum-assistant.

Open the folder on GitHubat commit 33cc983

Compare with similar skills

Release 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.

Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Release this skillvellum-ai/vellum-assistant	1.4k	—	~801	Automated safety check: Pass	MIT	today
Agent Browser CLIvercel-labs/agent-browser	44k	24 repos	~864	Automated safety check: Pass	Apache-2.0	today
Slack GIF Creatoranthropics/skills	180k	29 repos	~2k	Automated safety check: Pass	Apache-2.0	today
Code Design Rationale Investigatorcursor/plugins	11k	9 repos	~2.6k	Automated safety check: Pass	None	today
Electron App Automationvercel-labs/agent-browser	44k	5 repos	~1.7k	Automated safety check: Pass	Apache-2.0	today
Slack Browser Automationvercel-labs/agent-browser	44k	1 repos	~2.1k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Agent Browser CLI
vercel-labs/agent-browser
Official
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking…
44k GitHub starsUsed in 24 repos~864 tokens
Productivity & AutomationAuto-check passed
Slack GIF Creator
anthropics/skills
Official
Provides Slack size and frame limits, Python animation helpers and validators for building animated GIFs sized for emoji and messages.
180k GitHub starsUsed in 29 repos~2k tokens
Media & CreativeAuto-check passed
Code Design Rationale Investigator
cursor/plugins
Official
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
11k GitHub starsUsed in 9 repos~2.6k tokens
DevelopmentAuto-check passed
Electron App Automation
vercel-labs/agent-browser
Official
Automates Electron desktop apps such as VS Code, Slack or Discord by connecting agent-browser to their Chrome DevTools Protocol port.
44k GitHub starsUsed in 5 repos~1.7k tokens
Productivity & AutomationAuto-check passed
Slack Browser Automation
vercel-labs/agent-browser
Official
Drives the Slack web app with the agent-browser CLI to check unread channels, search, read channel details and extract information, with screenshots as evidence.
44k GitHub starsUsed in 1 repo~2.1k tokens
Productivity & AutomationAuto-check passed
Composio
ComposioHQ/composio
Route and complete Composio work across Composio For You and Composio Platform.
30k GitHub starsUsed in 1 repo~1.7k tokens
Productivity & AutomationAuto-check passed

Questions about Release

What does Release do?

Cut a new release: create the release branch (staging bake), then dispatch the production Release run on that branch. Release is an agent skill from vellum-ai/vellum-assistant. Cut a new release: create the release branch (staging bake), then dispatch the production Release run on that branch.

How do I install Release in Claude Code?

Run `npx skills add vellum-ai/vellum-assistant --skill release -a claude-code`. Or copy the skill folder (.claude/skills/release in vellum-ai/vellum-assistant) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.

How do I install Release in Codex?

Run `npx skills add vellum-ai/vellum-assistant --skill release -a codex`. Or copy the skill folder (.claude/skills/release in vellum-ai/vellum-assistant) into .agents/skills/release in your project. Codex loads it when a task matches its description.

Can I use Release 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 vellum-ai/vellum-assistant --skill release -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, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.

What does Release need to run?

Going by SKILL.md and its folder, Release needs the command-line tools its instructions call (git and gh). Our summary lists: Docker.

Does Release access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Release 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 use?

Release 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 use?

About 801 tokens (SKILL.md is roughly 3.2k 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?

Skills that share tags, products or a category with Release: Agent Browser CLI (vercel-labs/agent-browser, 44k stars), Slack GIF Creator (anthropics/skills, 180k stars), Code Design Rationale Investigator (cursor/plugins, 11k stars) and Electron App Automation (vercel-labs/agent-browser, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

vellum-ai (a GitHub organization) maintains it in vellum-ai/vellum-assistant, which has 1,408 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 9, 2026.

Source: vellum-ai/vellum-assistant on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Release

Install Release

Facts

At a glance

What it does

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Steps

1. Pull latest main and show the payload

2. Cut the release branch (staging bake)

3. Dispatch the production release

4. Verify

5. Report

Files

Compare with similar skills

Similar skills

Agent Browser CLI

Slack GIF Creator

Code Design Rationale Investigator

Electron App Automation

Slack Browser Automation

Composio

More from vellum-ai/vellum-assistant

Vellum GitHub App Setup

Discord App Setup

Sentry App Setup

Memory Corpus Ingest

Plugin Builder

Slack App Setup

Questions about Release

Install Release

Facts

At a glance

What it does

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Steps

1. Pull latest main and show the payload

2. Cut the release branch (staging bake)

3. Dispatch the production release

4. Verify

5. Report

Files

Compare with similar skills

Similar skills

More from vellum-ai/vellum-assistant

Related

Questions about Release