More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Pipeline Failure RCA

    1

    Turn messy CI/CD, Docker, and Kubernetes failure logs into an evidence-backed Root Cause Analysis and a safe, human-run recovery plan.

    $15

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Pipeline Failure RCA

    Pipeline Failure RCA

    Example session with this skill installed

    Context: GitLab CI → deploy payments-api to staging Kubernetes (EKS).
    Symptom: deploy:staging job fails; pods never Ready. Production not involved.

    kubectl get pods -n payments-staging:
    payments-api-7f8c9d4b6-xk2m1 0/1 CrashLoopBackOff 6 11m
    payments-api-5a1b2c3d4-m8n7w 1/1 Running 0 2d

    kubectl describe (excerpt):
    Readiness probe failed: HTTP probe failed with statuscode: 500
    Back-off restarting failed container payments-api

    kubectl logs --previous (excerpt):
    ERROR config validation failed: missing required env STRIPE_WEBHOOK_SECRET
    FATAL refusing to start with invalid config
    process exit code=1

    GitLab CI / Helm (tail):
    helm upgrade --install payments-api ... --set image.tag=2.14.0 --wait --timeout 5m
    Error: UPGRADE FAILED: context deadline exceeded
    ERROR: Job failed: exit code 1

    • Read your context and instructions
    • Compiled the pipeline failure rca

    Pipeline Failure RCA Report

    1. Executive Summary

    The staging Helm rollout for payments-api:2.14.0 failed because new pods enter
    CrashLoopBackOff: process exits with code 1 after config validation fails on
    missing STRIPE_WEBHOOK_SECRET, readiness probes return HTTP 500, and
    helm upgrade --wait times out. Old pods remain healthy; production was not touched.

    2. Root Cause Analysis (Evidence-Backed)

    | Failure Domain | Specific Error | Log Evidence |
    | Infrastructure / Config | Missing required env | missing required env STRIPE_WEBHOOK_SECRET |
    | Runtime | Exit code 1 | refusing to start with invalid config |
    | Kubernetes Health | Readiness 500 | HTTP probe failed with statuscode: 500 |
    | CI/CD Deploy | Helm wait timeout | UPGRADE FAILED: context deadline exceeded |

    3. Immediate Recovery Plan (human-run only)

    1. Inspect Secret + Deployment env refs in payments-staging
    2. Apply STRIPE_WEBHOOK_SECRET from vault (never commit secrets)
    3. helm upgrade … --wait; verify READY 1/1 and /health 200
    4. If blocked: helm rollback payments-api -n payments-staging

    4. Long-Term Prevention

    • CI pre-check for required secrets in target namespace
    • Helm lint fails when secretKeyRefs unset
    • Boot integration test with minimal env fixture

    5. Blast Radius & Rollback

    • Data impact: None (config at startup)
    • Downtime risk: Staging rollout stuck; old pod still Running
    • Rollback: helm rollback (staging only) — no namespace delete

    Incident Management JSON

    {
      "incident_type": "Kubernetes Rollout Failure",
      "severity": "Medium (Staging)",
      "failure_domain": "Infrastructure/Config",
      "root_cause_summary": "payments-api:2.14.0 CrashLoopBackOff because STRIPE_WEBHOOK_SECRET is missing; readiness 500 and helm --wait timeout.",
    

    "immediate_fix_commands": ["kubectl get secret -n payments-staging", "helm rollback payments-api -n payments-staging", "..."],
    "prevention_tags": ["kubernetes", "helm", "secrets", "crashloopbackoff", "gitlab-ci"]
    }

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Failed deploys dump hundreds of lines of CI, Docker, and Kubernetes noise. Teams lose time scrolling for the real error code, guess the root cause, and sometimes apply unsafe “fixes” under pressure.

    What it does

    Pipeline Failure RCA turns raw failure evidence into a structured report:

    • Executive summary of what failed and where
    • Evidence-backed RCA with log quotes and failure domain
    • Immediate recovery plan (unblock) + verification steps
    • Long-term prevention recommendations
    • Blast radius and rollback assessment
    • Incident Management JSON for tickets / status pages

    Frameworks & tools

    • GitHub Actions, GitLab CI, Jenkins, CircleCI log triage
    • Docker exit codes (e.g. 137 OOM, 143 SIGTERM, 1)
    • Kubernetes CrashLoopBackOff, ImagePullBackOff, probe failures
    • Common patterns: OOM, peer deps, IAM 403, missing config/secrets
    • Production safety rules: fix-forward vs rollback, no destructive recovery

    Why this beats prompting it yourself

    • Every RCA claim must cite log evidence — less hand-waving
    • Pattern library for frequent DevOps failure modes
    • Safety gate rewrites unsafe recovery suggestions
    • Blast radius + rollback decision matrix built in
    • JSON artifact for incident tooling — not only a chat essay
    • Strict read-only: analysis only, human executes

    Use cases

    • Broken CI build or deploy stage
    • Container OOM or crash on start
    • K8s rollout stuck / CrashLoopBackOff
    • Cloud/IAM deploy permission errors
    • Fast RCA for engineering managers and on-call

    Known limitations

    • Quality depends on the logs you provide (truncated logs lower confidence)
    • Does not connect to clusters or CI systems by itself
    • Does not execute remediation commands
    • Not a substitute for on-call judgment on production data-path incidents

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.

    • Needs the failing log excerpt; truncated logs → low confidence + missing-evidence ask.
    • Does not SSH, kubectl, or call cloud APIs unless you paste output.
    • Never executes recovery commands.
    • Review aid — production data-path decisions still need human/SRE judgment.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 21 days ago

    Accounts
    Api

    Permissions

    Read Files

    Allowed Hosts

    api.internal

    Strict read-only forensics. Never executes kubectl/helm/docker, never pushes code, never suggests rm -rf, DROP TABLE, force-push to main, or deleting namespaces. Recovery steps are copy-paste blocks for human review. If auto-detect grants Shell/Write/Network, turn them off.

    Listed3 months ago

    What's inside

    Frequently Asked Questions

    The skill analyzes raw logs from CI/CD tools (GitHub Actions, Jenkins, etc.), Docker containers, and Kubernetes events to identify the specific root cause and provide a structured recovery plan. It eliminates the time wasted manually scrolling through thousands of lines of log noise during an outage.

    No, this skill operates on a strict 'read-only' analysis basis to ensure production safety. It provides a human-executable recovery plan and verification steps, but it will never directly execute commands or modify your infrastructure.

    This skill is compatible with any AI agent platform that supports text-based log input. Simply paste your CI/CD, Docker, or Kubernetes logs into the agent, and it will generate the structured RCA report and JSON artifacts.

    Yes, the skill is pre-configured to recognize common DevOps failure patterns such as Docker OOM kills (137), Kubernetes CrashLoopBackOffs, IAM permission errors, and dependency conflicts. It includes a built-in safety gate to prioritize rollbacks over potentially destructive 'fix-forward' attempts.

    You will receive the full AI agent skill configuration, including the specialized RCA pattern library and the incident management JSON schema. You also get lifetime access to version updates as new DevOps failure patterns are added to the library.

    The skill relies on the logs you provide; for the most accurate results, ensure you include the full stack trace or event description. While it can handle truncated logs, the confidence level of the root cause identification may decrease if critical context is missing.

    New in DevOps & Cloud