github-issue-triage skillA
github-issue-triage is agent-read markdown (skill) from openhands/extensions: Prioritize open issues and establish acceptance criteria before marking them ready for development..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# GitHub issue triage Prioritize open issues and establish acceptance criteria before marking them ready for development. Create this automation separately from implementation and review. Use a fine-grained GitHub PAT limited to the selected repositories with Issues: read and write. Never put the token value in the automation definition or prompt. Package `worker.py` with the shared `github_client.py` and `agent_conversation.py` helpers. Supply `config.json` with `repos` and the saved GitHub secret name; the entrypoint is `python3 worker.py`. Include that secret in the selected profile so the delegated agent can use GitHub. Naming it in the automation does not grant it to the agent. The scanner is an ordinary Automation host command. It submits selected issues through the shared KV-backed conversation dispatcher, which creates or resumes one stable conversation per issue through the Software Agent SDK. Only that agent workspace is local or Docker. Automation owns scheduling, cancellation, and cleanup. Honor `Depends on: #12, #13` lines. A dependency must be closed as completed. Do not treat an existing `ready-for-dev` label as proof of readiness: inspect the …
Read the whole file at its exact version.
How to install
mdr add openhands/extensions/github-issue-triage@git:20260921.49d0e9amdr add openhands/extensions/github-issue-triage@sha256:eec8e8f6d1c9f41fPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_vbnsphybkdexfdho)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260921.49d0e9a latest | 2026-09-21 | 49d0e9a | 3,141 B | A | view · diff |
| git:20260921.0d17c63 | 2026-09-21 | 0d17c63 | 2,955 B | A | view · diff |
| git:20260916.72cc245 | 2026-09-16 | 72cc245 | 1,665 B | A | view · diff |
| git:20260914.ceaddf0 | 2026-09-14 | ceaddf0 | 1,982 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 (3141 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
openhands/extensions · 150 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vbnsphybkdexfdho GET https://markdownregistry.com/api/v1/resolve?ref=openhands/extensions/github-issue-triage GET https://markdownregistry.com/api/v1/blob/eec8e8f6d1c9f41f898f438f037c082476ae3a08f70e609a4458c12c196861e3
Your agent 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.