failure-triage skillA
failure-triage is agent-read markdown (skill) from yeaight7/agent-powerups: Use when confronted with an unknown failure in CI or production, before committing to a deep debugging approach..
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
## Purpose Before diving deep into a stack trace or spending hours reproducing a bug, triage it to determine the blast radius, subsystem, and debugging approach. Do not start writing fixes until you have explicitly stated your triage hypothesis and confirmed the category. ## When to Use - A CI job or production system is failing and the cause is unknown - A bug report arrives without a clear owner or subsystem - Before choosing between deep debugging, bisecting, or reproduction work ## Inputs - The failure signal: stack trace, CI log excerpt, or error report - The repo, for recent-change inspection ## Workflow 1. **Categorize the failure:** - **Syntax/Build error** — fails before running - **Logic error** — runs, but produces wrong output - **Infrastructure/Environment error** — network timeout, missing DB table - **Flaky/Non-deterministic error** — fails sometimes 2. **Locate the origin.** Scan the stack trace. Ignore framework/library internals. Find the highest frame that belongs to the *first-party application code*: ```bash # surface first-party frames (adjust the path filter to the repo layout) grep -n "src/" stacktrace.txt | head -20 ``` …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/failure-triage@git:20260606.08e9c42mdr add yeaight7/agent-powerups/failure-triage@sha256:93e284c240f87567Pin 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_oots6ps5dkqwqds2)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.08e9c42 latest | 2026-06-06 | 08e9c42 | 2,478 B | A | view · diff |
| git:20260602.e829caf | 2026-06-02 | e829caf | 1,249 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 (2478 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
yeaight7/agent-powerups · 6 stars · license Apache-2.0 · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oots6ps5dkqwqds2 GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/failure-triage GET https://markdownregistry.com/api/v1/blob/93e284c240f87567e5086c5e4bfeb6ed3c6f9c9d52efddf87079bf1ae718a30d
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.
More from yeaight7/agent-powerups
Every file in yeaight7/agent-powerups