tickets-triage SKILL.md skillA
tickets-triage from baristaze/swe_guidelines is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add baristaze/swe_guidelines/tickets-triage@git:20261014.62aa70ePins git:20261014.62aa70e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- baristaze/swe_guidelines
- Path
scaffold/acme_root/.agents/skills/tickets-triage/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261014.62aa70e, committed Oct 14, 2026
- First version recorded
- Sep 29, 2026
- Size
- 6,200 bytes
- Repository stars
- 94
- License
- MIT
Triage the open tickets whose subject is this repository: for each, read it and check it against the code on main, the merged and open pull requests, and the history, then give it a verdict (done, moot, partly done, still relevant, in flight, out of scope, unsure) with the evidence. Writes a report; with --apply, and the person's word in the session, it comments the evidence and closes the done and the moot. Never changes code.
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
# tickets-triage Which open tickets are stale. A ticket is judged against the code as it is on `main`, not against its own text: a fix may have landed under another ticket's name, and a ticket's premise may no longer hold. ## Input `[--apply] [--team <name>] [--project <name>] [--limit <n>]` The tracker is Linear, the team `Acme` (the tools take the team's name, not its key), whose ticket ids read `ACME-<n>`, by default. The scope is every open ticket whose subject is this repository: the `Acme` project, and tickets in no project or in another project whose title or text names this repository or a path, a table, a route, or a skill of it. `--limit` triages that many of the scope, newest first, and the report says so. `--apply` closes what the verdicts allow, as step 6 says; without it the skill only reports. ## Role and credential None of the system's: the skill reads no environment and no database. It reads the tracker through the session's Linear connector, under the person's own sign-in, and the repository through `git` and `gh`. The connector's writes (a comment, a status) are not pre-approved: each one is the person's to allow. ## Procedure …
Read the whole file at its exact version.
How to install
mdr add baristaze/swe_guidelines/tickets-triage@sha256:b709e2a8a275894dThe line at the top of this page pins the label git:20261014.62aa70e, 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_m4bqvmv2hoxtbueq)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 29, 2026 and Oct 14, 2026, about one every 15 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.62aa70e latest | 2026-10-14 | 62aa70e | 6,200 B | A | view · diff |
| git:20260929.3422014 | 2026-09-29 | 3422014 | 6,202 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 (6200 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
baristaze/swe_guidelines · 94 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_m4bqvmv2hoxtbueq GET https://markdownregistry.com/api/v1/resolve?ref=baristaze/swe_guidelines/tickets-triage GET https://markdownregistry.com/api/v1/blob/b709e2a8a275894ddb83a9371442705baea5a7c6bc1cf8854c819c2b7416f63b
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.