issue-triage skillA
issue-triage is agent-read markdown (skill) from office-kit/pptx: Use to triage a GitHub issue — classify as bug / feature request / question / docs / dependency, apply the right label, and run the appropriate workflow (reproduce + fix-PR for bugs; "one way to do one thing" check + spec for features; answer with code pointer for questions). Invoked when the user mentions an issue number, pastes a GitHub issue URL, or says "triage", "look at", "handle", or "process" an issue..
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
# Issue triage Triage a GitHub issue end to end: read it, classify it, label it, and run the workflow that matches its kind. The user's GitHub handle is the **operator** (referred to as `op` below). When the issue's author and `op` are different, "the author" means whoever opened the issue. ## Operating principles - **Stay on the issue you were given.** One issue per invocation. Don't sweep related issues unless the user asks. - **Confirm before public actions.** Posting comments, applying labels, opening PRs, @-mentioning anyone: confirm the plan with the user before the first GitHub- visible action. After they approve, you can execute the rest of the plan without re-confirming each step. - **Never close the issue yourself.** Triage is routing; closing is the maintainer's call. - **Don't @-mention people who aren't already in the thread.** Specifically, the only person you may @-mention is the issue's author, and only when you actually need information from them. - **Match the issue's language.** If the issue is in Japanese, your comment is in Japanese. If English, English. Don't switch languages on the author. ## Step 0 — Locate the issue …
Read the whole file at its exact version.
How to install
mdr add office-kit/pptx/issue-triage@git:20260514.7b45fd7mdr add office-kit/pptx/issue-triage@sha256:1bc721fd91fa47b3Pin 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_wxwfs7tjaknyglie)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260514.7b45fd7 latest | 2026-05-14 | 7b45fd7 | 10,563 B | A | view · diff |
| git:20260514.f87e12d | 2026-05-14 | f87e12d | 10,175 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 (10563 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
office-kit/pptx · 14 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wxwfs7tjaknyglie GET https://markdownregistry.com/api/v1/resolve?ref=office-kit/pptx/issue-triage GET https://markdownregistry.com/api/v1/blob/1bc721fd91fa47b3f3052d54dc3277b83b4172e7957957590c912335a25137f4
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.