Agent skill

Release

Plugin release process for MAG Claude Plugins marketplace. An agent skill from MadAppGang/claude-code.

MITAuto-check passedDevelopment

Install Release

skills CLI

$ npx skills add MadAppGang/claude-code --skill release -a claude-code

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

GitHub CLI

$ gh skill install MadAppGang/claude-code 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/MadAppGang/claude-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/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/MadAppGang/claude-code/tree/main/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/MadAppGang/claude-code/tree/main/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 MadAppGang/claude-code --skill release -a codex

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

GitHub CLI

$ gh skill install MadAppGang/claude-code 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/MadAppGang/claude-code.git skills-src && mkdir -p .agents/skills && cp -r skills-src/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/MadAppGang/claude-code/tree/main/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 MadAppGang/claude-code --skill release -a cursor

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

GitHub CLI

$ gh skill install MadAppGang/claude-code 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/MadAppGang/claude-code.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/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/MadAppGang/claude-code/tree/main/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/MadAppGang/claude-code.git --path 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 MadAppGang/claude-code --skill release -a gemini-cli

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

GitHub CLI

$ gh skill install MadAppGang/claude-code 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/MadAppGang/claude-code.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/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/MadAppGang/claude-code/tree/main/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 MadAppGang/claude-code 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 MadAppGang/claude-code --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/MadAppGang/claude-code.git skills-src && mkdir -p .github/skills && cp -r skills-src/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/MadAppGang/claude-code/tree/main/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 MadAppGang/claude-code --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 MadAppGang/claude-code 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/MadAppGang/claude-code.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/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/MadAppGang/claude-code/tree/main/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: 285
Token cost: ~1.2k tokens
SKILL.md length: 357 words
Files: 1
Skills in repo: 69
Repo updated: Mar 15, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Plugin release process for MAG Claude Plugins marketplace. An agent skill from MadAppGang/claude-code.

Works in 5 steps: Update Plugin Files → Update Documentation → ⚠️ CRITICAL - Update Marketplace Catalog → …
Releasing new plugin versions
SKILL.md covers Critical Understanding, Release Checklist, Common Mistakes and Version Numbering, plus 3 more sections
Calls git

What it does

Release is an agent skill from MadAppGang/claude-code. Plugin release process for MAG Claude Plugins marketplace. Covers version bumping, marketplace.json updates, git tagging, and common mistakes. Use when releasing new plugin versions or troubleshooting update issues.

Its SKILL.md is about 1.2k 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 Deployment and Hooks and plugins. It works with Git. The repository describes itself as: claude code plugins marketplace. The licence is MIT.

When your agent uses it

Releasing new plugin versions
Troubleshooting update issues

Example prompts

“/release”

Workflow steps

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

Update Plugin Files
Update Documentation
⚠️ CRITICAL - Update Marketplace Catalog
Commit and Tag
Verify

What it can do on your machine

Read from SKILL.md and the folder at commit 6097ad4. 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
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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 1.2k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 357 words of instructions outside code blocks.

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

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 MadAppGang/claude-code at commit 6097ad4, republished under its MIT licence (© MadAppGang). 357 words, ~1,241 tokens.

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

name: release
description: Plugin release process for MAG Claude Plugins marketplace. Covers version bumping, marketplace.json updates, git tagging, and common mistakes. Use when releasing new plugin versions or troubleshooting update issues.

Plugin Release Process

Complete guide for releasing new versions of plugins in the MAG Claude Plugins marketplace.

Critical Understanding

Claude Code plugin discovery works through TWO configuration files that MUST BOTH BE UPDATED:

plugins/{plugin-name}/plugin.json - The plugin's own version metadata
.claude-plugin/marketplace.json - The marketplace catalog (what users see when browsing)

Why both?

plugin.json - Defines the plugin itself (agents, commands, version)
marketplace.json - The "catalog" that Claude Code reads for plugin discovery
Users run /plugin marketplace update which reads marketplace.json
If you only update plugin.json, users won't see the new version!

Release Checklist

Step 1: Update Plugin Files

plugins/{plugin-name}/plugin.json - Update version field
plugins/{plugin-name}/agents/*.md - Add new agents (if any)
plugins/{plugin-name}/commands/*.md - Update commands (if any)
plugins/{plugin-name}/skills/*/SKILL.md - Add new skills (if any)

