pan-rollout SKILL.md skillA
pan-rollout from eltmon/overdeck is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add eltmon/overdeck/pan-rollout@git:20260924.0eed7d5Pins git:20260924.0eed7d5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- eltmon/overdeck
- Path
sync-sources/skills/pan-rollout/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260924.0eed7d5, committed Sep 24, 2026
- First version recorded
- Jul 12, 2026
- Size
- 2,031 bytes
- Repository stars
- 35
- License
- MIT
pan rollout <status|retry> <id> — inspect or re-run post-merge release coordination.
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
# pan rollout
Post-merge release coordination for projects with a `release:` config section.
This is distinct from `pan release`, which publishes npm stable/canary packages.
```bash
pan rollout status <issue-id>
pan rollout retry <issue-id>
```
## What It Does
`pan rollout status` prints the release set's overall `status` (`pending`,
`releasing`, `passed`, `failed`, `partial`, `rolled_back`, `skipped`) and each
configured component's key, release order, and current status.
`pan rollout retry` re-runs the release engine for the issue (health checks,
version checks, smoke tests, rollback if configured) and prints the resulting
status.
## When to Use
- After a merge, to see whether the coordinated release is in progress, passed,
failed, partial, or rolled back.
- To manually retry a release after fixing a failed component or external
deploy.
## Release Configuration
Projects opt in via `projects.yaml`:
```yaml
projects:
- key: myn
release:
components:
api:
provider: kubernetes
trigger: auto
health_url: https://api.myn.example.com/health
version_check: scripts/check-version.sh api
…Read the whole file at its exact version.
How to install
mdr add eltmon/overdeck/pan-rollout@sha256:41fcc90ac6c5eae3The line at the top of this page pins the label git:20260924.0eed7d5, 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_2f4adwne2fdb4xer)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 12, 2026 and Sep 24, 2026, about one every 74 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260924.0eed7d5 latest | 2026-09-24 | 0eed7d5 | 2,031 B | A | view · diff |
| git:20260712.90bc899 | 2026-07-12 | 90bc899 | 1,942 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 (2031 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
eltmon/overdeck · 35 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2f4adwne2fdb4xer GET https://markdownregistry.com/api/v1/resolve?ref=eltmon/overdeck/pan-rollout GET https://markdownregistry.com/api/v1/blob/41fcc90ac6c5eae3644754e1155944e2007c8072acb1e9845b53edb9058b15d4
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.