woodpecker-investigating-pipelines SKILL.md skillA
woodpecker-investigating-pipelines 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/woodpecker-investigating-pipelines@git:20261019.e70ee23Pins git:20261019.e70ee23 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/woodpecker/skills/woodpecker-investigating-pipelines/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261019.e70ee23, committed Oct 19, 2026
- First version recorded
- Oct 17, 2026
- Size
- 2,481 bytes
- Repository stars
- 12
- License
- MIT
Use when a Woodpecker CI pipeline failed or its status is unclear - a red `ci/woodpecker/...` check, "Pipeline failed" from `gh pr checks`, a Woodpecker `/repos/<id>/pipeline/<n>` URL, "why did CI fail" in a repo that builds with Woodpecker, or a push that has no CI result at all.
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
# Investigating Woodpecker pipelines
Woodpecker's web UI and REST API need a login Claude doesn't have, and a forge status only says "failed". `woodpecker-snapshot` drives `woodpecker-cli` (already logged in) and prints one block: the pipeline's state, every step's state, and the first failed step's log tail.
## Run it
```bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/woodpecker-snapshot" [REF] [--pr N | --sha SHA] [--repo owner/name] [--tail N]
```
| Input | Looks up |
|-------|----------|
| nothing | the pipeline for the current commit (repo from the git remote) |
| `--pr N` or `--sha SHA` | the pipeline for that commit (needs `gh` for `--pr`) |
| a number | that pipeline number |
| a pipeline URL | the repo ID and number in it |
Exit 0 means a state was reported, including `failed`. Exit 2 means it couldn't read Woodpecker; the `State:` line says why.
## Read the State line first
The first line is always `State: <state>`. Report that state, not a guess from the forge status.
| State | Do this |
|-------|---------|
| `failed` | Read the log tail for the **first** failure. Later skipped steps are fallout. If the tail cuts off before the error, rerun with a larger `--tail`. |
…Read the whole file at its exact version.
How to install
mdr add technicalpickles/pickled-claude-plugins/woodpecker-investigating-pipelines@sha256:b3f20fb1aeaea7c2The line at the top of this page pins the label git:20261019.e70ee23, 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_247z7fr3jsjih45h)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 17, 2026 and Oct 19, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.e70ee23 latest | 2026-10-19 | e70ee23 | 2,481 B | A | view · diff |
| git:20261017.f0972a6 | 2026-10-17 | f0972a6 | 2,462 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 (2481 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-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_247z7fr3jsjih45h GET https://markdownregistry.com/api/v1/resolve?ref=technicalpickles/pickled-claude-plugins/woodpecker-investigating-pipelines GET https://markdownregistry.com/api/v1/blob/b3f20fb1aeaea7c214fd0770702aef0fae87c4cea235820e75a2c9e2354b60ec
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.