Skip to content
TrustedSkillsbeta
Back to all skills

Pipeline Health Analyzer

Checked
onewave-ai·vlatest·devops·MIT

Proactively identifies bottlenecks and anomalies in CI/CD pipelines, optimizing performance and reducing deployment failures.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add onewave-ai/claude-skills --skill pipeline-health-analyzer -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

onewave-ai

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned onewave-ai/claude-skills at f317e08649.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
f317e08649
Manifest
pipeline-health-analyzer/SKILL.md
Scanned
6 files, 534 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The pipeline-health-analyzer skill provides real-time visibility into CI/CD system performance, automatically detecting bottlenecks and resource constraints within your build infrastructure. It correlates job execution metrics with underlying infrastructure events to pinpoint root causes of delays or failures.

When to use it

  • Investigating sudden spikes in build duration across multiple repositories.
  • Diagnosing intermittent timeout errors that lack clear error logs.
  • Optimizing resource allocation for high-traffic deployment windows.
  • Analyzing the impact of recent code changes on pipeline stability.

Key capabilities

  • Real-time monitoring of CI/CD job execution metrics.
  • Automatic detection of performance bottlenecks and latency sources.
  • Correlation of build failures with infrastructure events.
  • Identification of resource contention issues within the pipeline environment.

Example prompts

  • "Analyze the last 50 failed builds in our main repository and identify common failure patterns."
  • "Why is the staging deployment pipeline taking twice as long to complete compared to yesterday?"
  • "Correlate recent infrastructure changes with a spike in job timeout errors across the team."

Tips & gotchas

Ensure your CI/CD provider has detailed telemetry enabled, as the analyzer relies on comprehensive execution logs to generate accurate insights. Focus analysis on specific timeframes or repositories to avoid overwhelming the system with too much data at once.