release SKILL.md skillA

release from vibemaestro/vibemaestro-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add vibemaestro/vibemaestro-kit/release@git:20261113.9661a88

Pins git:20261113.9661a88 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
vibemaestro/vibemaestro-kit
Path
plugins/vibemaestro-sdlc/skills/release/SKILL.md
Versions recorded
4
Latest version
git:20261113.9661a88, committed Nov 13, 2026
First version recorded
Oct 22, 2026
Size
10,223 bytes
Repository stars
4
License
Apache-2.0

Use when: in a repo that publishes plugins from an export (it has .changes/), a plan's release row is due (a public release of the repository: a feature group closes and its version is shipped), or a defect in the public plugin needs a hotfix before the next release — cut the release or hotfix PR with scripts/release.py (plan, cut, check), open it through ship, and after it merges move the branch release to it, then publish it your own way. Not for an ordinary PR: that one adds a .changes/…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# release — cut a release or a hotfix of a plugin marketplace repo

A version exists only as a public release:
the source repository carries none in a manifest or the marketplace (the export writes it), and a plugin's version is the first `## X.Y.Z` heading of
its `CHANGELOG.md` (the first public release is 0.1.0). Such a heading appears in two kinds of PR only: a **release PR**, run by a
feature group's release row, ships every pending change file (`.changes/*.md`) from main; a **hotfix PR** into the branch
`release` ships one patch that users of the public plugin need before the next release. `scripts/release.py` writes both, and
its `check` (run by CI) is red for anything else, so do not write a version, a `CHANGELOG.md` heading, a `Released together:`
line or a `Frozen at` by hand (check is red when a PR changes the `Released together:` line of a section already on the base),
and never write a version into a `plugin.json`: the public export does that.

Condition: the repo has `.changes/README.md` on main and a branch `release` on its remote (the owner creates `release` once;
until then a release can be cut and merged, but `release` cannot move).
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ospqaji2eqwn5nqb/f3af37b2d03c94ef035efb3b844b4b818f8611c1ddcc808d5a3c8e33c97e89a8.json

Then /plugin install release@markdownregistry-ospqaji2eqwn5nqb in Claude Code. It installs git:20261113.9661a88, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add vibemaestro/vibemaestro-kit/release@sha256:f3af37b2d03c94ef

