ci-monitor

Monitor Nx Cloud CI pipeline and handle self-healing fixes automatically. Checks for Nx Cloud connection before starting.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/ci-monitor/SKILL.md

Quality

Content

77%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.

The body is highly actionable and lays out a clear, well-validated monitoring workflow with concrete MCP/git commands and feedback loops. Its main weaknesses are redundancy in the Apply-Locally + Enhance flow and a monolithic structure with no external references despite the length.

Suggestions

Consolidate the Apply-Locally + Enhance flow into a single canonical section and reference it from the other flows instead of restating it.

Move the two example sessions (and optionally the full status-behavior table) into a references/ file (e.g. EXAMPLES.md) and link to it from the body to improve progressive disclosure.

Trim explanatory prose around obvious commands and tables to tighten token efficiency without losing the concrete guidance.

Dimension	Reasoning	Score
Conciseness	Mostly efficient decision tables and concrete commands, but the Apply-Locally + Enhance flow is described repeatedly (Fix Available Decision Logic Step 3b, the dedicated 'Apply Locally + Enhance Flow' section, and again inside other flows), and the example-session block adds length that could be trimmed.	3 / 5
Actionability	Provides fully executable guidance: exact MCP call signatures (update_self_healing_fix({ shortLink, action: "APPLY" })), concrete git/npm commands, package-manager detection logic, and ready-to-use subagent Task() prompts covering the common cases.	5 / 5
Workflow Clarity	Clear multi-step monitoring loop with explicit validation checkpoints — a Step 0 Nx Cloud connection check, a local-verify → enhance → re-run feedback loop before pushing, a no-progress circuit breaker, and a complete exit-conditions table.	5 / 5
Progressive Disclosure	Well-organized with clear headers and tables, but it is a 430-line monolithic SKILL.md with no external reference files; content that could be split out (detailed status-behavior tables, the two example sessions) is inlined, so structure is present but not leveraged for progressive disclosure.	3 / 5
	Total	16 / 20 Passed

Description

58%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.

The description is specific and clearly scoped to Nx Cloud CI monitoring with self-healing, but it lacks an explicit 'when to use' trigger clause and relies on fairly technical language rather than natural user phrases. Adding a 'Use when...' sentence with common user phrasings would raise both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when monitoring an Nx Cloud CI run, handling self-healing fixes for a failed PR, or when CI is failing on your branch.'

Include natural user-facing phrases alongside the technical terms ('CI is failing', 'broken PR', 'fix my CI') to broaden trigger-term coverage.

Mention the file/context signals that should prompt use (e.g. an nx.json with nxCloudId) to further reduce conflict risk with generic CI skills.

Dimension	Reasoning	Score
Specificity	Names the domain (Nx Cloud CI pipeline) and lists several concrete actions — monitor the pipeline, handle self-healing fixes automatically, and check the Nx Cloud connection before starting — with only minor gaps in coverage.	4 / 5
Completeness	Has a clear 'what' (monitor pipeline, handle self-healing fixes, check connection) but no explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Includes relevant domain keywords ('Nx Cloud CI pipeline', 'self-healing fixes') but leans technical and misses common natural variations a user might say ('monitor my CI', 'fix broken PRs', 'CI is failing').	3 / 5
Distinctiveness Conflict Risk	Targets a specific niche (Nx Cloud CI monitoring with self-healing) with distinct product-scoped triggers, leaving only minor overlap risk with adjacent CI/devops skills.	4 / 5
	Total	14 / 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: .cursor/skills/ci-monitor/SKILL.md
Commit: 9064aa9

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