Step 2: Update Documentation

CHANGELOG.md - Add new version entry at the top
RELEASES.md - Add detailed release notes at the top
CLAUDE.md - Update ALL version references (6+ locations)

Step 3: ⚠️ CRITICAL - Update Marketplace Catalog

File: .claude-plugin/marketplace.json

Update TWO fields:

Marketplace metadata version (line ~10):

json

"metadata": {
  "version": "3.3.0"  // ← Update this
}

Specific plugin version (in plugins array):

json

"plugins": [
  {
    "name": "frontend",
    "version": "3.3.0",      // ← Update this (CRITICAL!)
    "description": "..."     // ← Update if description changed
  }
]

Step 4: Commit and Tag

bash

# Commit all changes
git add -A
git commit -m "feat({plugin}): v{X.Y.Z} - {Feature summary}"

# Create tag (format: plugins/{plugin-name}/v{X.Y.Z})
git tag -a plugins/{plugin}/v{X.Y.Z} -m "..."

# Push
git push origin main
git push origin plugins/{plugin}/v{X.Y.Z}

Step 5: Verify

bash

/plugin marketplace update mag-claude-plugins
# Should show new version ✅

Common Mistakes

❌ #1: Forgot to update marketplace.json

Symptom: Users still see old version after /plugin marketplace update

Fix:

bash

# Update .claude-plugin/marketplace.json
vim .claude-plugin/marketplace.json
# Update plugins[].version field

git add .claude-plugin/marketplace.json
git commit -m "fix(marketplace): Update {plugin} version to v{X.Y.Z}"
git push origin main

❌ #2: Wrong git tag format

Wrong: frontend-v3.3.0, v3.3.0, frontend/v3.3.0 Correct: plugins/frontend/v3.3.0 ✅

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

❌ #3: Inconsistent versions

Problem: plugin.json says v3.3.0 but marketplace.json says v3.2.0

Prevention: Use checklist, search for old version: grep -r "3.2.0" .

Version Numbering

MAJOR (X.0.0): Breaking changes (removed agents, changed behavior) MINOR (x.Y.0): New features (new agents/commands, backward compatible) PATCH (x.y.Z): Bug fixes (no new features, backward compatible)

Quick Reference

Minimal checklist:

✅ Update plugins/{plugin}/plugin.json version
✅ Update .claude-plugin/marketplace.json plugin version ⚠️ CRITICAL
✅ Update CHANGELOG.md, RELEASES.md, CLAUDE.md
✅ Commit: git commit -m "feat({plugin}): v{X.Y.Z} - {summary}"
✅ Tag: git tag -a plugins/{plugin}/v{X.Y.Z} -m "..."
✅ Push: git push origin main && git push origin plugins/{plugin}/v{X.Y.Z}
✅ Verify: /plugin marketplace update shows new version

Example Release

bash

# 1. Update versions
vim plugins/frontend/plugin.json          # version: "3.3.0"
vim .claude-plugin/marketplace.json       # plugins[0].version: "3.3.0"  ← DON'T FORGET!
vim CHANGELOG.md RELEASES.md CLAUDE.md

# 2. Commit
git add -A
git commit -m "feat(frontend): v3.3.0 - Multi-Model Plan Review"

# 3. Tag
git tag -a plugins/frontend/v3.3.0 -m "Frontend Plugin v3.3.0"

# 4. Push
git push origin main
git push origin plugins/frontend/v3.3.0

# 5. Verify
/plugin marketplace update mag-claude-plugins
# Output: frontend v3.3.0 ✅

Troubleshooting

Q: Users still see old version A: Check .claude-plugin/marketplace.json - version must match plugin.json

Q: Tag already exists A: git tag -d {tag} then git push origin :{tag} then recreate

Q: How to test locally? A: /plugin marketplace add /path/to/claude-code

Related: RELEASE_PROCESS.md - Full detailed documentation

Last Updated: November 13, 2025

Files

Just SKILL.md in skills/release of MadAppGang/claude-code.

