rollout-readiness-review SKILL.md skillA
rollout-readiness-review from yarlson/yarstack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yarlson/yarstack/rollout-readiness-review@git:20261017.2f2e03bPins git:20261017.2f2e03b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yarlson/yarstack
- Path
plugins/yarstack/skills/rollout-readiness-review/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261017.2f2e03b, committed Oct 17, 2026
- First version recorded
- Jul 18, 2026
- Size
- 2,157 bytes
- Repository stars
- 3
- License
- MIT
Review cross-cutting operational readiness after implementation and before deployment. Use when a concrete change may alter runtime prerequisites, failure visibility, deployment order, rollback, recovery, or production failure modes.
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
# Rollout Readiness Review Assess repository-local deployment readiness without performing or implying a live rollout. ## Workflow 1. Confirm the concrete change, target environment class, available evidence, and whether the task is repository review or explicitly authorized live verification. 2. Identify the runtime delta, required configuration and permissions, startup and shutdown behavior, background work, migration order, and partial-state risk. 3. Determine how failures appear through existing signals and how an operator verifies success. 4. Check the mixed-version window: during a deploy, old and new versions run side by side, so each must work with the data, messages, and configuration that the other writes. Check that the previous version can still run against the state the new version leaves; if it cannot, rollback is not available, and the result must say so. 5. Define the smallest safe deployment order, rollback conditions, and recovery path. 6. Delegate IaC blast radius to `infra-review`, trust-boundary risk to `security-review`, dependency provenance to `dependency-review`, documentation drift to `docs-drift-review`, and verification gaps to `test-gap-review`. …
Read the whole file at its exact version.
How to install
mdr add yarlson/yarstack/rollout-readiness-review@sha256:8fb27923439288a3The line at the top of this page pins the label git:20261017.2f2e03b, 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_xjtxg4exqt5lg3df)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 18, 2026 and Oct 17, 2026, about one every 46 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.2f2e03b latest | 2026-10-17 | 2f2e03b | 2,157 B | A | view · diff |
| git:20260718.42bcc8e | 2026-07-18 | 42bcc8e | 1,840 B | A | view · diff |
| git:20260718.6a34e4d | 2026-07-18 | 6a34e4d | 1,368 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 (2157 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
yarlson/yarstack · 3 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xjtxg4exqt5lg3df GET https://markdownregistry.com/api/v1/resolve?ref=yarlson/yarstack/rollout-readiness-review GET https://markdownregistry.com/api/v1/blob/8fb27923439288a353b79adce3e9e3c65ee3e562b33549b7d3a82512a386b60f
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.