CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 clearly sequenced with thorough validation and feedback loops, making it a strong operational spec. Its main weakness is conciseness and progressive disclosure: repetitive flows and two long example sessions are inlined in a single ~445-line file with no supporting bundle files.

Suggestions

Consolidate the repeated 'Apply Locally + Enhance Flow' and commit-message-format sections into a single canonical reference instead of restating them in multiple places.

Move the two full example sessions and the detailed per-status handling subsections into separate reference files (e.g. EXAMPLES.md, STATUS-HANDLING.md) and link to them from the main loop, reducing the SKILL.md footprint.

Tighten the status table and the individual status subsections so each status is defined in exactly one place, eliminating overlap between the default-behavior table and the prose subsections.

DimensionReasoningScore

Conciseness

Dense and procedural with little concept padding, but the ~445-line body repeats several flows (Apply Locally + Enhance, commit message formats, status handling) across sections in a way that could be tightened.

3 / 5

Actionability

Provides copy-paste-ready Task() spawn prompts, exact MCP calls, git/bash commands, package-manager detection, and commit message templates that cover the common cases.

5 / 5

Workflow Clarity

Clear sequenced main loop (Steps 1-4) with explicit validation checkpoints (Nx Cloud check, local verification), feedback loops (enhance/re-verify, circuit breaker), and an exit-conditions checklist.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and tables, but everything is inlined in a single long file with no bundle files; the two full example sessions and repeated flow descriptions could be factored out.

4 / 5

Total

17

/

20

Passed

Description

87%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 strong: it clearly states what the skill does, when to use it via natural trigger phrases, and includes a precondition plus a negative-use boundary that minimizes conflict risk. Minor room remains for slightly more granular action coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Monitor Nx Cloud CI pipeline status', 'handle self-healing fixes automatically') plus a precondition and an explicit negative boundary; minor gaps in granular coverage.

4 / 5

Completeness

Explicitly answers both what (monitor CI status, handle self-healing fixes) and when (concrete quoted trigger phrases), plus a precondition and a 'Do NOT use' boundary.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('watch CI', 'monitor pipeline', 'check CI status', 'fix CI failures', 'self-heal CI') with synonym coverage, though a few natural variations are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Nx Cloud CI self-healing) with distinct triggers and an explicit negative boundary excluding local execution and general CI debugging.

5 / 5

Total

18

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tech-leads-club/agent-skills
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.