Agent skill

Fix Failing Pipelines

Install Fix Failing Pipelines

skills CLI

$ npx skills add a5c-ai/babysitter --skill fix-failing-pipelines -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install a5c-ai/babysitter fix-failing-pipelines --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/a5c-ai/babysitter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/fix-failing-pipelines .claude/skills/fix-failing-pipelines && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "fix-failing-pipelines" agent skill from https://github.com/a5c-ai/babysitter/tree/main/.claude/skills/fix-failing-pipelines into .claude/skills/fix-failing-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-failing-pipelines", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/a5c-ai/babysitter/tree/main/.claude/skills/fix-failing-pipelines

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add a5c-ai/babysitter --skill fix-failing-pipelines -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install a5c-ai/babysitter fix-failing-pipelines --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/a5c-ai/babysitter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/fix-failing-pipelines .agents/skills/fix-failing-pipelines && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "fix-failing-pipelines" agent skill from https://github.com/a5c-ai/babysitter/tree/main/.claude/skills/fix-failing-pipelines into .agents/skills/fix-failing-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-failing-pipelines", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add a5c-ai/babysitter --skill fix-failing-pipelines -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install a5c-ai/babysitter fix-failing-pipelines --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/a5c-ai/babysitter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/fix-failing-pipelines .cursor/skills/fix-failing-pipelines && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "fix-failing-pipelines" agent skill from https://github.com/a5c-ai/babysitter/tree/main/.claude/skills/fix-failing-pipelines into .cursor/skills/fix-failing-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-failing-pipelines", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/a5c-ai/babysitter.git --path .claude/skills/fix-failing-pipelines

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add a5c-ai/babysitter --skill fix-failing-pipelines -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install a5c-ai/babysitter fix-failing-pipelines --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/a5c-ai/babysitter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/fix-failing-pipelines .gemini/skills/fix-failing-pipelines && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "fix-failing-pipelines" agent skill from https://github.com/a5c-ai/babysitter/tree/main/.claude/skills/fix-failing-pipelines into .gemini/skills/fix-failing-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-failing-pipelines", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install a5c-ai/babysitter fix-failing-pipelines

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add a5c-ai/babysitter --skill fix-failing-pipelines -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/a5c-ai/babysitter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/fix-failing-pipelines .github/skills/fix-failing-pipelines && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "fix-failing-pipelines" agent skill from https://github.com/a5c-ai/babysitter/tree/main/.claude/skills/fix-failing-pipelines into .github/skills/fix-failing-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-failing-pipelines", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add a5c-ai/babysitter --skill fix-failing-pipelines -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install a5c-ai/babysitter fix-failing-pipelines --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/a5c-ai/babysitter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/fix-failing-pipelines .opencode/skills/fix-failing-pipelines && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "fix-failing-pipelines" agent skill from https://github.com/a5c-ai/babysitter/tree/main/.claude/skills/fix-failing-pipelines into .opencode/skills/fix-failing-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-failing-pipelines", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: fix-failing-pipelines
GitHub stars: 1.8k
Token cost: ~1k tokens
SKILL.md length: 447 words
Files: 1
Skills in repo: 14
Repo updated: Sep 16, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Works in 7 steps: Fetch Most Recent Run Per Workflow → Identify Failures → Get Failure Details → …
Asks to fix pipelines
SKILL.md covers Workflow and Notes
Calls gh

What it does

Fix Failing Pipelines is an agent skill from a5c-ai/babysitter. This skill should be used when the user asks to "fix pipelines", "fix CI", "check staging pipelines", "fix failing workflows", "fix failing actions", or wants to find and fix failing GitHub Actions workflows on the staging branch of the babysitter repo.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Failing and flaky tests and CI/CD. It works with GitHub Actions. The repository describes itself as: Babysitter enforces obedience on agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration. The licence is MIT.

When your agent uses it

Asks to fix pipelines
Check staging pipelines
Fix failing workflows
Fix failing actions

