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

89%

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

88%Weight 40%Scale 1-5

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

A highly actionable, well-sequenced orchestration skill with explicit validation gates and feedback loops appropriate to its destructive git/fix operations. Progressive disclosure is mostly sound, with minor room to push more reference material out of the top-level file.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational with no conceptual padding, though some inline reference material (the full MCP field-set lists and large status tables) could be trimmed or moved to keep the overview leaner.	4 / 5
Actionability	Provides fully executable, copy-paste-ready script invocations with every flag specified, exact MCP tool field sets, and concrete per-status tool calls covering the common cases.	5 / 5
Workflow Clarity	A clearly sequenced main loop (Steps 1-4) with explicit validation checkpoints (gate check before local fixes, cycle-check before handling codes, hard stop on limitReached) and feedback loops via the error-handling table.	5 / 5
Progressive Disclosure	Good structure with a well-signaled one-level-deep reference (references/fix-flows.md) and offloaded deterministic scripts, though a fair amount of reference-like material (field sets, status tables) remains inline.	4 / 5
	Total	18 / 20 Passed

Description

90%Weight 40%Scale 1-5

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

A strong description that clearly states its purpose, provides abundant natural trigger phrases, and explicitly differentiates itself from competing CI provider tools. The only minor gap is that the capability list is limited to two top-level actions rather than a fuller enumeration.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ("Monitor Nx Cloud CI pipeline and handle self-healing fixes") but does not enumerate the broader set of monitoring/fix capabilities, matching the 1-2 concrete actions anchor.	3 / 5
Completeness	Explicitly answers both what (monitor Nx Cloud CI pipeline, handle self-healing fixes) and when via a concrete "USE WHEN" clause with multiple trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive coverage of natural user phrases including synonyms and variations ("monitor ci", "watch ci", "ci monitor", "watch ci for this branch", "track ci", "check ci status") that users would naturally say.	5 / 5
Distinctiveness Conflict Risk	Clear Nx Cloud CI-monitoring niche with distinct triggers, and it explicitly positions itself against native CI provider tools (gh, glab) to minimize conflict risk.	5 / 5
	Total	18 / 20 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: 9064aa9

Reviewed: about 4 hours 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.