Skip to content
TrustedSkillsbeta
Back to all skills

Ci Monitoring

Checked
troykelly·vlatest·devops

Proactively monitors CI/CD pipelines for failures, bottlenecks, and inefficiencies using data analysis and automated alerts.

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 troykelly/claude-skills --skill ci-monitoring -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

troykelly

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 troykelly/claude-skills at 38a2ecc528.

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

Scanned
3 files, 327 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

What it does

This skill provides continuous integration (CI) monitoring capabilities. It allows you to track the status of your CI pipelines, identify failures, and receive notifications about build outcomes. The skill is designed to integrate with various CI platforms and provide actionable insights into your development process.

When to use it

  • Troubleshooting Build Failures: Quickly diagnose why a recent CI pipeline run failed by examining logs and error messages.
  • Proactive Issue Detection: Monitor CI pipelines for regressions or performance degradation over time.
  • Automated Reporting: Generate regular reports on CI build success rates and overall health.
  • Real-time Notifications: Receive alerts when critical CI builds fail, enabling rapid response and mitigation.

Key capabilities

  • CI pipeline status tracking
  • Build failure analysis
  • Integration with various CI platforms (unspecified)
  • Automated reporting
  • Real-time notifications

Example prompts

  • "What was the result of the last build for project 'Phoenix'?"
  • "Show me a graph of build success rates for the 'Mobile App' pipeline over the past week."
  • "Notify me immediately if any builds in the 'Backend API' pipeline fail."

Tips & gotchas

This skill requires access to your CI platform’s APIs or logs. Ensure appropriate credentials and permissions are configured within the AI agent environment for proper functionality.