Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
Cut a VCell release and deploy it — pick the next version, write the changelog, tag + GitHub release (triggers the CI-full image build), then CD-sites to a site (alpha→dev namespace, rel→prod…
$ npx skills add virtualcell/vcell --skill deploy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install virtualcell/vcell deploy --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/virtualcell/vcell.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/deploy .claude/skills/deploy && 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 "deploy" agent skill from https://github.com/virtualcell/vcell/tree/master/.claude/skills/deploy into .claude/skills/deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy", 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/virtualcell/vcell/tree/master/.claude/skills/deployType 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 virtualcell/vcell --skill deploy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install virtualcell/vcell deploy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/virtualcell/vcell.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/deploy .agents/skills/deploy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deploy" agent skill from https://github.com/virtualcell/vcell/tree/master/.claude/skills/deploy into .agents/skills/deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy", 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 virtualcell/vcell --skill deploy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install virtualcell/vcell deploy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/virtualcell/vcell.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/deploy .cursor/skills/deploy && 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 "deploy" agent skill from https://github.com/virtualcell/vcell/tree/master/.claude/skills/deploy into .cursor/skills/deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy", 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/virtualcell/vcell.git --path .claude/skills/deploy--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 virtualcell/vcell --skill deploy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install virtualcell/vcell deploy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/virtualcell/vcell.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/deploy .gemini/skills/deploy && 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 "deploy" agent skill from https://github.com/virtualcell/vcell/tree/master/.claude/skills/deploy into .gemini/skills/deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy", 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 virtualcell/vcell deployInstalls 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 virtualcell/vcell --skill deploy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/virtualcell/vcell.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/deploy .github/skills/deploy && 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 "deploy" agent skill from https://github.com/virtualcell/vcell/tree/master/.claude/skills/deploy into .github/skills/deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy", 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 virtualcell/vcell --skill deploy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install virtualcell/vcell deploy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/virtualcell/vcell.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/deploy .opencode/skills/deploy && 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 "deploy" agent skill from https://github.com/virtualcell/vcell/tree/master/.claude/skills/deploy into .opencode/skills/deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy", 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.
deployCut a VCell release and deploy it — pick the next version, write the changelog, tag + GitHub release (triggers the CI-full image build), then CD-sites to a site (alpha→dev namespace, rel→prod…
Deploy is an agent skill from virtualcell/vcell. Cut a VCell release and deploy it — pick the next version, write the changelog, tag + GitHub release (triggers the CI-full image build), then CD-sites to a site (alpha→dev namespace, rel→prod, test→stage). Use when asked to "deploy to alpha/dev/prod/stage", "cut a release", or "bump the version and deploy".
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Changelog and release notes. It works with GitHub. The repository describes itself as: Virtual Cell Framework.
7 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 340d6ee. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
ghgitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Deploy loads about 1.1k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 485 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.
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.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 485 words (~1,118 tokens).
“Always present the full plan (version, target site, ordered steps) and get the user's explicit confirmation BEFORE tagging, releasing, or deploying anything. The first three version parts are release-engineering decisions a human makes (docs/RELEASING.md); the target site decides who is…”
Just SKILL.md in .claude/skills/deploy of virtualcell/vcell.
Open the folder on GitHubat commit 340d6ee
Deploy 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 |
|---|---|---|---|---|---|---|
| Deploy this skillvirtualcell/vcell | 140 | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Draft Release Notesjamiepine/voicebox | 57k | — | ~941 | Automated safety check: Pass | MIT | |
| Mole Release Notes Publishertw93/Mole | 70k | — | ~1.9k | Automated safety check: Pass | GPL-3.0 | |
| Release Bumpjamiepine/voicebox | 57k | — | ~1.1k | Automated safety check: Pass | MIT |
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
jamiepine/voicebox
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
jfernandez/bpftop
Cut a new versioned release of bpftop — pick the version, open a version-bump PR, sign-tag the merge commit on main, and draft GitHub release notes in the project's established format.
virtualcell/vcell
Drive and inspect the running VCell desktop client (Swing) through the debug bridge — launch it from a source build, read the live UI as JSON, click/type/select, and verify a fix against the real app.
Works with
Categories
Cut a VCell release and deploy it — pick the next version, write the changelog, tag + GitHub release (triggers the CI-full image build), then CD-sites to a site (alpha→dev namespace, rel→prod…. Deploy is an agent skill from virtualcell/vcell. Cut a VCell release and deploy it — pick the next version, write the changelog, tag + GitHub release (triggers the CI-full image build), then CD-sites to a site (alpha→dev namespace, rel→prod, test→stage).
Deploy fits situations like: the CI-full image build); then CD-sites to a site (alpha→dev namespace; asked to deploy to alpha/dev/prod/stage; bump the version and deploy.
Run `npx skills add virtualcell/vcell --skill deploy -a claude-code`. Or copy the skill folder (.claude/skills/deploy in virtualcell/vcell) into .claude/skills/deploy in your project. Claude Code loads it when a task matches its description.
Run `npx skills add virtualcell/vcell --skill deploy -a codex`. Or copy the skill folder (.claude/skills/deploy in virtualcell/vcell) into .agents/skills/deploy in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add virtualcell/vcell --skill deploy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deploy, .gemini/skills/deploy, .github/skills/deploy and .opencode/skills/deploy in your project.
Going by SKILL.md and its folder, Deploy needs the command-line tools its instructions call (gh and git). Our summary lists: Docker.
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Deploy has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Deploy: Cutting A Release (TriliumNext/Trilium, 38k stars), Mole CLI Release Flow (tw93/Mole, 70k stars), Draft Release Notes (jamiepine/voicebox, 57k stars) and Mole Release Notes Publisher (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
virtualcell (a GitHub organization) maintains it in virtualcell/vcell, which has 140 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 8, 2026.
Source: virtualcell/vcell on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.