Example prompts

“fix pipelines”
“fix CI”
“check staging pipelines”
“/fix-failing-pipelines”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

Fetch Most Recent Run Per Workflow
Identify Failures
Get Failure Details
Present Failures
Fix via Babysitter
Verify Fixes
Summary

What it can do on your machine

Read from SKILL.md and the folder at commit feb68ab. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fix Failing Pipelines loads about 1k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 447 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~69
When it runs · the whole SKILL.md, loaded when a task matches: ~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from a5c-ai/babysitter at commit feb68ab, republished under its MIT licence (© a5c-ai). 447 words, ~1,031 tokens.

Download SKILL.mdSave it as .claude/skills/fix-failing-pipelines/SKILL.md (or your agent's skills folder).

name: fix-failing-pipelines
description: This skill should be used when the user asks to "fix pipelines", "fix CI", "check staging pipelines", "fix failing workflows", "fix failing actions", or wants to find and fix failing GitHub Actions workflows on the staging branch of the babysitter repo.

Fix Failing Pipelines

Check GitHub Actions workflows on the staging branch of https://github.com/a5c-ai/babysitter/actions, identify workflows whose most recent run is failing, and dispatch /babysitter:yolo to fix each one.

Workflow

Step 1: Fetch Most Recent Run Per Workflow

Use the gh CLI to list recent workflow runs on the staging branch:

bash

gh run list --repo a5c-ai/babysitter --branch staging --limit 50 --json databaseId,workflowName,status,conclusion,createdAt,headBranch

Group the results by workflowName. For each workflow, keep only the most recent run (by createdAt). Discard workflows where the most recent run is still in_progress -- we only care about completed runs.

Step 2: Identify Failures

From the grouped results, select only workflows where the most recent completed run has conclusion: "failure". Skip workflows whose latest run succeeded, was cancelled, or is still running.

If no workflows have a failing most-recent run, report that all staging pipelines are green and stop.

Step 3: Get Failure Details

For each failing workflow run, fetch the failed job and step details:

bash

gh run view <run_id> --repo a5c-ai/babysitter --json jobs --jq '.jobs[] | select(.conclusion == "failure") | {name, conclusion, steps: [.steps[] | select(.conclusion == "failure") | .name]}'

Then fetch the logs to understand the actual error:

bash

gh run view <run_id> --repo a5c-ai/babysitter --log-failed 2>&1 | tail -100

Step 4: Present Failures

Display the list of failing workflows to the user with:

Workflow name
Run ID and link
Failed job name(s) and failed step name(s)
Brief summary of the error from the logs

Step 5: Fix via Babysitter

For each failing workflow, invoke the babysitter:yolo skill with a prompt that includes the failure context:

/babysitter:yolo fix the failing "<workflow_name>" pipeline on staging. The most recent run (<run_id>) failed in job "<job_name>" at step "<step_name>". Error details: <brief_error_summary>. Investigate the failure, fix the root cause, and push a fix to the staging branch. Do not create a new branch -- commit directly to staging.

If multiple workflows are failing, process them sequentially -- complete one before starting the next. Present a summary after each fix attempt.

Step 6: Verify Fixes

After pushing a fix for each workflow, wait briefly then check if a new run was triggered:

bash

gh run list --repo a5c-ai/babysitter --branch staging --workflow "<workflow_file>" --limit 1 --json databaseId,status,conclusion

Report whether a new run was triggered and its current status. Do not wait for it to complete -- just confirm it was triggered.

Show full SKILL.md (169 more words)Show less

Step 7: Summary

After all failing workflows have been addressed, provide a summary:

Which workflows were failing
What was fixed for each
Whether new runs were triggered
Any workflows that could not be fixed (with reason)

Notes

Only the most recent run per workflow type matters. Older failures that have since been superseded by a success are not actionable.
Runs that are in_progress are skipped entirely -- they haven't concluded yet.
Cancelled runs are not treated as failures.
The gh CLI must be authenticated. If authentication fails, prompt the user to run gh auth login.
Each fix is handed off to /babysitter:yolo which handles the actual implementation work non-interactively.
Fixes are committed directly to staging -- no feature branches or PRs for pipeline fixes.
The entire workflow should be without any user interaction or breakpoints in the run, allowing for seamless pipeline repair.
if you fixed it, wait for the new run to be completed and check if it succeeded. if it failed again, iterate on the fix until it succeeds.

Files

Just SKILL.md in .claude/skills/fix-failing-pipelines of a5c-ai/babysitter.

Open the folder on GitHubat commit feb68ab

Compare with similar skills

Fix Failing Pipelines next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fix Failing Pipelines compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Fix Failing Pipelines this skilla5c-ai/babysitter	1.8k	—	~1k	Automated safety check: Pass	MIT	24 days ago
CI Failure Triage and RepairChachamaru127/claude-code-harness	3.2k	1 repos	~1.1k	Automated safety check: Notes	MIT	6 days ago
CI Watchdoglatitude-dev/latitude-llm	4.7k	—	~1.6k	Automated safety check: Pass	MIT	2 days ago
Megatron-LM CI Failure TriageNVIDIA/Megatron-LM	18k	—	~1.6k	Automated safety check: Pass	Apache-2.0	today
CI Triagefair-acc/gnuradio4	115	—	~548	Automated safety check: Pass	LGPL-3.0	today
CI Failure Triagen1m21n/Infinite	272	—	~1.5k	Automated safety check: Pass	Custom licence	today

Similar skills

CI Failure Triage and Repair
Chachamaru127/claude-code-harness
Diagnoses failing CI pipelines and tests, deciding first whether the test or the implementation is at fault, and hands hard cases to a dedicated fixer subagent.
3.2k GitHub starsUsed in 1 repo~1.1k tokens
DevOps & CloudAuto-check: notes
CI Watchdog
latitude-dev/latitude-llm
Continuously monitor GitHub PR CI checks and automatically fix failures until all checks pass.
4.7k GitHub stars~1.6k tokensUpdated 2 days ago
DevOps & CloudAuto-check passed
Megatron-LM CI Failure Triage
NVIDIA/Megatron-LM
Official
Investigates a failing GitHub Actions run or job for Megatron-LM, finds the root cause plus the PR and test author involved, and files a structured bug issue.
18k GitHub stars~1.6k tokensUpdated today
DevOps & CloudAuto-check passed
CI Triage
fair-acc/gnuradio4
Fetch and classify a failed GitHub Actions job for this repo — distinguish out-of-memory kills, six-hour timeouts, configure errors and genuine test failures, and identify what was in flight.
115 GitHub stars~548 tokensUpdated today
DevOps & CloudAuto-check passed
CI Failure Triage
n1m21n/Infinite
Diagnose a failed GitHub Actions run (Windows MSVC crash, Linux clang/sanitizer, link errors) from the logs in one pass, and fix every candidate at once instead of one CI round-trip at a time.
272 GitHub stars~1.5k tokensUpdated today
DevOps & CloudAuto-check passed
CI Debugging
citypaul/.dotfiles
Systematic CI/CD failure diagnosis using hypothesis-first investigation, local reproduction, and environment delta analysis.
740 GitHub stars~1.5k tokensUpdated 2 days ago
DevOps & CloudAuto-check: notes

More from a5c-ai/babysitter

All 14 skills in this repo

AWS DrawIO Diagram Generator
a5c-ai/babysitter
Creates and edits AWS architecture diagrams as DrawIO XML, converting a text description or an image and reading existing files back into shapes.
1.8k GitHub stars~4.2k tokensUpdated 24 days ago
Auto-check passed
GCP DrawIO Diagram Generator
a5c-ai/babysitter
Creates DrawIO XML diagrams of Google Cloud architectures from text or images, and analyzes existing .drawio files to list their GCP components.
1.8k GitHub stars~3.7k tokensUpdated 24 days ago
Auto-check passed
Babysitter Run Orchestrator
a5c-ai/babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter…
1.8k GitHub starsUsed in 1 repo~514 tokens
Auto-check passed
Babysitter Process Runner
a5c-ai/babysitter
Execute via @babysitter. Use this skill when asked to babysit a task, do anything that is structured process-driven (even a loop) or whenever it is called…
1.8k GitHub starsUsed in 1 repo~726 tokens
Auto-check: notes
Assimilate Popular Workflows
a5c-ai/babysitter
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns"…
1.8k GitHub stars~8.5k tokensUpdated 24 days ago
Auto-check passed
Babysit Babysitter Issues
a5c-ai/babysitter
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues…
1.8k GitHub stars~590 tokensUpdated 24 days ago
Auto-check passed

Works with

GitHub Actions

Questions about Fix Failing Pipelines

What does Fix Failing Pipelines do?

This skill should be used when the user asks to "fix pipelines", "fix CI", "check staging pipelines", "fix failing workflows", "fix failing actions", or wants to find and fix failing GitHub Actions…. Fix Failing Pipelines is an agent skill from a5c-ai/babysitter. This skill should be used when the user asks to "fix pipelines", "fix CI", "check staging pipelines", "fix failing workflows", "fix failing actions", or wants to find and fix failing GitHub Actions workflows on the staging branch of the babysitter repo.

When should I use Fix Failing Pipelines?

Fix Failing Pipelines fits situations like: asks to fix pipelines; check staging pipelines; fix failing workflows; fix failing actions.

How do I install Fix Failing Pipelines in Claude Code?

Run `npx skills add a5c-ai/babysitter --skill fix-failing-pipelines -a claude-code`. Or copy the skill folder (.claude/skills/fix-failing-pipelines in a5c-ai/babysitter) into .claude/skills/fix-failing-pipelines in your project. Claude Code loads it when a task matches its description.

How do I install Fix Failing Pipelines in Codex?

Run `npx skills add a5c-ai/babysitter --skill fix-failing-pipelines -a codex`. Or copy the skill folder (.claude/skills/fix-failing-pipelines in a5c-ai/babysitter) into .agents/skills/fix-failing-pipelines in your project. Codex loads it when a task matches its description.

Can I use Fix Failing Pipelines in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add a5c-ai/babysitter --skill fix-failing-pipelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix-failing-pipelines, .gemini/skills/fix-failing-pipelines, .github/skills/fix-failing-pipelines and .opencode/skills/fix-failing-pipelines in your project.

What does Fix Failing Pipelines need to run?

Going by SKILL.md and its folder, Fix Failing Pipelines needs the command-line tools its instructions call (gh).

Does Fix Failing Pipelines access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Fix Failing Pipelines safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Fix Failing Pipelines use?

Fix Failing Pipelines is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fix Failing Pipelines use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Fix Failing Pipelines?

Skills that share tags, products or a category with Fix Failing Pipelines: CI Failure Triage and Repair (Chachamaru127/claude-code-harness, 3.2k stars), CI Watchdog (latitude-dev/latitude-llm, 4.7k stars), Megatron-LM CI Failure Triage (NVIDIA/Megatron-LM, 18k stars) and CI Triage (fair-acc/gnuradio4, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix Failing Pipelines?

a5c-ai (a GitHub organization) maintains it in a5c-ai/babysitter, which has 1,839 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 16, 2026.

Source: a5c-ai/babysitter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Fix Failing Pipelines

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Fix Failing Pipelines

Workflow

Step 1: Fetch Most Recent Run Per Workflow

Step 2: Identify Failures

Step 3: Get Failure Details

Step 4: Present Failures

Step 5: Fix via Babysitter

Step 6: Verify Fixes

Step 7: Summary

Notes

Files

Compare with similar skills

Similar skills

More from a5c-ai/babysitter

Related

Questions about Fix Failing Pipelines