record-upgrade-instructions SKILL.md skillB
record-upgrade-instructions 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/record-upgrade-instructions@git:20261118.4188e15Pins git:20261118.4188e15 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- prisma/orm
- Path
skills-contrib/record-upgrade-instructions/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261118.4188e15, committed Nov 18, 2026
- First version recorded
- Oct 6, 2026
- Size
- 14,001 bytes
- Repository stars
- 47,691
- License
- Apache-2.0
Record upgrade instructions alongside a Prisma 8 breaking-change PR, so downstream consumers (applications on the published `@prisma/orm-*` packages and authors of Prisma 8 extensions) can apply the matching code translation automatically via the published upgrade skills. Use when you have refactored framework code and the test suite went red in `examples/`, `packages/3-extensions/` or a target facade, when you fixed those red tests by updating example or extension code, when you are told to…
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
# Record upgrade instructions Contribute an independent fragment on the PR that changes Prisma 8. Release preparation combines fragments into the published app and extension guides; **feature PRs do not edit shared transition guides or choose a release number**. Read the canonical [upgrade instruction lifecycle](../../upgrade-instructions/README.md) for storage, release assembly, and checker modes. ## Detection signals and routing Use this skill when a framework change makes tests red in `examples/`, `packages/3-extensions/` or a target facade (`packages/3-targets/*/9-facade/` or `packages/3-targets/*/*/9-facade/`) and you fix them by updating the example or extension code rather than reverting the framework change. Those edits are the same translation downstream consumers need. | Directory changed by the PR | Fragment audience | Consumers | | --- | --- | --- | | `examples/` | `app` | Public package API, contract files, on-disk migrations | | `packages/3-extensions/`, `packages/3-targets/*/9-facade/` and `packages/3-targets/*/*/9-facade/` | `extension` | Framework SPI and extension authors | | Both | Both, independently | Both audiences | …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_tnbezt4bcuyd2zkk/001d68ffd952c2be3f9d6d825ad444c9faf0cb41950731887d7ddea8f0b5ae3f.json
Then /plugin install record-upgrade-instructions@markdownregistry-tnbezt4bcuyd2zkk in Claude Code. It installs git:20261118.4188e15, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add prisma/orm/record-upgrade-instructions@sha256:001d68ffd952c2beThe line at the top of this page pins the label git:20261118.4188e15, 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_tnbezt4bcuyd2zkk)
3 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/record-upgrade-instructions 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 record-upgrade-instructions from somewhere else? Ask it: where did my record-upgrade-instructions 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 6 versions of this file, between Oct 6, 2026 and Nov 18, 2026, about one every 9 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261118.4188e15 latest | 2026-11-18 | 4188e15 | 14,001 B | B | view · diff |
| git:20261110.2c1274d | 2026-11-10 | 2c1274d | 13,567 B | B | view · diff |
| git:20261110.596348e | 2026-11-10 | 596348e | 13,420 B | B | view · diff |
| git:20261022.6af5425 | 2026-10-22 | 6af5425 | 13,167 B | B | view · diff |
| git:20261006.4412051 | 2026-10-06 | 4412051 | 12,767 B | B | view · diff |
| git:20261006.b32ec30 | 2026-10-06 | b32ec30 | 12,558 B | B | 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/record-upgrade-instructions/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
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14001 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
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_tnbezt4bcuyd2zkk GET https://markdownregistry.com/api/v1/resolve?ref=prisma/orm/record-upgrade-instructions GET https://markdownregistry.com/api/v1/blob/001d68ffd952c2be3f9d6d825ad444c9faf0cb41950731887d7ddea8f0b5ae3f
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.