release SKILL.md skillA
release from gao-xh/multi-agent-protocol is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gao-xh/multi-agent-protocol/release@git:20261028.ea8a704Pins git:20261028.ea8a704 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gao-xh/multi-agent-protocol
- Path
skills/release/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261028.ea8a704, committed Oct 28, 2026
- First version recorded
- Oct 21, 2026
- Size
- 3,536 bytes
- Repository stars
- 4
- License
- MIT
Take the release role of the Multi-Agent Protocol - intake of finished branches, strict verification, deployment, the release record, and, by default, the only role that advances the main branch (a project may name another role for that work in its agent rules file, PROTOCOL.md 2.2). Use when the user says this session releases, or when a release-request needs handling.
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 role
You are the **release** role in a project that follows the Multi-Agent Protocol.
1. Read `${CLAUDE_PLUGIN_ROOT}/PROTOCOL.md` in full, unless the project vendors its own copy (the project's `AGENTS.md` or `CLAUDE.md` says where); then read that copy instead. Section 7 is your procedure; sections 3, 5 and 8 also apply.
2. Read the project's agent rules file: the checks, the release command, the release log, any standing authorizations, and its "Roles and permissions" section (PROTOCOL.md 2.2 defaults otherwise).
3. Run the `coordinate` skill's start-of-session routine with your own line name (`release`, or `release-a`, `release-b` when several release sessions run) and `Role: release` in your status file, so that messages addressed to the role reach you. Handle `release-request` messages in the order they were pushed; when other release sessions exist, claim it (`claim.sh <line> messages/<file>.md`, which uses `msg-<message name>`) before acting on one (PROTOCOL.md 2.1, 5.6).
For each release request, follow PROTOCOL.md section 7 step by step, in order, and do not skip a step silently:
…Read the whole file at its exact version.
How to install
mdr add gao-xh/multi-agent-protocol/release@sha256:ae130fc0f8125419The line at the top of this page pins the label git:20261028.ea8a704, 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.
[](https://markdownregistry.com/a/art_ygo7s7acqben2jt6)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 21, 2026 and Oct 28, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.ea8a704 latest | 2026-10-28 | ea8a704 | 3,536 B | A | view · diff |
| git:20261027.08f7e63 | 2026-10-27 | 08f7e63 | 3,481 B | A | view · diff |
| git:20261022.635bfc8 | 2026-10-22 | 635bfc8 | 2,950 B | A | view · diff |
| git:20261021.f269b09 | 2026-10-21 | f269b09 | 2,859 B | A | view · diff |
| git:20261021.1f34ec0 | 2026-10-21 | 1f34ec0 | 2,586 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3536 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
gao-xh/multi-agent-protocol · 4 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ygo7s7acqben2jt6 GET https://markdownregistry.com/api/v1/resolve?ref=gao-xh/multi-agent-protocol/release GET https://markdownregistry.com/api/v1/blob/ae130fc0f812541942fe8ff32cd40a5f8bd13b2b33ca53bec5bd4aa25c8a0ebe
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 gao-xh/multi-agent-protocol
Every file in gao-xh/multi-agent-protocol