fixing-ci SKILL.md skillA
fixing-ci 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/fixing-ci@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/ci-cd-tools/skills/fixing-ci/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261028.3c582f7, committed Oct 28, 2026
- First version recorded
- May 7, 2026
- Size
- 9,469 bytes
- Repository stars
- 12
- License
- MIT
Use when CI is failing on a branch, PR, or specific Buildkite build and the user wants to iteratively fix it through verify-locally → push → check → iterate. Strong signals: "fix CI", "make CI green", "CI is failing", "tests are failing in Buildkite", "iterate on this build", a Buildkite build URL paired with intent to push fixes, a PR with a red check the user wants to make green, or repeat-push debugging. Covers verify-fix-locally workflows (rspec, jest, lint, type checking before pushing)…
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
# Fixing CI ## Overview This skill drives an iterative CI fix session: investigate the failure (via the Buildkite investigation skill), apply a fix, verify it locally, push, watch the new build, and iterate until green or until you've hit the iteration cap and need to step back. The scope is the **fix loop only** — investigation is delegated to `buildkite:investigating-builds`, which already covers `bktide snapshot`, log reading, and failure-pattern recognition. ## When to Use - You have a failing CI build and want to push fixes until it goes green - You want to verify changes locally before each push (saves CI cycles) - You're iterating on fixes across multiple builds and need to know when to step back ## When NOT to Use - First-time "why did this fail" investigation with no fix-and-push intent → use `buildkite:investigating-builds` directly - Authoring or modifying pipeline YAML → use `buildkite:developing-pipelines` - GitHub Actions, CircleCI, or non-Buildkite CI ## Input Contract The skill needs to know what to fix. Any one of these inputs is sufficient: - **`build_url`** — A Buildkite build URL (e.g. `https://buildkite.com/org/pipeline/builds/123`) …
Read the whole file at its exact version.
How to install
mdr add technicalpickles/pickled-claude-plugins/fixing-ci@sha256:c9969218ec380ebbThe 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_cincsug4cgjcqfpw)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 7, 2026 and Oct 28, 2026, about one every 87 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.3c582f7 latest | 2026-10-28 | 3c582f7 | 9,469 B | A | view · diff |
| git:20261028.1458c1b | 2026-10-28 | 1458c1b | 8,773 B | A | view · diff |
| git:20260507.4006e57 | 2026-05-07 | 4006e57 | 7,942 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 (9469 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_cincsug4cgjcqfpw GET https://markdownregistry.com/api/v1/resolve?ref=technicalpickles/pickled-claude-plugins/fixing-ci GET https://markdownregistry.com/api/v1/blob/c9969218ec380ebbd9413339113b6e6e4cc0c7babe93faa9d91793f78694cd69
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.