Skip to content
TrustedSkillsbeta
Back to all skills

Ci Monitoring

Checked
troykelly·vlatest·devops

Proactively monitors CI/CD pipelines for errors, performance bottlenecks, and failed builds, alerting relevant teams immediately.

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 troykelly/codex-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/codex-skills at d8fb3968e4.

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

Commit
d8fb3968e4
Manifest
skills/ci-monitoring/SKILL.md
Scanned
1 file, 347 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 monitors Continuous Integration (CI) pipelines, providing real-time status updates and alerting on failures. It can integrate with various CI systems to track build progress, identify broken builds, and offer insights into potential deployment blockers. The agent can summarize pipeline history and provide details about specific build steps.

When to use it

  • Proactive Issue Detection: Get notified immediately when a CI pipeline fails, preventing delays in deployments.
  • Build Status Reporting: Quickly check the status of builds for different branches or features.
  • Troubleshooting Build Failures: Investigate specific build failures by examining logs and step-by-step details.
  • Release Readiness Assessment: Determine if a release candidate has passed all CI checks before promotion to production.

Key capabilities

  • Integration with various CI systems (specifics not detailed)
  • Real-time pipeline status monitoring
  • Failure alerting
  • Build history summarization
  • Detailed build step information

Example prompts

  • "What is the current status of the 'main' branch CI pipeline?"
  • "Show me the logs for the last failed build on the 'develop' branch."
  • "Summarize the recent history of builds for the 'release/1.0' branch."

Tips & gotchas

  • Requires configuration with your specific CI system credentials and URLs.
  • The level of detail provided depends on the capabilities exposed by the integrated CI system.