deploy-verify SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
deploy-verify from kensaurus/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kensaurus/skills/deploy-verify@git:20260923.938ff43Pins git:20260923.938ff43 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kensaurus/skills
- Path
skills/deploy-verify/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260923.938ff43, committed Sep 23, 2026
- First version recorded
- Aug 20, 2026
- Size
- 15,576 bytes
- Repository stars
- 9
- License
- MIT
Post-deploy smoke test across browser, Sentry, Supabase, Langfuse, and the public web. Use when "verify deploy", "smoke test production", "post-release check", or "ship or rollback". Deploy plus watch → workflow-ship-and-observe.
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
# Post-Deploy Verification **Degree of freedom: MIXED.** Verdict and MONITOR escalation `[HIGH freedom]`; probe sequences and the report table `[LOW freedom — run exactly]`. Automated post-deploy health check across all services. Run after every deploy to catch regressions before users do. Works with **any project** — auto-detects configuration. ## How to reason 1. **Observe** — what did each probe actually return (counts, logs, screenshots)? 2. **Interpret** — new-since-deploy vs pre-existing; skip-missing vs real fail 3. **Classify** — PASS / MONITOR / FAIL per phase 4. **Severity** — auth/data-loss/5xx on the main path outranks a Langfuse quiet window ## Worked example > **Observe:** home loads; Sentry shows 12 new `TypeError` on `/checkout`; Supabase API 200s. > **Interpret:** checkout is a critical path; errors started with this release. > **Classify:** Sentry FAIL, smoke FAIL on checkout, DB PASS. > **Verdict:** ROLLBACK — main money path is 5xx, not a MONITOR item. ## Self-critique before reporting - **Evidence** — every row cites a probe result, not "looks fine" - **Binary verdict** — SHIP / MONITOR / HOTFIX / ROLLBACK with a next action …
Read the whole file at its exact version.
How to install
mdr add kensaurus/skills/deploy-verify@sha256:53094c94448a9e6dThe line at the top of this page pins the label git:20260923.938ff43, 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_m4asiuffesk3tafc)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 20, 2026 and Sep 23, 2026, about one every 8 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260923.938ff43 latest | 2026-09-23 | 938ff43 | 15,576 B | A | view · diff |
| git:20260923.68c095e | 2026-09-23 | 68c095e | 13,716 B | A | view · diff |
| git:20260923.cf348bd | 2026-09-23 | cf348bd | 13,760 B | A | view · diff |
| git:20260821.2a41031 | 2026-08-21 | 2a41031 | 13,659 B | A | view · diff |
| git:20260820.950107c | 2026-08-20 | 950107c | 12,407 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 (15576 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/skills · 9 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_m4asiuffesk3tafc GET https://markdownregistry.com/api/v1/resolve?ref=kensaurus/skills/deploy-verify GET https://markdownregistry.com/api/v1/blob/53094c94448a9e6db57b56192d50611277f45e7362d6faf834b3c06d130df10c
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 kensaurus/skills
Every file in kensaurus/skills