agentsclimarketplace

Ci failure triage

Skill jukrap/ai-agent-playbook/skills/devops/ci-failure-triage

Reusable AI agent skills, project templates, and guardrails for safer software maintenance and delivery.

Install
npx -y skills add jukrap/ai-agent-playbook --skill ci-failure-triage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when diagnosing failing CI jobs, build pipelines, deployment checks, flaky tests, environment drift, or release automation failures.

SKILL.md

0.7 KB, 124 tokens by cl100k_base, as published. Nobody here has run it

CI Failure Triage

Use this as the primary DevOps skill for pipeline failures.

Workflow

  1. Capture the failing job, command, environment, recent diff, and first meaningful error.
  2. Classify the failure as code, test, dependency, environment, cache, secret, or external service.
  3. Reproduce locally when feasible, then make the narrowest fix.
  4. Verify with the failing command or nearest reliable equivalent.

Reference

Read references/failure-signal-triage.md for log ordering, root-cause classification, cache/dependency handling, and rerun rules.

What ships with it: 1 file

1.9 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most test skills give in 124 tokens

Counted across 964 of the 1,571 authors here whose files we hold, read 2026-08-07

  • Close the browser when donein 55 of 964, across 12 files
  • Wait for network idle statein 51 of 964, across 6 files
  • Launch Chromium in headless modein 49 of 964, across 6 files
  • Use descriptive selectors for elementsin 49 of 964, across 6 files
  • Run provided scripts with help flag firstin 49 of 964, across 6 files
  • Add appropriate explicit waitsin 48 of 964, across 5 files
  • Use bundled scripts as black boxesin 46 of 964, across 3 files
  • Do not read script source codein 46 of 964, across 3 files
  • Use sync playwright for scriptsin 46 of 964, across 3 files
  • Inspect dom before executing actionsin 46 of 964, across 3 files
  • Run the full test suitein 37 of 964
  • Write the failing test firstin 29 of 964, across 23 files

Said here and by no other author read

  • capture failing job details
  • classify the failure type
  • reproduce locally when feasible
  • make the narrowest fix
  • verify with the failing command
  • read the referenced triage document

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.