Agent skill

Plugin Release Check

A skill your agent uses whenever a plugin under plugins/<name is updated/pushed, or whenever asked to write a changelog/release for the app or a plugin.

Apache-2.0Auto-check passedBackend & APIs

Install Plugin Release Check

skills CLI

$ npx skills add VoidenHQ/voiden --skill plugin-release-check -a claude-code

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

GitHub CLI

$ gh skill install VoidenHQ/voiden plugin-release-check --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/VoidenHQ/voiden.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/plugin-release-check .claude/skills/plugin-release-check && 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 "plugin-release-check" agent skill from https://github.com/VoidenHQ/voiden/tree/main/.agents/skills/plugin-release-check into .claude/skills/plugin-release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-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

$skill-installer install https://github.com/VoidenHQ/voiden/tree/main/.agents/skills/plugin-release-check

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 VoidenHQ/voiden --skill plugin-release-check -a codex

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

GitHub CLI

$ gh skill install VoidenHQ/voiden plugin-release-check --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/VoidenHQ/voiden.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/plugin-release-check .agents/skills/plugin-release-check && 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 "plugin-release-check" agent skill from https://github.com/VoidenHQ/voiden/tree/main/.agents/skills/plugin-release-check into .agents/skills/plugin-release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-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.

skills CLI

$ npx skills add VoidenHQ/voiden --skill plugin-release-check -a cursor

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

GitHub CLI

$ gh skill install VoidenHQ/voiden plugin-release-check --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/VoidenHQ/voiden.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/plugin-release-check .cursor/skills/plugin-release-check && 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 "plugin-release-check" agent skill from https://github.com/VoidenHQ/voiden/tree/main/.agents/skills/plugin-release-check into .cursor/skills/plugin-release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-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

$ gemini skills install https://github.com/VoidenHQ/voiden.git --path .agents/skills/plugin-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.

skills CLI

$ npx skills add VoidenHQ/voiden --skill plugin-release-check -a gemini-cli

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

GitHub CLI

$ gh skill install VoidenHQ/voiden plugin-release-check --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/VoidenHQ/voiden.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/plugin-release-check .gemini/skills/plugin-release-check && 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 "plugin-release-check" agent skill from https://github.com/VoidenHQ/voiden/tree/main/.agents/skills/plugin-release-check into .gemini/skills/plugin-release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-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.

GitHub CLI

$ gh skill install VoidenHQ/voiden plugin-release-check

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 VoidenHQ/voiden --skill plugin-release-check -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/VoidenHQ/voiden.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/plugin-release-check .github/skills/plugin-release-check && 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 "plugin-release-check" agent skill from https://github.com/VoidenHQ/voiden/tree/main/.agents/skills/plugin-release-check into .github/skills/plugin-release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-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.

skills CLI

$ npx skills add VoidenHQ/voiden --skill plugin-release-check -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 VoidenHQ/voiden plugin-release-check --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/VoidenHQ/voiden.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/plugin-release-check .opencode/skills/plugin-release-check && 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 "plugin-release-check" agent skill from https://github.com/VoidenHQ/voiden/tree/main/.agents/skills/plugin-release-check into .opencode/skills/plugin-release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-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: plugin-release-check
GitHub stars: 1.9k
Token cost: ~857 tokens
SKILL.md length: 365 words
Files: 1
Skills in repo: 2
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

A skill your agent uses whenever a plugin under plugins/<name is updated/pushed, or whenever asked to write a changelog/release for the app or a plugin.

Works in 3 steps: plugins//package.json → version (local… → The plugin repo's latest GitHub release… → plugins/plugin-registry/extensions.json…
A plugin under plugins/<name is updated/pushed
SKILL.md covers How to check, Decision tree per plugin and Notes
Calls node, git and gh; reaches github.com

What it does

Plugin Release Check is an agent skill from VoidenHQ/voiden. Use whenever a plugin under plugins/<name is updated/pushed, or whenever asked to write a changelog/release for the app or a plugin. Cross-checks each plugin's local package.json version against its latest GitHub release and the plugin-registry entry, so a bumped-but-unreleased plugin doesn't get silently left behind.

Its SKILL.md is about 860 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 Backend & APIs, covering Changelog and release notes and MCP servers. It works with GitHub, npm, OpenAPI and Postman. The repository describes itself as: Design, Test and Document APIs in plain Markdown. Compose Requests with API blocks. Reuse, Replace & Version everything just like code. Offline, Truly Git Native, No Lock-in. The licence is Apache-2.0.

