release-verification SKILL.md skillA
release-verification from nahid-sparktales/agent-dispatcher is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nahid-sparktales/agent-dispatcher/release-verification@git:20260919.a0d4f55Pins git:20260919.a0d4f55 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nahid-sparktales/agent-dispatcher
- Path
skills/devops/release-verification/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260919.a0d4f55, committed Sep 19, 2026
- Size
- 7,161 bytes
- Repository stars
- 58
- License
- MIT
Prove a deployment is healthy rather than merely finished — the revision actually serving asked of the running system, every instance moved, smoke paths walked against the real environment, error rate and latency compared to a pre-deploy baseline. Use after any deploy to a shared environment, before a release is called good, or when checking someone else's claim that it went fine. Not for planning the rollout (deployment) or executing a revert (rollback); it never accepts a green pipeline, a…
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
# Release verification "The deploy finished" is a fact about a pipeline. It says nothing about which revision is serving, whether all of it is serving, or whether the thing serving works. Those are three separate questions and this procedure answers them in that order. ## When this fires A deploy has completed to any shared environment and someone is about to call the release good — your deploy or somebody else's. It fires again after every rollback, hotfix and re-run. It does not fire for a build, and it is not a substitute for tests. ## Procedure 1. **Write down what healthy means before you look.** Which signals, what threshold, over what window, compared to what baseline. Deciding after seeing the numbers is how a bad release gets talked into being fine. 2. **Capture the pre-deploy baseline**, or declare it missing. Error rate, latency at the percentile that matters, throughput, saturation — from before the change. Without it you can report absolute numbers but you cannot say the release did not make anything worse. Say that in those words. 3. **Ask the running system which revision it is serving.** A version or build-info surface the …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/release-verification@sha256:25d9bb3e9d3d8242The line at the top of this page pins the label git:20260919.a0d4f55, 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_zzusto2eihkfzy7m)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 19, 2026.
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 (7161 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
nahid-sparktales/agent-dispatcher · 58 stars · license MIT · pushed 2026-10-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zzusto2eihkfzy7m GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/release-verification GET https://markdownregistry.com/api/v1/blob/25d9bb3e9d3d8242ff7f9b427493427a719668438693f7f34f199d7d4bcd6a70
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 nahid-sparktales/agent-dispatcher
Every file in nahid-sparktales/agent-dispatcher