fix-failing-pipelines
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.
Install / Use
npx skills add a5c-ai/babysitter --skill fix-failing-pipelinesInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of fix-failing-pipelines
fix-failing-pipelines scores 89/100 on our quality scale, 1369th of 2,780 Automation skills we index (top 50%).
Its SKILL.md is 4.0 KB long, well organised into 10 sections with 5 code examples: a solid amount of guidance for an agent.
With 1,809 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so fix-failing-pipelines is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
ReviewOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky: The skill instructs the agent to commit fixes directly to the `staging` branch without creating PRs or requiring user review.
AI review: risky
- The skill instructs the agent to commit fixes directly to the `staging` branch without creating PRs or requiring user review.
- It explicitly requires the workflow to run 'without any user interaction or breakpoints' and to auto-iterate until the pipeline succeeds.
- While the purpose (fixing CI failures) is legitimate, the autonomous push-and-iterate pattern removes normal human oversight safeguards.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
fix-failing-pipelines compared with similar skills
All 4 of these similar skills score higher than fix-failing-pipelines; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| fix-failing-pipelines (this skill)by a5c-ai | 89 | 1.8k | 2mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
Frequently asked questions
- How do I install fix-failing-pipelines?
- Run
npx skills add a5c-ai/babysitter --skill fix-failing-pipelines. The install tabs above show the steps for each supported agent. - Which AI agents does fix-failing-pipelines work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is fix-failing-pipelines safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky: The skill instructs the agent to commit fixes directly to the
stagingbranch without creating PRs or requiring user review. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand. - Is fix-failing-pipelines still maintained?
- The repository was last updated about 2 months ago, so fix-failing-pipelines is actively maintained.
Skill content
View source on GitHubname: 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:
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:
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:
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:
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.
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_progressare skipped entirely -- they haven't concluded yet. - Cancelled runs are not treated as failures.
- The
ghCLI must be authenticated. If authentication fails, prompt the user to rungh auth login. - Each fix is handed off to
/babysitter:yolowhich 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.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