When your agent uses it

A plugin under plugins/<name is updated/pushed
Whenever asked to write a changelog/release for the app

Example prompts

“/plugin-release-check”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

plugins//package.json → version (local working tree)
The plugin repo's latest GitHub release tag
plugins/plugin-registry/extensions.json → that plugin's "version" field

What it can do on your machine

Read from SKILL.md and the folder at commit f73a1d0. 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:
- node
- git
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- github.com
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

Plugin Release Check loads about 857 tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 365 words of instructions outside code blocks.

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

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 VoidenHQ/voiden at commit f73a1d0, republished under its Apache-2.0 licence (© VoidenHQ). 365 words, ~857 tokens.

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

name: plugin-release-check
description: Use whenever a plugin under plugins/<name> is updated/pushed, or whenever asked to write a changelog/release for the app or a plugin. Cross-checks each plugin's local package.json version against its latest GitHub release and the plugin-registry entry, so a bumped-but-unreleased plugin doesn't get silently left behind.

Plugin release / registry consistency check

Each directory under plugins/<name>/ is its own independent git repo (its own GitHub remote, its own versioning, its own release cycle) — separate from the main Voiden app. The central source of truth for what's actually installable is plugins/plugin-registry/extensions.json, one object per plugin, keyed by id, with at least repo (owner/name), version, and voidenVersion.

These three numbers can drift out of sync:

plugins/<name>/package.json → version (local working tree)
The plugin repo's latest GitHub release tag
plugins/plugin-registry/extensions.json → that plugin's "version" field

How to check

For each plugin directory with a package.json and a git remote (skip plugin-registry itself):

bash

# 1. Local version
node -p "require('./plugins/<name>/package.json').version"

# 2. Repo remote -> owner/name
git -C plugins/<name> remote get-url origin   # https://github.com/<owner>/<repo>.git

# 3. Latest GitHub release tag for that repo
gh release view --repo <owner>/<repo> --json tagName -q .tagName

# 4. Registry's recorded version for that plugin id
# (read plugins/plugin-registry/extensions.json, find the matching "id")

Strip the leading v from the release tag before comparing against semver in package.json.

Decision tree per plugin

