ticket-triage SKILL.md skillA
ticket-triage from prabhdeepsingh/claude-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add prabhdeepsingh/claude-plugins/ticket-triage@git:20260913.4e5ade4Pins git:20260913.4e5ade4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- prabhdeepsingh/claude-plugins
- Path
sonu/skills/ticket-triage/SKILL.md- Versions recorded
- 6
- Latest version
- git:20260913.4e5ade4, committed Sep 13, 2026
- First version recorded
- Aug 1, 2026
- Size
- 13,857 bytes
- Repository stars
- 4
- License
- MIT
Turn one raw ticket into an implementation-ready spec — or ask the smallest unblocking question — without writing production code. INVOKE when specifying, scoping, or triaging a ticket from any tracker, when a ticket carries the ready-for-spec trigger, or when /sonu:factory routes a spec pass. Not backlog-wide classification ([[classify-tickets]]), defect discovery ([[bug-finder]]), or building an approved spec (/sonu:build). It writes only to the ticket. (Rulebook: [[ticket-lifecycle]].).
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
# Ticket triage — make the ticket good enough to build from A vague ticket is not ready for a human or an agent. Somebody has to convert "login is broken sometimes" into a bounded problem with testable acceptance criteria, and doing that work *before* implementation starts is what keeps the build from becoming a guess. That conversion is this skill's only job, and the artifact it produces is the spec every later stage inherits. The discipline that makes it useful is restraint. A triage pass that quietly starts fixing things destroys the human approval gate — the whole point is that a person reads the spec and decides whether it should be built at all. ## How to apply this Apply to `$ARGUMENTS` — the text typed after the invocation, a ticket id or URL. If that token appears literally or is empty, derive the ticket from context (the one `/sonu:factory` routed, or the one under discussion). With no ticket identifiable, say so and stop; never triage a ticket you had to guess at. …
Read the whole file at its exact version.
How to install
mdr add prabhdeepsingh/claude-plugins/ticket-triage@sha256:0a4eca10a1244ec9The line at the top of this page pins the label git:20260913.4e5ade4, 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_iurqetiufdxriu4u)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Aug 1, 2026 and Sep 13, 2026, about one every 8 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260913.4e5ade4 latest | 2026-09-13 | 4e5ade4 | 13,857 B | A | view · diff |
| git:20260826.3bb29a7 | 2026-08-26 | 3bb29a7 | 13,108 B | A | view · diff |
| git:20260826.0b4d903 | 2026-08-26 | 0b4d903 | 12,717 B | A | view · diff |
| git:20260826.41a30c8 | 2026-08-26 | 41a30c8 | 13,506 B | A | view · diff |
| git:20260825.06c64c5 | 2026-08-25 | 06c64c5 | 13,765 B | A | view · diff |
| git:20260801.179ef1c | 2026-08-01 | 179ef1c | 13,714 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 (13857 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
prabhdeepsingh/claude-plugins · 4 stars · license MIT · pushed 2026-10-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_iurqetiufdxriu4u GET https://markdownregistry.com/api/v1/resolve?ref=prabhdeepsingh/claude-plugins/ticket-triage GET https://markdownregistry.com/api/v1/blob/0a4eca10a1244ec927387f619c9b15bba8c748bb1f4ec189df8e18f659faaf6f
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 prabhdeepsingh/claude-plugins
Every file in prabhdeepsingh/claude-plugins