CtrlK
BlogDocsLog inGet started
Tessl Logo

ci-pipeline-monitor

Monitors .NET runtime CI test pipelines on Azure DevOps. Use this skill when asked to monitor CI pipeline test results, triage CI test failures across ADO pipelines, or generate CI test monitoring reports.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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

A well-architected, highly actionable skill body with a clearly sequenced 7-step workflow, explicit validation and retry feedback loops, an executable script inventory, and clean one-level-deep references. The main weakness is moderate repetition of key directives across sections, which could be tightened.

Suggestions

Consolidate the repeated 'INSERT every failure into test_results immediately' directive so it is stated authoritatively once (e.g. in the Extraction rules) and merely referenced from the Step 3 notes, to reduce token cost.

De-duplicate the ADO_TOKEN / authentication warnings that appear in both Step 0 and the Rules > Extraction section, keeping the canonical version in Step 0 and linking from elsewhere.

Ensure the referenced template files (pipelines.md, log-template.md, report-template.md) are present in the bundle or clearly marked as runtime-generated, so every in-body reference resolves to an existing file.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes Claude's competence (no explanations of what CI, SQLite, or Azure DevOps are), but several directives are repeated across sections — e.g. 'Every individual failure must be INSERT'd' appears in both the Step 3 notes and the Extraction rules, and the ADO_TOKEN/auth warnings recur in Step 0 and Rules. This matches score 2 (mostly efficient but could be tightened) rather than score 3 where every token strictly earns its place.

2 / 3

Actionability

Provides fully executable bash commands with exact arguments (e.g. 'python scripts/validate_results.py --db scripts/monitor.db --pipelines pipelines.md --log logs/...'), a concrete script-to-step table, a complete SQL schema, and exact API URLs. This matches the score-3 anchor of copy-paste-ready, executable guidance.

3 / 3

Workflow Clarity

The 7-step sequence (Step 0 through Step 7) is clearly ordered with an explicit validation checkpoint (Step 5 validate-before-report) and a fix→revalidate feedback loop (Step 5a, up to 3 retries with a 'stop when failure count stops decreasing' condition). This matches the score-3 anchor of clear sequencing with explicit validation and error-recovery feedback loops.

3 / 3

Progressive Disclosure

SKILL.md is an organized overview that signals one-level-deep references to real files in references/ (triage-workflow.md, verbatim-rules.md, validation-checks.md, prerequisites.md), all of which exist in the bundle. Content is appropriately split; no nested multi-level reference chains. The additionally referenced pipelines.md/log-template.md/report-template.md are runtime/template artifacts documented in directory-layout.md rather than missing nested references, so the structure still meets the score-3 anchor.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concise description that names a specific domain and multiple concrete actions, with an explicit 'Use this skill when' trigger clause covering natural user phrasings. It is highly distinctive and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Names the domain (.NET runtime CI on Azure DevOps) and lists multiple concrete actions: 'monitor CI pipeline test results', 'triage CI test failures across ADO pipelines', and 'generate CI test monitoring reports'. This matches the score-3 anchor (lists multiple specific concrete actions) rather than score 2, which only names a domain and some actions incomprehensively.

3 / 3

Completeness

Explicitly answers both what ('Monitors .NET runtime CI test pipelines...triaging failures') and when ('Use this skill when asked to monitor CI pipeline test results, triage CI test failures across ADO pipelines, or generate CI test monitoring reports'). The explicit 'Use this skill when' trigger clause satisfies the score-3 anchor; score 2 requires when to be missing or only implied.

3 / 3

Trigger Term Quality

Includes natural terms a user would actually say — 'CI pipeline test results', 'CI test failures', 'ADO pipelines', 'CI test monitoring reports' — with good coverage of phrasing variations. It is above score 2 because it covers multiple natural variations rather than a single relevant keyword.

3 / 3

Distinctiveness Conflict Risk

The narrow niche (.NET runtime CI on Azure DevOps, ADO pipelines, Helix) and specific trigger phrasing make it unlikely to fire for unrelated skills. This clears the score-3 anchor of a clear niche with distinct triggers, rather than the score-2 case of only being somewhat specific.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 missing

Warning

referenced_paths_exist

Referenced path issues: 12 missing

Warning

Total

14

/

16

Passed

Repository
dotnet/runtime
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.