triage-findings-list SKILL.md skillA
triage-findings-list from webreactiva/yesyak is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add webreactiva/yesyak/triage-findings-list@git:20261017.b634987Pins git:20261017.b634987 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- webreactiva/yesyak
- Path
skills/triage-findings-list/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.b634987, committed Oct 17, 2026
- First version recorded
- Sep 27, 2026
- Size
- 1,933 bytes
- Repository stars
- 3
- License
- MIT
Merges findings from several reports (verification, browser testing, red team, production readiness, code review) into one numbered, deduplicated change list with traffic lights, grouped by when each change should happen and tagged with its source. Use it whenever the user asks to turn reports into a list of changes, prioritize findings, "what do we fix first", build a backlog from reviews, or decide what goes before merge and what goes later.
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
# Triage findings list ## Inputs Read every report the user names, and by default every `*-report.md` in `.scratchpad/<slug>/`. Give each report a short source tag, for example V (verification against the spec), B (browser testing), RT (red team), P (production readiness). ## Build the list 1. **Deduplicate.** One change can fix findings from several reports. Merge them and keep all source tags and ids: `(RT2, B1)`. 2. **Write each change as an action**, not as a problem: "Wrap long words in the order list", not "Long words break the layout". 3. **Give it a light** with `traffic-light-findings`. Keep the highest light that the evidence supports. 4. **Group by timing:** 🔴 before merge (mandatory); 🟠 before merge (recommended, little code); 🟠 before production; 🟠 technical debt; 🟡 minor improvements; accepted (no change), with the reason. 5. **Number the changes 1..N** in that order. These numbers are what the user will use to approve work, so do not change them after you share the list. For each change give: number, light, action, a short "why", the main files, and the source tags. ## Output - Save `.scratchpad/<slug>/change-list.md`. …
Read the whole file at its exact version.
How to install
mdr add webreactiva/yesyak/triage-findings-list@sha256:65e77bf8ab5e0fc7The line at the top of this page pins the label git:20261017.b634987, 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_ge2xiavex37qx6h5)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 27, 2026 and Oct 17, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.b634987 latest | 2026-10-17 | b634987 | 1,933 B | A | view · diff |
| git:20260927.2f2f40b | 2026-09-27 | 2f2f40b | 1,937 B | A | view · diff |
| git:20260927.87257af | 2026-09-27 | 87257af | 1,941 B | A | view · diff |
| git:20260927.d224a3a | 2026-09-27 | d224a3a | 1,941 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 (1933 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
webreactiva/yesyak · 3 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ge2xiavex37qx6h5 GET https://markdownregistry.com/api/v1/resolve?ref=webreactiva/yesyak/triage-findings-list GET https://markdownregistry.com/api/v1/blob/65e77bf8ab5e0fc71eb91331ab0c94abba19b375a7d408e0a5f5be2ab1447c2b
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.