ci-failure-readout skillA
ci-failure-readout is agent-read markdown (skill) from yeaight7/agent-powerups: Use when a CI pipeline has failed and the real error must be extracted from thousands of lines of noisy logs..
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 CI logs are notoriously noisy. Extract the one true error, prove it locally, and write a readout — do not dump the entire log into the context window. ## When to Use - A CI pipeline failed and the error is buried in long logs - A readout is needed before deciding what (or who) fixes the failure - A CI failure must be reproduced locally before fixing ## Inputs - Access to the CI run (e.g., `gh` for GitHub Actions) or a downloaded log file - The repo, to rerun the failing command locally ## Workflow 1. **Locate the true error.** Find the exact step that failed; ignore setup/teardown noise: ```bash gh run list --limit 10 # find the failing run gh run view <run-id> # failing job and step gh run view <run-id> --log-failed # logs from failing steps only # or, with a downloaded log: grep -n -iE "error|failed|exit code" ci.log | head -20 ``` 2. **Extract the trace.** Copy only the stack trace or the specific compiler/linter error message — not the surrounding noise. …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/ci-failure-readout@git:20260606.6ac314emdr add yeaight7/agent-powerups/ci-failure-readout@sha256:d3af9ab557bfcb53Pin 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_ag4kwr2th7htximu)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.6ac314e latest | 2026-06-06 | 6ac314e | 2,444 B | A | view · diff |
| git:20260502.db74eab | 2026-05-02 | db74eab | 910 B | A | view · diff |
| git:20260502.d4a3d81 | 2026-05-02 | d4a3d81 | 139 B | B | 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 (2444 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_ag4kwr2th7htximu GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/ci-failure-readout GET https://markdownregistry.com/api/v1/blob/d3af9ab557bfcb538ad5635f2b3cc0441f5127e301bd1196a6e527876e6b0f1f
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