More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    CI Pipeline Slowdown Fix

    1

    Find the stage eating your CI time, cut it, cache it, or parallelise it, with numbers before and after.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    CI Pipeline Slowdown Fix

    CI Pipeline Slowdown Fix

    Example session with this skill installed

    Apply the skill to a small test input and produce its core output. The script shares out median stage minutes only; it does not measure queue waiting or cache hit rates, which the protocol checks separately.

    • Read your context and instructions
    • Compiled the ci pipeline slowdown

    A pipeline had grown from 11 minutes to 38 minutes over four months, and developers had started batching changes to avoid it. Stage measurement showed the test stage at 24 minutes, but queue waiting added a further 9 minutes because only two runners served the team. Cache hit rate for dependencies was 18 percent because the cache key included a timestamp that changed every run. Fixing the cache key alone recovered 6 minutes; adding two runners recovered most of the queue wait; splitting the test stage by module recovered a further 7 minutes. Total time fell to 14 minutes over the next twenty runs, and the team stopped batching. No stage was removed, because the safety check showed the lint stage had caught two real defects in the previous month.

    Script demo (verified): running python3 scripts/ci_slowdown.py on a test file printed total 35.0 minutes, with the test stage at 24.0 minutes and 68.6 percent.

    This is a worked example produced by applying the skill, not a claim about a live customer outcome.

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

    About this skill

    A diagnostic workflow for slow continuous integration pipelines: measure stage durations, separate real work from waiting and repetition, and apply the fix that matches the measured cause. The skill provides a step-by-step protocol with decision points, a decision table, a fill-in template, a checklist, and a scoring rubric, plus a runnable script (ci_slowdown.py) that reads a pipeline-stage csv and reports each stage share of total time plus the slowest stages. It focuses on finding the bottleneck first and fixing in an order backed by evidence, rather than applying generic advice.

    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.

    It measures the pipeline, not developer machines; local build slowness needs a separate diagnosis. It cannot fix a slow test suite without test-level work.

    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 23 days ago

    Permissions

    Terminal / Shell
    Listed23 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    No. It organises evidence and decisions so judgement is applied to the right question, with a record of why.

    Longer than a generic checklist, because measurement comes first. Later uses are faster once templates and scripts are in place.

    Yes, by narrowing scope explicitly and recording what was skipped. The quality gate still applies to the narrowed work.

    New in DevOps & Cloud