release skillA
release is agent-read markdown (skill) from muthuishere/toolnexus: Cut and verify a toolnexus release across all seven registries, with the guardrails that a green CI run does not give you. Use whenever the user says publish, release, ship it, cut a release, bump the version, or asks whether a release actually landed. Also use to re-publish a single failed registry leg..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Releasing toolnexus Publishing is **outward-facing and irreversible**: a version number can never be reused on npm, PyPI, NuGet, Maven Central, Hex or Clojars. This skill exists because the obvious signals lie in both directions — a green workflow can ship nothing, and a red workflow can be a complete success. ## The two rules that override intuition **1. A green run is not evidence a package landed.** ADR-0012 exists because NuGet and Maven have reported success without publishing. **Always verify from outside, as a consumer would** (step 6). **2. A red run is not evidence of failure.** Re-dispatching a completed release makes the already-published legs refuse a duplicate — npm `cannot publish over the previously published versions`, Clojars `403 redeploying non-snapshots is not allowed`. That is immutability working. Read the **job list**, not the conclusion. ## Never do these - **Never publish unless the owner asked in this conversation.** "Is it ready?" is a question, not authorization. - **Never release unmerged code.** The release is cut from `main` after the PR merges. - **Never bump one port "to unblock".** `preflight` refuses it, and that refusal is the point. …
Read the whole file at its exact version.
How to install
mdr add muthuishere/toolnexus/release@v1.0mdr add muthuishere/toolnexus/release@sha256:62881083fc59af3aPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ao7gcjzgqvyjphtj)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0 latest | 2026-08-17 | 7927ade | 8,096 B | A | view · diff |
| v1.0 | 2026-08-16 | 22f4bf9 | 7,160 B | A | view · diff |
| v1.0 | 2026-08-16 | 845c518 | 6,373 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 (8096 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
muthuishere/toolnexus · 5 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ao7gcjzgqvyjphtj GET https://markdownregistry.com/api/v1/resolve?ref=muthuishere/toolnexus/release GET https://markdownregistry.com/api/v1/blob/62881083fc59af3a2cb92580b882aa53339fea5f05cff3a1656db3411641a403
Your agent 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.
More from muthuishere/toolnexus
Every file in muthuishere/toolnexus