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.
85
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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, natural trigger terms in a 'Use when' clause, clear scope boundaries with explicit exclusions referencing other skills, and a distinct niche focused on Nx Cloud CI pipeline monitoring and self-healing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists concrete actions: monitor 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. | 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 | Includes excellent 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-specific terms like 'Nx Cloud' and 'pipeline'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche (Nx Cloud CI monitoring/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
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured skill with excellent workflow clarity, featuring explicit decision trees, validation checkpoints, and error recovery flows. However, it suffers significantly from verbosity—the document is far too long for a SKILL.md, with repeated explanations and inline detail that should be split into referenced sub-documents. The content would benefit greatly from aggressive compression and progressive disclosure into separate files.
Suggestions
Reduce the SKILL.md to a concise overview (~100 lines) covering the main loop, status table, and key decision points, moving detailed flows (Fix Available Decision Logic, Apply Locally + Enhance, No-New-CIPE Handling) into separate referenced markdown files.
Eliminate redundant explanations—for example, the Apply vs Reject vs Apply Locally section largely repeats what's already covered in the Fix Available Decision Logic and subsequent flow sections.
Compress the configuration defaults and user instruction examples tables, which explain concepts Claude can infer (e.g., 'Maximum duration in minutes' for --timeout).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This skill is extremely verbose at ~350+ lines. It includes extensive tables, repeated explanations of flows (Apply vs Reject vs Apply Locally explained multiple times), and detailed state machine logic that could be significantly compressed. Many sections restate information already covered elsewhere in the document. | 1 / 3 |
Actionability | The skill provides highly concrete, executable guidance: specific git commands, exact MCP call signatures, precise decision trees with conditions and actions, commit message formats, and package manager detection logic. Every workflow step has clear, copy-paste-ready commands. | 3 / 3 |
Workflow Clarity | The multi-step workflow is exceptionally well-sequenced with explicit validation checkpoints (local verification before pushing, circuit breakers, progress tracking, retry limits). The main loop is clearly numbered, decision trees have explicit conditions and paths, and error recovery flows are well-defined with feedback loops. | 3 / 3 |
Progressive Disclosure | While the content is organized with clear headers and tables, it's essentially a monolithic document with no references to external files. The extensive decision logic, multiple flow variants, and detailed examples could benefit from being split into separate reference files (e.g., fix-flows.md, status-reference.md) with the SKILL.md serving as a concise overview. | 2 / 3 |
Total | 9 / 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
906a57d
- 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.