deploy-receipt SKILL.md skillA
deploy-receipt from naimkatiman/continuous-improvement is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add naimkatiman/continuous-improvement/deploy-receipt@git:20260906.fca30a4Pins git:20260906.fca30a4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- naimkatiman/continuous-improvement
- Path
plugins/continuous-improvement/skills/deploy-receipt/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260906.fca30a4, committed Sep 6, 2026
- First version recorded
- May 8, 2026
- Size
- 13,850 bytes
- Repository stars
- 9
- License
- MIT
Enforces Law 4 (Verify Before Reporting) of the 7 Laws of AI Agent Discipline at the deploy seam. A merge into a branch that auto-deploys is not "done" until the deploy provider reports the merged commit SHA running and a healthcheck endpoint returns 200. Companion to the vendored `finishing-a-development-branch` skill — does not replace it, runs after it for projects on Railway, Cloudflare Workers, Vercel, Netlify, Fly.io, or any other auto-deploy target.
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 Receipt — Closing the Merge-to-Production Gap ## Why This Skill Exists Multiple sessions in the operator's recent telemetry ended in a "partially achieved" state with the same shape: PR merged green, branch deleted, agent reports done — and then hours later the operator discovers the deploy provider never picked up the commit, was building from a stale lockfile, or silently rolled back. The merge happened. The deploy did not. `finishing-a-development-branch` (vendored from Obra superpowers in `third-party/superpowers/`) ends at the merge. For repos that do not auto-deploy that is the correct boundary. For repos that DO auto-deploy from `main` (Railway, Cloudflare Workers, Vercel, Netlify, Fly.io, Cloud Run, App Runner, et al.) the merge is only the trigger — the work is not done until the deployed SHA matches the merged HEAD and the application answers a healthcheck. This skill defines the receipt that closes that gap, without modifying the vendored upstream file. ## When to Activate Activate when ALL of the following are true: 1. A merge into the deploy branch (typically `main` or `master`) has just landed …
Read the whole file at its exact version.
How to install
mdr add naimkatiman/continuous-improvement/deploy-receipt@sha256:225b30154aee0ef9The line at the top of this page pins the label git:20260906.fca30a4, 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_jpvn2wjfqkuwav4m)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 8, 2026 and Sep 6, 2026, about one every 30 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260906.fca30a4 latest | 2026-09-06 | fca30a4 | 13,850 B | A | view · diff |
| git:20260710.b8ed97c | 2026-07-10 | b8ed97c | 13,856 B | A | view · diff |
| git:20260517.097d3da | 2026-05-17 | 097d3da | 13,762 B | A | view · diff |
| git:20260517.966ce51 | 2026-05-17 | 966ce51 | 13,402 B | A | view · diff |
| git:20260508.b9594de | 2026-05-08 | b9594de | 13,371 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 (13850 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
naimkatiman/continuous-improvement · 9 stars · license MIT · pushed 2026-09-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jpvn2wjfqkuwav4m GET https://markdownregistry.com/api/v1/resolve?ref=naimkatiman/continuous-improvement/deploy-receipt GET https://markdownregistry.com/api/v1/blob/225b30154aee0ef915eb95571f3d6038a77c292079e5c6cc636d3f9d49951783
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.