triage-backlog SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 4 indexed copies. Same content hash, so the same checks give both the same grade.
triage-backlog from phmatray/tagout is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add phmatray/tagout/triage-backlog@git:20261010.9485205Pins git:20261010.9485205 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- phmatray/tagout
- Path
plugins/tagout/skills/triage-backlog/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261010.9485205, committed Oct 10, 2026
- First version recorded
- Sep 15, 2026
- Size
- 24,151 bytes
- Repository stars
- 4
- License
- MIT
Prune and re-decide an EXISTING GitHub issue backlog: verifies which open issues are already fixed or superseded, clusters the rest by root cause, proposes ONE disposition each and executes only what the owner confirms. ALWAYS reach for this when the user wants to prune, triage, groom, re-decide, or take stock of open issues, or says the queue never shrinks: "triage the backlog", "clean up the open issues", "what should we close?", « fais le tri dans les issues », « le backlog ne descend…
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
# Triage the backlog ## What this does `create-issue` opens work, `implement-issue` builds it, `merge-pr` lands it — and `merge-pr` Step 6 opens more, because landing a PR is when deferred work becomes visible. That is a lifecycle with three inlets and no outlet: every issue that ever leaves the queue leaves through a PR, so the queue can only drain at the speed of implementation, while implementation is itself what fills it. This skill is the outlet. It reads the open backlog, works out which items are still real work, which are duplicates of a job already tracked, which were quietly fixed by something else, and which were **observations that got filed as commitments** — then puts a single proposed disposition per item in front of the owner and executes what they confirm. The doctrine comes from `review-followups`, which has always had this outlet for migration reports: closing by decision is *"a legitimate, documented state, never a silent deletion"* — the precedent being *"not pursued by decision, not by lack of capability"*. This skill applies that same idea to GitHub issues, where until now the only documented way out was to build the thing. ## Autonomy contract …
Read the whole file at its exact version.
How to install
mdr add phmatray/tagout/triage-backlog@sha256:b7db8ac5e4614152The line at the top of this page pins the label git:20261010.9485205, 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_7vazi24cawsmdabv)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 15, 2026 and Oct 10, 2026, about one every 25 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261010.9485205 latest | 2026-10-10 | 9485205 | 24,151 B | A | view · diff |
| git:20260915.96b4731 | 2026-09-15 | 96b4731 | 24,159 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 (24151 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
phmatray/tagout · 4 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7vazi24cawsmdabv GET https://markdownregistry.com/api/v1/resolve?ref=phmatray/tagout/triage-backlog GET https://markdownregistry.com/api/v1/blob/b7db8ac5e4614152d1ff9843ef344fbb30d5a88ed4e062e5c4790081d395851c
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.