investigating-builds SKILL.md skillA
investigating-builds from technicalpickles/pickled-claude-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add technicalpickles/pickled-claude-plugins/investigating-builds@git:20261028.3c582f7Pins git:20261028.3c582f7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- technicalpickles/pickled-claude-plugins
- Path
plugins/buildkite/skills/investigating-builds/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261028.3c582f7, committed Oct 28, 2026
- First version recorded
- Apr 6, 2026
- Size
- 10,043 bytes
- Repository stars
- 12
- License
- MIT
Use when the user is working with an existing Buildkite CI run and wants to understand, diagnose, or act on it. Strong signals: a buildkite.com URL, the word "buildkite", the `bk` CLI, the `bktide` tool, or a reference to a specific pipeline, build, or job. Covers intents like: "why did this build fail", "what's flaking", "summarize pass/fail rates across recent builds", "pull logs for this job", "figure out the exact command CI ran so I can reproduce it locally" (often via docker-compose)…
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
# Working with Buildkite Builds
Check status, investigate failures, and reproduce them locally for Buildkite builds that already exist.
## Tools, in order
**Always use Buildkite-native tools. Don't fall back to `gh pr view`/`gh pr checks` or the GitHub API**: GitHub shows only a summary and loses annotations, logs, and the broken-vs-failed distinction. If one Buildkite tool fails, move to the next tier below rather than abandoning Buildkite.
1. **`npx bktide@latest snapshot <buildkite-url>`** (use this first). Parses any build or step URL, downloads build metadata, annotations, and logs for failed steps into files you can grep and re-read without more API calls. `bktide snapshot --help` for options, `bktide prime` for LLM-oriented usage.
```
./tmp/bktide/snapshots/<org>/<pipeline>/<build>/
├── manifest.json # Step index with states and exit codes
├── build.json # Full build metadata
├── annotations.json # Build annotations
└── steps/<NN-step-name>/{log.txt,step.json}
```
…Read the whole file at its exact version.
How to install
mdr add technicalpickles/pickled-claude-plugins/investigating-builds@sha256:30d4b54804455515The line at the top of this page pins the label git:20261028.3c582f7, 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_3plseby3chvos7h4)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Apr 6, 2026 and Oct 28, 2026, about one every 41 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.3c582f7 latest | 2026-10-28 | 3c582f7 | 10,043 B | A | view · diff |
| git:20261028.c2c0bcf | 2026-10-28 | c2c0bcf | 9,039 B | A | view · diff |
| git:20260901.75010d8 | 2026-09-01 | 75010d8 | 28,665 B | A | view · diff |
| git:20260509.bbbee03 | 2026-05-09 | bbbee03 | 26,975 B | A | view · diff |
| git:20260417.5fb33ec | 2026-04-17 | 5fb33ec | 25,887 B | A | view · diff |
| git:20260406.7c7544e | 2026-04-06 | 7c7544e | 25,120 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 (10043 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
technicalpickles/pickled-claude-plugins · 12 stars · license MIT · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3plseby3chvos7h4 GET https://markdownregistry.com/api/v1/resolve?ref=technicalpickles/pickled-claude-plugins/investigating-builds GET https://markdownregistry.com/api/v1/blob/30d4b54804455515a9a1984066fb3d3a4d830c7165f60efe2d81f7d7421cf90d
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.