publish-release SKILL.md skillA
publish-release from molefrog/moi is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add molefrog/moi/publish-release@git:20261020.be4a16cPins git:20261020.be4a16c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- molefrog/moi
- Path
.agents/skills/publish-release/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261020.be4a16c, committed Oct 20, 2026
- First version recorded
- Jul 28, 2026
- Size
- 10,754 bytes
- Repository stars
- 191
- License
- a license file GitHub does not identify
Release moi-computer to npm — verify locally, hand off to the gated GitHub Actions workflow, then verify the published package. Defaults to a `next` preview; pass `stable` for a `latest` release. Use when the user asks to publish, release, ship a version, or cut a dev preview.
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
# Publish a moi-computer release `publish-release` — preview under the `next` dist-tag. `publish-release stable` — real release under `latest`, with a GitHub release. **npm publishing happens only in GitHub Actions.** `.github/workflows/release.yml` authenticates via npm trusted publishing (OIDC), gated behind the `release` environment's required reviewer. There is no npm token anywhere and no npm session to reuse. - Never run `npm publish` yourself. It will fail, and it is not the path. - Never run `npm login` or ask the user for an OTP. - A tag push is what starts a release. Tags are awkward to retract — earn the push with §2 first. Two human checkpoints: the user confirms the version before the push, and approves the deployment in GitHub after it. Everything else runs unattended. ## 0. Preflight 1. `git status` — clean tree, on `main`. Stop and ask if not. 2. `git fetch && git status -sb` — up to date with `origin/main`. 3. `git log origin/main..HEAD --oneline` — if anything is unpushed, show it and confirm it should ship. 4. Record whether a dev `bun link` is active, because §8 branches on it: ```sh readlink ~/.bun/install/global/node_modules/moi-computer ``` …
Read the whole file at its exact version.
How to install
mdr add molefrog/moi/publish-release@sha256:afa24a1eea6deca8The line at the top of this page pins the label git:20261020.be4a16c, 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_w7hlgl5od72zfj2k)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jul 28, 2026 and Oct 20, 2026, about one every 17 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.be4a16c latest | 2026-10-20 | be4a16c | 10,754 B | A | view · diff |
| git:20261019.2345208 | 2026-10-19 | 2345208 | 10,052 B | A | view · diff |
| git:20260818.74d3548 | 2026-08-18 | 74d3548 | 10,052 B | A | view · diff |
| git:20260728.365520a | 2026-07-28 | 365520a | 9,962 B | A | view · diff |
| git:20260728.fbe3a34 | 2026-07-28 | fbe3a34 | 7,451 B | A | view · diff |
| git:20260728.c29699a | 2026-07-28 | c29699a | 6,962 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 (10754 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
molefrog/moi · 191 stars · license a license file GitHub does not identify · pushed 2026-10-29 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_w7hlgl5od72zfj2k GET https://markdownregistry.com/api/v1/resolve?ref=molefrog/moi/publish-release GET https://markdownregistry.com/api/v1/blob/afa24a1eea6deca8d02b20287bc00e79a7aeaca2f837c3ef88c7c264b055e6dc
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.