oss-issue-triage SKILL.md skillA
oss-issue-triage from samber/developer-relations-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add samber/developer-relations-skills/oss-issue-triage@v1.0.2Pins v1.0.2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- samber/developer-relations-skills
- Path
skills/oss-issue-triage/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.2, committed Oct 25, 2026
- First version recorded
- Sep 27, 2026
- Size
- 25,586 bytes
- Repository stars
- 8
- License
- MIT
Designs an issue and pull-request triage system a maintainer team can sustain - response targets sized against real capacity, the label taxonomy, intake cuts through structured forms and off-tracker routing, a separate security-report path, triage duty assignment, and the closing, staleness and volume-gating policy. Use whenever someone says "our issue tracker is out of control", "design an issue triage process", "set up labels for our repo", "we have 900 open issues…
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
# OSS Issue Triage You design the system that decides how a project's incoming issues and pull requests get handled - labels, intake, response promise, duty rotation, closing rules - sized to the capacity the maintainers actually have. The queue is not out of control because the labels are wrong. It is out of control because inflow exceeds available attention and no written rule says what happens to the difference. Make that arithmetic explicit, then design around it. Machine-generated submissions broke one side of it in 2025. RedMonk's Kate Holterhoff named the asymmetry for security reports (May 2026): "generating a plausible-sounding vulnerability report now costs pennies in tokens. Evaluating whether it's real still costs an hour of expert time." Inflow is no longer bounded by human effort while triage capacity still is, so every design needs a planned answer for volume, not only for classification. Do not triage individual items, curate the first-contribution queue, review code, or handle conduct incidents. Route those elsewhere: - First-contribution path, good first issues: samber/developer-relations-skills@oss-contributor-onboarding …
Read the whole file at its exact version.
How to install
mdr add samber/developer-relations-skills/oss-issue-triage@sha256:e69187de88a1b67aThe line at the top of this page pins the label v1.0.2, 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_7xq3zspq2chidjgx)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 27, 2026 and Oct 25, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.2 latest | 2026-10-25 | 2c2141c | 25,586 B | A | view · diff |
| v1.0.1 | 2026-10-21 | 3d28b0b | 25,581 B | A | view · diff |
| v1.0.1 | 2026-10-21 | d80286d | 25,453 B | A | view · diff |
| v1.0.1 | 2026-10-21 | dbff509 | 25,298 B | A | view · diff |
| v1.0.1 | 2026-09-27 | bc8ac6d | 25,174 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 (25586 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
samber/developer-relations-skills · 8 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7xq3zspq2chidjgx GET https://markdownregistry.com/api/v1/resolve?ref=samber/developer-relations-skills/oss-issue-triage GET https://markdownregistry.com/api/v1/blob/e69187de88a1b67a4b5fe1b412fda7547db7e523858b95037cadf1604e2eb975
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.