deploy-checklist SKILL.md skillA
deploy-checklist from mblode/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mblode/agent-skills/deploy-checklist@git:20261110.8400fe5Pins git:20261110.8400fe5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mblode/agent-skills
- Path
skills/agent-skills-creator/evals/fixtures/long-deploy-checklist/base/skills/deploy-checklist/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261110.8400fe5, committed Nov 10, 2026
- Size
- 11,065 bytes
- Repository stars
- 203
- License
- MIT
Walks through deploying the Orchard storefront to staging and production, including pre-deploy checks, the canary, monitoring, and rollback. Use when asked to "deploy", "ship to prod", "run the release", "roll back", or "is it safe to deploy".
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
# Deploy Checklist This skill helps you deploy the Orchard storefront safely. Deployment is one of the most important parts of the software development lifecycle, and doing it well takes care, attention, and good communication. Read this whole document carefully before you begin, and refer back to it whenever you are unsure. A good deployment is a boring deployment. The goal is always to get working software in front of customers without surprising anyone. ## Why deployment discipline matters Deployments are the moment when code changes meet real users. Even a small change can have a large effect, so it is important to be careful and methodical. - A bad deploy can cause downtime, which costs money and damages trust. - A rushed deploy is more likely to contain mistakes. - A well-communicated deploy means that everyone knows what is happening. - A reversible deploy means that mistakes can be fixed quickly. Always remember that it is better to deploy slowly and safely than quickly and dangerously. Take your time. Double-check your work. If something does not look right, stop and think. ## What a deployment is …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_k65u4tvt4mfvokwv/2914ec906c52d380c0e4ca8776120773366554c59dd1d257838bc0183748c01c.json
Then /plugin install deploy-checklist@markdownregistry-k65u4tvt4mfvokwv in Claude Code. It installs git:20261110.8400fe5, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add mblode/agent-skills/deploy-checklist@sha256:2914ec906c52d380The line at the top of this page pins the label git:20261110.8400fe5, 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_k65u4tvt4mfvokwv)
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 mblode/agent-skills/deploy-checklist 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 deploy-checklist from somewhere else? Ask it: where did my deploy-checklist 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 Nov 10, 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/deploy-checklist/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 (11065 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
mblode/agent-skills · 203 stars · license MIT · pushed 2026-11-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_k65u4tvt4mfvokwv GET https://markdownregistry.com/api/v1/resolve?ref=mblode/agent-skills/deploy-checklist GET https://markdownregistry.com/api/v1/blob/2914ec906c52d380c0e4ca8776120773366554c59dd1d257838bc0183748c01c
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.
More from mblode/agent-skills
Every file in mblode/agent-skills