pipeline-status skillA
pipeline-status is agent-read markdown (skill) from eltmon/overdeck: Cross-room visual status board for every active issue moving through the Overdeck pipeline. One row per issue, one column per phase (agent → review → test → verify → merge → ready), with a checkmark or X in each cell. Designed to be readable from across the room while agents work autonomously. Surface this BEFORE the verbose pan-status / agent-status output whenever the user asks "where are we?" or wants a status overview..
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
# pipeline-status — Cross-Room Visual Status Board ## What this skill does Produces a single dense table for every issue returned by the authoritative pipeline-membership read door (plus active planning sessions), with one column per workflow phase. This includes exception-queue drift such as `zombie_pr` and `post_merge_limbo`, even when tracker or review-status state is stale. This is the **first thing** to show when the user asks for status. Anything more detailed (`pan status`, `agent-status`) goes underneath. ## Output format ``` ISSUE BUCKET TITLE MODEL AGENT REVIEW TEST VERIFY MERGE READY ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── PAN-1028 in_flight TTS: first speech utterance gets clipped kimi-k2.6 ✓ · · - · · PAN-945 post_merge_limbo Planning artifact path mismatch gpt-5.4 · · · · ✓* · …
Read the whole file at its exact version.
How to install
mdr add eltmon/overdeck/pipeline-status@git:20260726.b3c9fa5mdr add eltmon/overdeck/pipeline-status@sha256:12c6585715efe1fcPin 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_4ojfvaff2cn5dn4f)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260726.b3c9fa5 latest | 2026-07-26 | b3c9fa5 | 11,892 B | A | view · diff |
| git:20260719.df80540 | 2026-07-19 | df80540 | 11,344 B | A | view · diff |
| git:20260717.44567f2 | 2026-07-17 | 44567f2 | 11,344 B | A | view · diff |
| git:20260618.e501626 | 2026-06-18 | e501626 | 10,342 B | A | view · diff |
| git:20260618.ccb1e75 | 2026-06-18 | ccb1e75 | 10,352 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 (11892 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_4ojfvaff2cn5dn4f GET https://markdownregistry.com/api/v1/resolve?ref=eltmon/overdeck/pipeline-status GET https://markdownregistry.com/api/v1/blob/12c6585715efe1fc1dffb2f6afdf2ee92c0dac84aabe178ad08c2d0d41898ca9
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.