upgrade-express SKILL.md skillA
upgrade-express from phaedra-solutions/cursor-rules is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add phaedra-solutions/cursor-rules/upgrade-express@git:20261029.f67468cPins git:20261029.f67468c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- phaedra-solutions/cursor-rules
- Path
skills/upgrade-express/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261029.f67468c, committed Oct 29, 2026
- Size
- 5,696 bytes
- Repository stars
- 4
- License
- MIT
Upgrade an Express 4 app to Express 5 with the official codemods from the codemod.com registry (@expressjs/v5-migration-recipe), then fix what codemods can't - path-to-regexp v8 route syntax, the simple query parser and read-only req.query, req.body undefined without a parser, async error handling, express.static dotfiles - and verify with tests and a smoke test. Use when asked to upgrade Express, or when the installed express is 4.x and legacy/express-4 applies.
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
# Upgrade Express 4 → 5 ## When to use - The user asks to upgrade Express, or to move off Express 4 (in maintenance since 1 Apr 2025; EOL no sooner than 1 Oct 2026). - `legacy/express-4` applies and the user agrees to upgrade. For a patch within 4.x, follow Safe maintenance in `legacy/express-4` instead. ## Before you start - Read `express`, its middleware (`body-parser`, `cors`, `helmet`, `express-session`, `multer`, `passport`, routers, error wrappers) and Node from the lockfile and config. Express 5 needs Node ≥ 18; move to a supported LTS first if needed (`upgrade-node`). - The working tree must be clean; work on a branch (`chore/express-5`). - Ask the user: - whether codemods may edit files (they rewrite code; run them on a clean tree so the diff is reviewable); - whether network installs are approved (`core/supply-chain` cooldown applies); - which routes are business-critical, for the smoke test. - Note: `@expressjs/codemod` on npm is deprecated; the official codemods now run through the `codemod` CLI from the codemod.com registry. ## Steps …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_jzpvxtv7gtldhwto/8f9698062c6d45accc41889005195d381d376f9f8aeef653ab6a6fe4570ed798.json
Then /plugin install upgrade-express@markdownregistry-jzpvxtv7gtldhwto in Claude Code. It installs git:20261029.f67468c, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add phaedra-solutions/cursor-rules/upgrade-express@sha256:8f9698062c6d45acThe line at the top of this page pins the label git:20261029.f67468c, 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_jzpvxtv7gtldhwto)
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 phaedra-solutions/cursor-rules/upgrade-express 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 upgrade-express from somewhere else? Ask it: where did my upgrade-express 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 1 version of this file, committed on Oct 29, 2026.
Watch this file (sign in, one email per new version)
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/upgrade-express/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 (5696 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
phaedra-solutions/cursor-rules · 4 stars · license MIT · pushed 2026-11-02 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_jzpvxtv7gtldhwto GET https://markdownregistry.com/api/v1/resolve?ref=phaedra-solutions/cursor-rules/upgrade-express GET https://markdownregistry.com/api/v1/blob/8f9698062c6d45accc41889005195d381d376f9f8aeef653ab6a6fe4570ed798
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.