local version > latest release tag → the working tree has unreleased changes. Ask the user to cut a new GitHub release (with the built runner/asset, matching how existing releases for that repo are structured) for that plugin — do not create the release yourself, this is a user-confirmed action. Mention that extensions.json will also need its version (and voidenVersion, if the plugin's minimum Voiden version requirement changed) updated to match once the release exists.
local version == latest release tag, but registry version differs → the release exists but the registry hasn't caught up. Update plugins/plugin-registry/extensions.json for that plugin's entry: version (and voidenVersion if it changed in this release) — bring it in sync with the actual release tag. This repo is also independent, so committing/pushing there needs the same confirmation as any other push.
local version < latest release tag → the local checkout is just stale (someone released ahead of what's checked out here). Not actionable — no release or registry change needed, just note it if relevant.
all three match → nothing to do.

Show full SKILL.md (76 more words)Show less

Notes

Never create a GitHub release on the user's behalf — always ask first, same as any other push/release action.
extensions.json edits are a normal file edit (fine to make directly), but committing/pushing them in the plugin-registry repo is a separate confirm-first step.
This check pairs naturally with [[release-changelog]] — when asked to write a changelog entry (app or plugin), also run this check so a plugin version bump that shipped code but never got tagged isn't missed.

Files

Just SKILL.md in .agents/skills/plugin-release-check of VoidenHQ/voiden.

Open the folder on GitHubat commit f73a1d0

Compare with similar skills

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

Plugin Release Check compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Plugin Release Check this skillVoidenHQ/voiden	1.9k	—	~857	Automated safety check: Pass	Apache-2.0	today
Release WorkflowGoldziher/spikard	123	—	~909	Automated safety check: Pass	MIT	3 days ago
Dependabot Alerts Updatelivesession/xyd	114	—	~2k	Automated safety check: Pass	MIT	15 days ago
Yaak Changelogmountain-loop/yaak	19k	—	~1.6k	Automated safety check: Pass	MIT	today
Project Releaseswimmwatch/cloakbrowser-mcp	161	—	~1.9k	Automated safety check: Pass	MIT	5 days ago
ToolJet Marketplace Plugin BuilderToolJet/ToolJet	41k	—	~2.1k	Automated safety check: Pass	AGPL-3.0	today

Similar skills

Release Workflow
Goldziher/spikard
Release/publish the spikard Rust core crate and CLI end-to-end.
123 GitHub stars~909 tokensUpdated 3 days ago
Backend & APIsAuto-check passed
Dependabot Alerts Update
livesession/xyd
Automatically fetch and fix Dependabot security alerts by querying GitHub REST API for open alerts, identifying vulnerable packages, researching secure versions, and updating package.json files…
114 GitHub stars~2k tokensUpdated 15 days ago
DevelopmentAuto-check passed
Yaak Changelog
mountain-loop/yaak
Create or edit Yaak changelogs. An agent skill from mountain-loop/yaak.
19k GitHub stars~1.6k tokensUpdated today
DevelopmentAuto-check passed
Project Release
swimmwatch/cloakbrowser-mcp
Prepare, publish, verify, or recover a cloakbrowser-mcp release only when the user explicitly requests release work.
161 GitHub stars~1.9k tokensUpdated 5 days ago
Agent WorkflowsAuto-check passed
ToolJet Marketplace Plugin Builder
ToolJet/ToolJet
Turns an API description, such as an OpenAPI file or a Postman collection, into a connector plugin for ToolJet's marketplace and checks it with the repo's validator.
41k GitHub stars~2.1k tokensUpdated today
Backend & APIsAuto-check passed
Use Yaak
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
19k GitHub stars~1.9k tokensUpdated today
Backend & APIsAuto-check passed

Questions about Plugin Release Check

What does Plugin Release Check do?

A skill your agent uses whenever a plugin under plugins/<name is updated/pushed, or whenever asked to write a changelog/release for the app or a plugin. Plugin Release Check is an agent skill from VoidenHQ/voiden. Use whenever a plugin under plugins/<name is updated/pushed, or whenever asked to write a changelog/release for the app or a plugin.

When should I use Plugin Release Check?

Plugin Release Check fits situations like: A plugin under plugins/<name is updated/pushed; whenever asked to write a changelog/release for the app.

How do I install Plugin Release Check in Claude Code?

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

How do I install Plugin Release Check in Codex?

Run `npx skills add VoidenHQ/voiden --skill plugin-release-check -a codex`. Or copy the skill folder (.agents/skills/plugin-release-check in VoidenHQ/voiden) into .agents/skills/plugin-release-check in your project. Codex loads it when a task matches its description.

Can I use Plugin 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 VoidenHQ/voiden --skill plugin-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/plugin-release-check, .gemini/skills/plugin-release-check, .github/skills/plugin-release-check and .opencode/skills/plugin-release-check in your project.

What does Plugin Release Check need to run?

Going by SKILL.md and its folder, Plugin Release Check needs the command-line tools its instructions call (node, git and gh).

Does Plugin Release Check access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

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

Plugin Release Check is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Plugin Release Check use?

About 857 tokens (SKILL.md is roughly 3.4k 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 Plugin Release Check?

Skills that share tags, products or a category with Plugin Release Check: Release Workflow (Goldziher/spikard, 123 stars), Dependabot Alerts Update (livesession/xyd, 114 stars), Yaak Changelog (mountain-loop/yaak, 19k stars) and Project Release (swimmwatch/cloakbrowser-mcp, 161 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Plugin Release Check?

VoidenHQ (a GitHub organization) maintains it in VoidenHQ/voiden, which has 1,933 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.

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

Plugin Release Check

Install Plugin Release Check

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Plugin release / registry consistency check

How to check

Decision tree per plugin

Notes

Files

Compare with similar skills

Similar skills

Release Workflow

Dependabot Alerts Update

Yaak Changelog

Project Release

ToolJet Marketplace Plugin Builder

Use Yaak

More from VoidenHQ/voiden

Release Changelog

Questions about Plugin Release Check

Install Plugin Release Check

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Plugin release / registry consistency check

How to check

Decision tree per plugin

Notes

Files

Compare with similar skills

Similar skills

Release Workflow

Dependabot Alerts Update

Yaak Changelog

Project Release

ToolJet Marketplace Plugin Builder

Use Yaak

More from VoidenHQ/voiden

Release Changelog

Related

Questions about Plugin Release Check