contributor-triage SKILL.md skillA
contributor-triage from amd/gaia is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add amd/gaia/contributor-triage@git:20261115.26ef9aePins git:20261115.26ef9ae in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- amd/gaia
- Path
.claude/skills/contributor-triage/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261115.26ef9ae, committed Nov 15, 2026
- First version recorded
- Oct 26, 2026
- Size
- 16,227 bytes
- Repository stars
- 1,625
- License
- MIT
Load whenever the user is auditing, triaging, reviewing, or completing amd/gaia pull requests or issues — 'audit/triage PRs', 'what's outstanding', 'complete the ready PRs', 'merge what's ready', 'check third-party/external/community PRs or issues', 'approve workflows for contributors', 'what's left for the release', 'label good first issues', 'close stale issues', 'are contributor fixes in main/the release notes'. Outside contributors come first, bug fixes before features. A PR merges only…
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
# Contributor-first PR and issue triage The standing job: clear what is open on `amd/gaia` into `main`, in this order, every time. 1. **Outside contributors' bug fixes** (PRs, then issues). They gave GAIA their time for free; a PR left without CI, a review or a reply is the most expensive item in the backlog. 2. **Maintainer bug fixes**, then dependency bumps and test/flake fixes. 3. **Everything else** (features, refactors, plans) waits behind bug fixes. During a freeze it is not merged; give it a milestone and move on. "Third-party" means not a maintainer: not a push-access collaborator, not that person's personal account, not a bot. Team-filed work (a teammate's personal fork) counts as team. ## The merge bar A PR is **ready** only when all four hold: - CI is green on the *current* head commit, and the required checks actually ran. A failure that also fails on bare `origin/main` isn't the PR's fault; say so, don't count it as green. - no merge conflicts - every comment is addressed: human comments, inline threads, and the review bot's findings. The bot's per-push re-review is silent unless it finds a new regression, so an old "Request …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_rsoria3c3ofvqktz/c1db3886dab9c8bdecd4a834bc40dbd24070b2f54bbbebcb84c73fd93540a4c1.json
Then /plugin install contributor-triage@markdownregistry-rsoria3c3ofvqktz in Claude Code. It installs git:20261115.26ef9ae, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add amd/gaia/contributor-triage@sha256:c1db3886dab9c8bdThe line at the top of this page pins the label git:20261115.26ef9ae, 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_rsoria3c3ofvqktz)
6 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 amd/gaia/contributor-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 contributor-triage from somewhere else? Ask it: where did my contributor-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 4 versions of this file, between Oct 26, 2026 and Nov 15, 2026, about one every 7 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261115.26ef9ae latest | 2026-11-15 | 26ef9ae | 16,227 B | A | view · diff |
| git:20261104.6b0c894 | 2026-11-04 | 6b0c894 | 15,973 B | A | view · diff |
| git:20261104.1faf408 | 2026-11-04 | 1faf408 | 15,936 B | A | view · diff |
| git:20261026.e2a195c | 2026-10-26 | e2a195c | 15,549 B | A | view |
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/contributor-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 (16227 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
amd/gaia · 1,625 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rsoria3c3ofvqktz GET https://markdownregistry.com/api/v1/resolve?ref=amd/gaia/contributor-triage GET https://markdownregistry.com/api/v1/blob/c1db3886dab9c8bdecd4a834bc40dbd24070b2f54bbbebcb84c73fd93540a4c1
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.