Skip to content
TrustedSkillsbeta
Back to all skills

Ci Monitor

Checked
nrwl·vlatest·testing·MIT

Continuously monitors CI build status, providing proactive alerts and insights to optimize development workflows.

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 nrwl/nx --skill ci-monitor -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

nrwl

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 nrwl/nx at 0ea74af9ad.

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

Commit
0ea74af9ad
Manifest
.cursor/skills/ci-monitor/SKILL.md
Scanned
3 files, 1,236 lines
Copies in repo
3 — all of them scanned
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

ci-monitor

What it does

This skill enables AI agents to monitor Continuous Integration (CI) pipelines, providing real-time visibility into build statuses and execution logs. It helps developers quickly identify failures or bottlenecks within automated testing workflows without manual dashboard checks.

When to use it

  • You need immediate alerts when a specific branch's CI job fails upon push.
  • You want an agent to summarize the root cause of a flaky test suite failure.
  • You require historical data on build times to optimize pipeline performance.
  • You need to verify that recent code changes passed all linting and unit tests automatically.

Key capabilities

  • Real-time monitoring of CI pipeline execution states.
  • Aggregation of build logs and error messages from various runners.
  • Integration with automated testing frameworks for comprehensive coverage tracking.
  • Status reporting across multiple branches or pull requests simultaneously.

Example prompts

  • "Check the status of the main branch CI pipeline and summarize any recent failures."
  • "Analyze the latest build logs to identify why the integration tests are timing out."
  • "List all open pull requests that have not yet passed their continuous integration checks."

Tips & gotchas

Ensure your CI provider credentials are securely configured before enabling this skill, as it requires access to live build data. Performance may degrade if monitoring an excessive number of parallel jobs simultaneously; consider filtering by specific branches or environments for better results.