pan-release skillA
pan-release is agent-read markdown (skill) from eltmon/overdeck: Overdeck-specific stable vs canary release workflow from main.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Overdeck Release Workflow Use this skill when the user asks how to release Overdeck, whether they should use a `develop` branch, or how stable vs canary publishing works. ## Core policy Overdeck develops directly on `main`. `main` is the active development branch, not the stable channel by itself. A release only happens when someone intentionally cuts and pushes a tag. Do not recommend GitFlow or a long-lived `develop` branch unless the user explicitly asks for a different workflow. ## Release channels ### Stable - Version format: `X.Y.Z` - Tag format: `vX.Y.Z` - npm dist-tag: `latest` - GitHub Release: normal release ### Canary - Version format: `X.Y.Z-canary.N` - Tag format: `vX.Y.Z-canary.N` - npm dist-tag: `canary` - GitHub Release: prerelease ## Preferred operator flow 1. Run: ```bash pan release check ``` 2. Create a stable or canary release: ```bash pan release stable --version 0.7.1 pan release canary --version 0.8.0-canary.1 ``` 3. Push intentionally: ```bash git push origin main git push origin v0.7.1 ``` ## What the CLI does `pan release stable` and `pan release canary`: - validate the version format …
Read the whole file at its exact version.
How to install
mdr add eltmon/overdeck/pan-release@git:20260727.441a01cmdr add eltmon/overdeck/pan-release@sha256:da3d1750df437e77Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_qfc6qmplvbtt2yzf)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260727.441a01c latest | 2026-07-27 | 441a01c | 5,894 B | A | view · diff |
| git:20260727.08ecbfc | 2026-07-27 | 08ecbfc | 5,631 B | A | view · diff |
| git:20260623.69b2ee4 | 2026-06-23 | 69b2ee4 | 3,311 B | A | view · diff |
| git:20260618.80fba74 | 2026-06-18 | 80fba74 | 1,817 B | A | view · diff |
| git:20260522.817c2c7 | 2026-05-22 | 817c2c7 | 1,825 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 (5894 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 · 28 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qfc6qmplvbtt2yzf GET https://markdownregistry.com/api/v1/resolve?ref=eltmon/overdeck/pan-release GET https://markdownregistry.com/api/v1/blob/da3d1750df437e77ed24707698699295499081f6bd995571e4546bf9f127e967
Your agent 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.