nx-ci-monitor
Monitor Nx Cloud CI pipeline status and handle self-healing fixes automatically. Use when user says "watch CI", "monitor pipeline", "check CI status", "fix CI failures", or "self-heal CI". Requires Nx Cloud connection. Do NOT use for local task execution (use nx-run-tasks) or general CI debugging outside Nx Cloud.
65
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./packages/skills-catalog/skills/(tooling)/nx-ci-monitor/SKILL.mdQuality
Discovery
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.
This is an excellent skill description that hits all the marks. It provides specific capabilities, comprehensive trigger terms, explicit 'Use when' and 'Do NOT use' clauses, and clear differentiation from related skills. The inclusion of negative boundaries referencing other skills by name is particularly effective for disambiguation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Monitor Nx Cloud CI pipeline status', 'handle self-healing fixes automatically'. Also specifies what NOT to use it for (local task execution, general CI debugging), which adds clarity about its scope. | 3 / 3 |
Completeness | Clearly answers both 'what' (monitor Nx Cloud CI pipeline status, handle self-healing fixes) and 'when' (explicit 'Use when' clause with multiple trigger phrases). Also includes negative boundaries ('Do NOT use for...') which further strengthens completeness. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'watch CI', 'monitor pipeline', 'check CI status', 'fix CI failures', 'self-heal CI'. These are phrases users would naturally say. Also includes domain terms like 'Nx Cloud' and 'pipeline'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche (Nx Cloud CI monitoring and self-healing). Explicitly differentiates from related skills by naming 'nx-run-tasks' for local execution and excluding general CI debugging, minimizing conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly actionable and has excellent workflow clarity with well-defined state machines, decision trees, and validation checkpoints. However, it is severely over-long and monolithic — the content would benefit enormously from being split across multiple files with the SKILL.md serving as a concise overview. The verbosity is the primary weakness, with many concepts explained redundantly across sections.
Suggestions
Split detailed flows (Fix Available Decision Logic, Apply Locally + Enhance, No-New-CIPE Handling, Error Handling) into separate referenced files, keeping only a summary table in SKILL.md
Remove redundant explanations — e.g., 'Apply vs Reject vs Apply Locally' section repeats information already covered in the status behavior table and the detailed flow sections
Consolidate the wait mode explanation into a single location rather than explaining it in both the status table, Step 3a, and the 'Why wait mode matters' paragraph
Move the Example Session section to a separate EXAMPLES.md file and reference it from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines. It contains extensive tables, repeated explanations of flows (Apply vs Reject vs Apply Locally explained multiple times), and detailed state machine logic that could be significantly condensed. Many sections restate information already covered elsewhere in the document (e.g., wait mode is explained in both the main table and Step 3a with redundant justification). | 1 / 3 |
Actionability | The skill provides highly concrete, executable guidance throughout: specific git commands, exact MCP call signatures, precise task categorization logic, commit message formats, and detailed decision trees with clear conditions and actions. Every status has a defined behavior with specific steps to execute. | 3 / 3 |
Workflow Clarity | The multi-step workflow is exceptionally well-sequenced with explicit validation checkpoints (Step 0 Nx Cloud check, local verification before pushing, retry loops with attempt tracking, circuit breaker after 3 no-progress iterations). The fix available decision logic has clear categorization steps, and feedback loops (enhance → verify → retry or push) are well-defined with max attempt limits. | 3 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of text with no references to supporting files. Given the complexity and length (~350+ lines), significant portions (e.g., the Fix Available Decision Logic, Apply Locally + Enhance Flow, No-New-CIPE Handling) should be split into separate reference files. There are no bundle files provided, and the skill makes no attempt to organize content across files despite clearly needing it. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
100%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
- tech-leads-club/agent-skills
- Commit
0ebf6cc
- Reviewed
Table of Contents
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.