publish-npm-version SKILL.md skillA
publish-npm-version from prisma/orm is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add prisma/orm/publish-npm-version@git:20261006.b32ec30Pins git:20261006.b32ec30 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- prisma/orm
- Path
skills-contrib/publish-npm-version/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261006.b32ec30, committed Oct 6, 2026
- First version recorded
- Aug 31, 2026
- Size
- 16,091 bytes
- Repository stars
- 47,691
- License
- Apache-2.0
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to <next-version>". When the maintainer merges the PR, the `Publish to npm` workflow runs automatically and ships the new version to npm under the dist-tag its shape implies (`latest`; RC releases get a pre-release GitHub Release), plus a matching GitHub Release. Also prepares the matching…
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 next npm version ## Audience Maintainers of Prisma 8 who have permission to push branches and open PRs in the repository. The skill is invoked locally by the maintainer; it does **not** run as a GitHub Action. Running locally is what makes the resulting PR trigger CI normally — PRs opened by a workflow's `GITHUB_TOKEN` do not, which defeats the point of cutting a reviewable release. ## Background reading Read [`docs/oss/versioning.md`](../../docs/oss/versioning.md) before running this skill. It covers: - The source-of-truth model (root `package.json` `version`). - The lockstep guarantee (every workspace package matches the root). - The v8 RC line (`8.0.0-rc.N`, with `latest` tracking the newest RC or stable release). - The dist-tag convention (`latest` / `dev` / `beta`). - The full release procedure (this skill covers steps 1-2 of 3; merging the PR is the publish trigger — there is no separate dispatch step). - The emergency-patch path (this skill does **not** handle patches). …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_scpj2fbz5qfclbmb/a1119c1fc1e4cfa6128af870bdb62618e4e2c81b542f0adbebf7fdc0f2c25447.json
Then /plugin install publish-npm-version@markdownregistry-scpj2fbz5qfclbmb in Claude Code. It installs git:20261006.b32ec30, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add prisma/orm/publish-npm-version@sha256:a1119c1fc1e4cfa6The line at the top of this page pins the label git:20261006.b32ec30, 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_scpj2fbz5qfclbmb)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in prisma/orm/publish-npm-version 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 publish-npm-version from somewhere else? Ask it: where did my publish-npm-version 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 5 versions of this file, between Aug 31, 2026 and Oct 6, 2026, about one every 9 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261006.b32ec30 latest | 2026-10-06 | b32ec30 | 16,091 B | A | view · diff |
| git:20260916.f3574a3 | 2026-09-16 | f3574a3 | 15,866 B | A | view · diff |
| git:20260914.9cd4175 | 2026-09-14 | 9cd4175 | 13,123 B | A | view · diff |
| git:20260913.1e8b6a6 | 2026-09-13 | 1e8b6a6 | 13,168 B | A | view · diff |
| git:20260831.aefbf79 | 2026-08-31 | aefbf79 | 9,229 B | A | view |
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.
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.
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.
Installed this file, say at .claude/skills/publish-npm-version/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
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
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (16091 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
prisma/orm · 47,691 stars · license Apache-2.0 · pushed 2026-11-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_scpj2fbz5qfclbmb GET https://markdownregistry.com/api/v1/resolve?ref=prisma/orm/publish-npm-version GET https://markdownregistry.com/api/v1/blob/a1119c1fc1e4cfa6128af870bdb62618e4e2c81b542f0adbebf7fdc0f2c25447
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.