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

82%

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

70%Scale 1-5

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

This is a sophisticated orchestration skill with excellent workflow clarity and strong actionability. Its main weakness is length — at 300+ lines it pushes the boundaries of conciseness, with several tables and sections that could be extracted into reference files. The references to external files (fix-flows.md, scripts) without bundle files makes it hard to fully evaluate progressive disclosure, but the SKILL.md itself carries too much detail inline.

Suggestions

Extract the anti-patterns table, error handling table, and user instruction examples into a separate reference file (e.g., references/monitor-ci-reference.md) to reduce the main skill's token footprint

Move the detailed 'Default Behaviors by Status' tables into a reference file, keeping only a brief summary in the main skill with a clear pointer to the detailed reference

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~300+ lines) and includes several tables and sections that could be more compact. Some information like the anti-patterns table and user instruction examples add value but are verbose. The configuration defaults table and detailed state tracking variables could be tightened. However, it doesn't over-explain basic concepts Claude already knows.	3 / 5
Actionability	Provides concrete bash commands for decision scripts, specific field sets for MCP tools, explicit state variable initialization, and clear action mappings. However, the actual MCP tool calls are described rather than shown with exact invocation syntax, and some actions reference external files (references/fix-flows.md) without providing them. The subagent spawning mechanism is described conceptually rather than with executable examples.	4 / 5
Workflow Clarity	The workflow is exceptionally well-structured with clear numbered steps (0 through 4), explicit validation checkpoints (Nx Cloud connection check, gate checks before local fixes, cycle classification before handling codes), feedback loops (poll → decide → act → track → poll), and error recovery paths. The decision script output drives clear branching logic, and the state update mechanism provides explicit verification before proceeding.	5 / 5
Progressive Disclosure	The skill references external files like 'references/fix-flows.md' and scripts like 'ci-poll-decide.mjs' and 'ci-state-update.mjs', but no bundle files are provided to verify these exist. The SKILL.md itself is quite long and monolithic — the detailed status tables, anti-patterns, error handling, and user instruction examples could potentially be split into reference files. The field sets (WAIT_FIELDS, LIGHT_FIELDS, HEAVY_FIELDS) are appropriately inlined, but the overall document would benefit from better separation of reference material.	3 / 5
	Total	15 / 20 Passed

Description

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

This is a strong skill description that clearly defines its scope (Nx Cloud CI monitoring and self-healing), provides comprehensive trigger terms covering natural user phrases, and proactively disambiguates from competing tools. The only minor weakness is that the concrete actions of 'self-healing fixes' could be slightly more elaborated, but overall this is well above average.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions: monitor CI pipeline, handle self-healing fixes, track CI status. It also specifies the domain (Nx Cloud CI) and differentiates from native CI provider tools. Minor gap: doesn't elaborate on what 'self-healing fixes' entails concretely.	4 / 5
Completeness	Clearly answers both 'what' (monitor Nx Cloud CI pipeline, handle self-healing fixes) and 'when' (explicit 'USE WHEN' clause with multiple concrete trigger phrases). Also includes a preference/disambiguation note explaining when to choose this skill over alternatives.	5 / 5
Trigger Term Quality	Excellent coverage of natural trigger phrases: 'monitor ci', 'watch ci', 'ci monitor', 'watch ci for this branch', 'track ci', 'check ci status'. These are exactly the phrases a user would naturally say. Also mentions 'self-healing CI fixes' and tool names like 'gh', 'glab' for disambiguation.	5 / 5
Distinctiveness Conflict Risk	Highly distinctive — explicitly scoped to Nx Cloud CI pipelines and self-healing, and proactively disambiguates from native CI provider tools (gh, glab). This clear niche and explicit preference guidance minimizes conflict risk with other CI-related skills.	5 / 5
	Total	19 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: getlarge/themoltnet
Path: .agents/skills/monitor-ci/SKILL.md
Commit: 5daa9ca

Reviewed: ~13 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.