backlog-triage SKILL.md skillA
backlog-triage from rampstackco/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rampstackco/claude-skills/backlog-triage@git:20261116.f6e91d9Pins git:20261116.f6e91d9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rampstackco/claude-skills
- Path
skills/backlog-triage/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261116.f6e91d9, committed Nov 16, 2026
- First version recorded
- Nov 8, 2026
- Size
- 11,857 bytes
- Repository stars
- 1,100
- License
- MIT
Turn an inbox of raw requests (bug reports, feature asks, support escalations, feedback, incident follow-ups) into a ranked, deduplicated backlog where every item at the top meets the definition of ready, with recorded scores, merge links, and a written reason for every park and decline. Use this skill whenever the user wants to triage incoming work, groom or prune a backlog, merge duplicate tickets, score or rank requests, decide what the team works on next, or run a weekly triage session.…
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
# Backlog Triage Turn a pile of raw requests into a short, ranked queue where everything at the top can be pulled today. Tracker-agnostic: works in Jira, Linear, GitHub Issues, or your tracker of choice. --- ## When to use - A pile of bug reports, feature asks, and escalations has no order - The same complaint shows up as five tickets from five people - The team asks "what should we work on next?" and nobody can answer from the backlog - Running the weekly triage session - The backlog has grown past the point anyone reads it - Checking whether the top of the queue is actually ready to pull ## When NOT to use - Writing the ticket itself, fields and all (use `ticket-authoring`) - Sequencing initiatives across quarters (use `roadmap-planning`) - Synthesizing a batch of research interviews (use `discovery-research-synthesis`) - Aggregating feedback channels into themes (use `user-feedback-aggregation`) - Running sprint planning, standups, or retros (use `sprint-operations`) - Writing the test plan for one item already in the queue (use `test-case-authoring`) --- ## Required inputs - The raw items: pasted text, an export, or a tracker query …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_kk6bzijci377v2io/dca28832d451907d2be4ec3023e693c0fb4a19fe6b11da206432528efd2ed2d4.json
Then /plugin install backlog-triage@markdownregistry-kk6bzijci377v2io in Claude Code. It installs git:20261116.f6e91d9, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add rampstackco/claude-skills/backlog-triage@sha256:dca28832d451907dThe line at the top of this page pins the label git:20261116.f6e91d9, 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_kk6bzijci377v2io)
5 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in rampstackco/claude-skills/backlog-triage since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of backlog-triage from somewhere else? Ask it: where did my backlog-triage come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, between Nov 8, 2026 and Nov 16, 2026, about one every 7 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261116.f6e91d9 latest | 2026-11-16 | f6e91d9 | 11,857 B | A | view · diff |
| git:20261108.0590510 | 2026-11-08 | 0590510 | 11,857 B | A | view |
Copies
1 file in 1 other repository holds the exact bytes of one of this file's versions, each committed after this file had them: it holds the newest version.
A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/backlog-triage/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (11857 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
rampstackco/claude-skills · 1,100 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kk6bzijci377v2io GET https://markdownregistry.com/api/v1/resolve?ref=rampstackco/claude-skills/backlog-triage GET https://markdownregistry.com/api/v1/blob/dca28832d451907d2be4ec3023e693c0fb4a19fe6b11da206432528efd2ed2d4
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.
More from rampstackco/claude-skills
Every file in rampstackco/claude-skills