workflow-ship-and-observe SKILL.md skillA
workflow-ship-and-observe from kensaurus/cursor-kenji is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kensaurus/cursor-kenji/workflow-ship-and-observe@git:20260923.68c095ePins git:20260923.68c095e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kensaurus/cursor-kenji
- Path
skills/workflow-ship-and-observe/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260923.68c095e, committed Sep 23, 2026
- First version recorded
- Jul 21, 2026
- Size
- 7,583 bytes
- Repository stars
- 9
- License
- MIT
Take merged, green code to a verified, monitored production release. Use when "ship it", "deploy to production", "release this", "go live", "roll this out", "promote to prod", or "cut a release" for a running app (npm packages → deploy-npm).
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
# workflow-ship-and-observe — Release, Verify, Observe, Roll Back **Degree of freedom: MIXED.** Rollback-vs-hotfix `[HIGH freedom]`; pin target/SHA, prove revision, observe window `[LOW freedom — run exactly]`. Shipping is not merging. A release is done only when the **intended revision is live on the confirmed target, production smoke checks pass, and a defined monitoring window elapses without crossing rollback thresholds** — or a rollback/hotfix has been executed. > **Prove the deployed revision, then watch it.** A 200 from a URL is not proof > that your code is live, and "it deployed" is not proof that it is healthy. **Before any browser action, read `protocol-browser-anti-stall`.** ## How to reason 1. **Pin** — SHA, environment, mechanism, rollback, signals 2. **Ship** — pipeline deploy; backend deps first 3. **Prove** — live revision equals SHA; smoke on critical flows 4. **Watch** — window elapsed under thresholds, or roll back ## Worked example > **Pin:** `a1b2c3d` on Vercel production; rollback = previous promotion; Sentry + 5xx threshold set. > **Ship:** migrations applied; `vercel deploy --prod` succeeded. …
Read the whole file at its exact version.
How to install
mdr add kensaurus/cursor-kenji/workflow-ship-and-observe@sha256:26090570a7445ba7The line at the top of this page pins the label git:20260923.68c095e, 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_l6ic45wefov3cy7t)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 21, 2026 and Sep 23, 2026, about one every 16 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260923.68c095e latest | 2026-09-23 | 68c095e | 7,583 B | A | view · diff |
| git:20260923.cf348bd | 2026-09-23 | cf348bd | 7,651 B | A | view · diff |
| git:20260821.2a41031 | 2026-08-21 | 2a41031 | 7,502 B | A | view · diff |
| git:20260817.5b93a21 | 2026-08-17 | 5b93a21 | 6,166 B | A | view · diff |
| git:20260721.36a3086 | 2026-07-21 | 36a3086 | 6,561 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 (7583 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
kensaurus/cursor-kenji · 9 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_l6ic45wefov3cy7t GET https://markdownregistry.com/api/v1/resolve?ref=kensaurus/cursor-kenji/workflow-ship-and-observe GET https://markdownregistry.com/api/v1/blob/26090570a7445ba7abaadcaef36ebce1f18995fcc5dab1b101eb25b4d98c971a
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.