issue-triage SKILL.md skillA
issue-triage from mattbrailsford/umbraco-devkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mattbrailsford/umbraco-devkit/issue-triage@git:20261019.61f6781Pins git:20261019.61f6781 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mattbrailsford/umbraco-devkit
- Path
plugins/umbraco-devkit/skills/issue-triage/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261019.61f6781, committed Oct 19, 2026
- First version recorded
- Oct 14, 2026
- Size
- 21,908 bytes
- Repository stars
- 3
- License
- MIT
Triages one, several or all untriaged tracker issues: type, code area, duplicates and possible security reports, as a report for human review. Once approved, applies `state/*` labels and a plain-language comment for the reporter. A `decisions` run walks through issues waiting on a maintainer. Use to classify a backlog, or one issue before acting on it. Owns the plugin's state labels, its tracker comment format, and its rule for handling security reports.
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
# issue-triage Read the room on a bug tracker before anyone commits to fixing anything. Classifies, checks for duplicates, points at the likely code, and flags anything that smells like a security report — then hands back a report. The tracker is the only record of what's been triaged, and nothing is written to it until the user says so. ## Scope - IN: fetch, classify, find the likely code area, duplicate-check, security-flag, report, draft a comment for the reporter, and apply the state labels, comments, or closes the user approves. - OUT: any tracker write the user hasn't approved, proving a bug's cause, writing fixes, planning a feature. Once a triaged issue turns into real work, hand off to `issue-resolve`. ## Preflight 1. **Resolve the tracker.** Read `CLAUDE.md` for an `## Issue tracker` section (type, location, access method). If it's missing, run the interview below and append the section — don't guess a tracker or invent an API to call. 2. Note whether the tracker lives in this repo or elsewhere (a separate GitHub repo, a Jira project, an Azure DevOps org) — the `Location` line answers that. Every fetch uses it …
Read the whole file at its exact version.
How to install
mdr add mattbrailsford/umbraco-devkit/issue-triage@sha256:4b54fe24957f67e0The line at the top of this page pins the label git:20261019.61f6781, 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_go7d6w4nicwdlxjc)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Oct 14, 2026 and Oct 19, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.61f6781 latest | 2026-10-19 | 61f6781 | 21,908 B | A | view · diff |
| git:20261016.a78a902 | 2026-10-16 | a78a902 | 21,192 B | A | view · diff |
| git:20261015.44b4607 | 2026-10-15 | 44b4607 | 21,632 B | A | view · diff |
| git:20261014.eeefa6a | 2026-10-14 | eeefa6a | 20,509 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 (21908 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
mattbrailsford/umbraco-devkit · 3 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_go7d6w4nicwdlxjc GET https://markdownregistry.com/api/v1/resolve?ref=mattbrailsford/umbraco-devkit/issue-triage GET https://markdownregistry.com/api/v1/blob/4b54fe24957f67e0336c57066c712f56decb5241fb08082db97b18d52b8a4b39
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 mattbrailsford/umbraco-devkit
Every file in mattbrailsford/umbraco-devkit