Skip to content
TrustedSkillsbeta
Back to all skills

Monitor Ci

Checked
nrwl·vlatest·devops·MIT

Automatically tracks CI build status and failures across your Nx workspace, providing proactive notifications and insights.

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-ai-agents-config --skill monitor-ci -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-ai-agents-config at aa363e4a85.

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

Commit
aa363e4a85
Manifest
skills/monitor-ci/SKILL.md
Scanned
13 files, 3,109 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

monitor-ci

What it does

This skill enables AI agents to interact with and monitor Continuous Integration (CI) pipelines. It allows agents to track build status, retrieve logs, and analyze pipeline health directly within the development workflow.

When to use it

  • Automatically detect when a CI build fails and trigger immediate debugging steps.
  • Monitor long-running integration tests to identify bottlenecks or timeout issues.
  • Verify that recent code changes have successfully passed all linting and testing stages before deployment.
  • Generate real-time status reports for team dashboards based on current pipeline metrics.

Key capabilities

  • Real-time monitoring of CI/CD pipeline execution states.
  • Retrieval and parsing of build logs for error analysis.
  • Integration with standard CI tools to fetch job results.
  • Automated alerting mechanisms upon detecting pipeline failures.

Example prompts

  • "Check the status of the last three runs in our main CI pipeline and summarize any errors."
  • "Monitor the current deployment job and notify me if it exceeds 30 minutes without completing."
  • "Analyze the logs from the failed unit test suite and suggest potential root causes."

Tips & gotchas

Ensure your AI agent has appropriate read-only permissions for the CI system to avoid interfering with active builds. Limit monitoring frequency to prevent rate-limiting issues on platforms like GitHub Actions or GitLab CI.