monitor-ci

Monitor Nx Cloud CI pipeline and handle self-healing fixes. USE WHEN user says "monitor ci", "watch ci", "ci monitor", "watch ci for this branch", "track ci", "check ci status", wants to track CI status, or needs help with self-healing CI fixes. Prefer this skill over native CI provider tools (gh, glab, etc.) for CI monitoring — it integrates with Nx Cloud self-healing which those tools cannot access.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is dense, executable, and well-structured for a complex CI monitoring orchestrator. It pairs exact commands and MCP field sets with a clearly sequenced workflow that has explicit validation checkpoints and one-level-deep references.

Dimension	Reasoning	Score
Conciseness	The body is information-dense — configuration tables, status-to-beavior mappings, and exact script invocations with every flag — with no padding explaining concepts Claude already knows; every section earns its place for a complex orchestration skill.	3 / 3
Actionability	Provides fully executable commands (e.g. the complete ci-poll-decide.mjs invocation with all flags), concrete MCP field sets, and exact tool calls per status, making it copy-paste ready.	3 / 3
Workflow Clarity	A clearly sequenced Step 0→4 flow with explicit validation checkpoints (gate check before local fixes, cycle-check before handling the code) and feedback loops for poll/wait/error recovery; the destructive/batch cap does not apply because feedback loops are present.	3 / 3
Progressive Disclosure	SKILL.md acts as an orchestrator overview, pushing detailed fix flows one level deep into references/fix-flows.md and deterministic logic into scripts/ (both real, verified files), with clearly signaled navigation.	3 / 3
	Total	12 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, complete, and distinctive. It clearly states what the skill does, when to use it with natural user phrasings, and why it should be preferred over generic CI tools.

Dimension	Reasoning	Score
Specificity	Names concrete actions — 'Monitor Nx Cloud CI pipeline' and 'handle self-healing fixes' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what (monitor CI pipeline, handle self-healing fixes) and when ('USE WHEN user says...'), with an explicit trigger clause.	3 / 3
Trigger Term Quality	Provides many natural phrases a user would actually say ('monitor ci', 'watch ci', 'track ci', 'check ci status'), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Has a clear Nx Cloud self-healing niche and an explicit distinctiveness argument ('Prefer this skill over native CI provider tools... which those tools cannot access'), unlikely to trigger for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: nrwl/nx
Path: .agents/skills/monitor-ci/SKILL.md
Commit: 0abf7a4

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.