The line at the top of this page pins the label git:20261113.9661a88, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_ospqaji2eqwn5nqb.svg)](https://markdownregistry.com/a/art_ospqaji2eqwn5nqb)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in vibemaestro/vibemaestro-kit/release since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of release from somewhere else? Ask it: where did my release come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 4 versions of this file, between Oct 22, 2026 and Nov 13, 2026, about one every 7 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261113.9661a88 latest2026-11-13 9661a88 10,223 BA view · diff
git:20261103.f4a254c2026-11-03 f4a254c 8,709 BA view · diff
git:20261029.d5142f72026-10-29 d5142f7 7,702 BA view · diff
git:20261022.867b0e02026-10-22 867b0e0 5,586 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (10223 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

vibemaestro/vibemaestro-kit · 4 stars · license Apache-2.0 · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_ospqaji2eqwn5nqb
GET https://markdownregistry.com/api/v1/resolve?ref=vibemaestro/vibemaestro-kit/release
GET https://markdownregistry.com/api/v1/blob/f3af37b2d03c94ef035efb3b844b4b818f8611c1ddcc808d5a3c8e33c97e89a8

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from vibemaestro/vibemaestro-kit

CLAUDE.md CLAUDE.md file
vibemaestro/vibemaestro-kit · CLAUDE.md
git:20261103.f4a254c · audit A · 4 stars
brain SKILL.md skill
vibemaestro/vibemaestro-kit · plugins/vibemaestro-brain/skills/brain/SKILL.md · Use when: a long-running session must keep a goal, a decision, a delegation window, the focus, what the owner asked…
git:20261115.f7fadb6 · audit A · 4 stars
matrix SKILL.md skill
vibemaestro/vibemaestro-kit · plugins/vibemaestro-brain/skills/matrix/SKILL.md · Print the Brain Matrix: what vibemaestro-brain holds in each cell (Know/Do × hot/warm/cold) and what it did in this…
git:20261022.867b0e0 · audit A · 4 stars
batonrun SKILL.md skill
vibemaestro/vibemaestro-kit · plugins/vibemaestro-sdlc/skills/batonrun/SKILL.md · Use when: writing or editing a baton script, for a write outside the session (GitHub, a registry, the user's plugin…
git:20261113.9661a88 · audit A · 4 stars
bootstrap SKILL.md skill
vibemaestro/vibemaestro-kit · plugins/vibemaestro-sdlc/skills/bootstrap/SKILL.md · Use when: a session starts on a new or moved machine, there is no baton launcher yet, or SessionStart says the baton…
git:20261103.f4a254c · audit A · 4 stars
brainstorm SKILL.md skill
vibemaestro/vibemaestro-kit · plugins/vibemaestro-sdlc/skills/brainstorm/SKILL.md · Use when: the person gives a request in an app repo that is still vague or needs a direction chosen before the spec is…
git:20261115.f7fadb6 · audit A · 4 stars
coordinator-bootstrap SKILL.md skill
vibemaestro/vibemaestro-kit · plugins/vibemaestro-sdlc/skills/coordinator-bootstrap/SKILL.md · Use when: someone asks for coordinator-bootstrap by name. It is the old name of the skill bootstrap and leaves in the…
git:20261103.f4a254c · audit A · 4 stars
history SKILL.md skill
vibemaestro/vibemaestro-kit · plugins/vibemaestro-sdlc/skills/history/SKILL.md · Use when: in the kit's everyday mode the person asks what was saved or wants an earlier state of their work, in any…
git:20261115.f7fadb6 · audit A · 4 stars
init-kb SKILL.md skill
vibemaestro/vibemaestro-kit · plugins/vibemaestro-sdlc/skills/init-kb/SKILL.md · Use when: a repo app has no kb/ or lacks one of its directories, or a repo adopts the plugin and needs its per-repo…
git:20261115.f7fadb6 · audit A · 4 stars
install-gates SKILL.md skill
vibemaestro/vibemaestro-kit · plugins/vibemaestro-sdlc/skills/install-gates/SKILL.md · Use when: a repo wants the process gates behind the plugin's rules - commit discipline, sensitive-info scan of PR text…
git:20261113.9661a88 · audit A · 4 stars
intake SKILL.md skill
vibemaestro/vibemaestro-kit · plugins/vibemaestro-sdlc/skills/intake/SKILL.md · Use when: the person gives a new piece of work in an app repo and it must become an intent in the kb/ of this very repo…
git:20261115.f7fadb6 · audit A · 4 stars
local-parallel SKILL.md skill
vibemaestro/vibemaestro-kit · plugins/vibemaestro-sdlc/skills/local-parallel/SKILL.md · Use when: on one machine (no sandbox, only vibemaestro-sdlc and vibemaestro-brain), the person wants several tasks done…
git:20261113.9661a88 · audit A · 4 stars

Every file in vibemaestro/vibemaestro-kit

Other files named release

release SKILL.md skill
thedotmack/claude-mem · plugin/skills/release/SKILL.md · Fully automate a release with version-bump and childhood.
git:20261017.ca1b99c · audit A · 117,202 stars
release SKILL.md skill
paperclipai/paperclip · .agents/skills/release/SKILL.md · Coordinate a full Paperclip release across engineering verification, npm, GitHub, smoke testing, and announcement…
git:20260710.5c85ae6 · audit A · 114,009 stars
release SKILL.md skill
amruthpillai/reactive-resume · .agents/skills/release/SKILL.md · Use when releasing a new version of Reactive Resume — bumping the version, writing the changelog entry, creating the…
git:20261104.22aa433 · audit A · 45,844 stars
release SKILL.md skill
reactive-resume/app · .agents/skills/release/SKILL.md · Use when releasing a new version of Reactive Resume — bumping the version, writing the changelog entry, creating the…
git:20261104.22aa433 · audit A · 45,759 stars
release SKILL.md skill
reactive-resume/reactive-resume · .agents/skills/release/SKILL.md · Use when releasing a new version of Reactive Resume — bumping the version, writing the changelog entry, creating the…
git:20261104.22aa433 · audit A · 45,757 stars
release SKILL.md skill
yeachan-heo/oh-my-claudecode · skills/release/SKILL.md · Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASE_RULE.md, then guides the release
git:20260411.c3c4851 · audit A · 40,827 stars
release SKILL.md skill
blockrunai/clawrouter · skills/release/SKILL.md · Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm…
git:20260524.3cc7323 · audit A · 6,665 stars
release SKILL.md skill
atmosphere/atmosphere · .claude/skills/release/SKILL.md · Cut an Atmosphere release end to end — the only path to release-4x.yml. Use whenever a release, a version cut, "ship…
git:20261019.ff4f7b0 · audit A · 3,834 stars

Browse by kind, by grade A, or by owner.