Open the folder on GitHubat commit 6097ad4

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 skillMadAppGang/claude-code	285	—	~1.2k	Automated safety check: Pass	MIT	6 mo ago
Hns Moaiadk Dev Referencemodu-ai/moai-adk	1.2k	—	~937	Automated safety check: Pass	Apache-2.0	today
ClawRouter Release ChecklistBlockRunAI/ClawRouter	6.6k	—	~1.4k	Automated safety check: Pass	MIT	4 days ago
Release Lithoxylmahmoud/lithoxyl	146	—	~1.3k	Automated safety check: Pass	BSD-3-Clause	2 mo ago
AnyDrag Release RoutineXueshiQiao/AnyDrag	227	—	~2.6k	Automated safety check: Pass	GPL-3.0	5 days ago
Product Surface Checkelliothux/open-compute	1.8k	—	~2.4k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Hns Moaiadk Dev Reference
modu-ai/moai-adk
moai-adk-go local dev reference — version management/release process (sec 5), shell-script hook development (sec 7), build & dev commands (sec 10).
1.2k GitHub stars~937 tokensUpdated today
DevelopmentAuto-check passed
ClawRouter Release Checklist
BlockRunAI/ClawRouter
Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release.
6.6k GitHub stars~1.4k tokensUpdated 4 days ago
DevelopmentAuto-check passed
Release Lithoxyl
mahmoud/lithoxyl
Walks through releasing the lithoxyl Python package to PyPI: CalVer version bump, tagging, pushing and checking the published release.
146 GitHub stars~1.3k tokensUpdated 2 mo ago
DevelopmentAuto-check passed
AnyDrag Release Routine
XueshiQiao/AnyDrag
Runs the full AnyDrag release process end to end, from cumulative bilingual release notes through version bumping to watching CI and the Homebrew cask update.
227 GitHub stars~2.6k tokensUpdated 5 days ago
DevelopmentAuto-check passed
Product Surface Check
elliothux/open-compute
Manually review changed open-compute behavior for drift across maintained user, operator, API, SDK, configuration, deployment, capability, CLI, Dashboard, and release surfaces.
1.8k GitHub stars~2.4k tokensUpdated yesterday
DevelopmentAuto-check passed
Plugin Version Bump and Release
thedotmack/claude-mem
Runs a semantic-versioning release workflow for a Claude Code plugin: bumps every manifest, builds, tags, creates a GitHub release, generates a changelog and publishes to npm.
99k GitHub stars~1.7k tokensUpdated today
DevelopmentAuto-check: warnings

Questions about Release

What does Release do?

Plugin release process for MAG Claude Plugins marketplace. An agent skill from MadAppGang/claude-code. Release is an agent skill from MadAppGang/claude-code. Plugin release process for MAG Claude Plugins marketplace.

When should I use Release?

Release fits situations like: releasing new plugin versions; troubleshooting update issues.

How do I install Release in Claude Code?

Run `npx skills add MadAppGang/claude-code --skill release -a claude-code`. Or copy the skill folder (skills/release in MadAppGang/claude-code) 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 MadAppGang/claude-code --skill release -a codex`. Or copy the skill folder (skills/release in MadAppGang/claude-code) 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 MadAppGang/claude-code --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).

Does Release access the network?

SKILL.md contains no URLs. Its commands use git, 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 1.2k tokens (SKILL.md is roughly 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?

Skills that share tags, products or a category with Release: Hns Moaiadk Dev Reference (modu-ai/moai-adk, 1.2k stars), ClawRouter Release Checklist (BlockRunAI/ClawRouter, 6.6k stars), Release Lithoxyl (mahmoud/lithoxyl, 146 stars) and AnyDrag Release Routine (XueshiQiao/AnyDrag, 227 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

MadAppGang (a GitHub organization) maintains it in MadAppGang/claude-code, which has 285 GitHub stars. The repository holds 69 skills in this directory. The repository was last updated on March 15, 2026.

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

Install Release

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 Process

Critical Understanding

Release Checklist

Step 1: Update Plugin Files

Step 2: Update Documentation

Step 3: ⚠️ CRITICAL - Update Marketplace Catalog

Step 4: Commit and Tag

Step 5: Verify

Common Mistakes

❌ #1: Forgot to update marketplace.json

❌ #2: Wrong git tag format

❌ #3: Inconsistent versions

Version Numbering

Quick Reference

Example Release

Troubleshooting

Files

Compare with similar skills

Similar skills

More from MadAppGang/claude-code

Related

Questions about Release