CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

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.

A well-engineered orchestration skill: deterministic steps are scripted with exact commands, agent steps are bounded by explicit rules, and the validate-fix-retry loop with gated report generation is exemplary. The main costs are token duplication between the pipeline overview and the detailed workflow, a large inline SQL schema, and thin inline guidance for the core triage step.

Suggestions

Move the full SQL DDL (~65 lines) into a reference file (e.g., references/schema.md), keeping only the behaviorally significant fields and their semantics inline in SKILL.md, to cut tokens and complete the content split.

De-duplicate the 'End-to-end pipeline' comment block against the detailed Workflow section — keep the overview as a bare command list and let the step sections carry the annotations, or vice versa.

Inline a compact classification taxonomy in Step 4 (e.g., exit-code + error-message patterns mapping to failure_category values), since triage is the skill's core agent responsibility and currently depends entirely on references/triage-workflow.md.

DimensionReasoningScore

Conciseness

The body is dense with operational specifics and explains no general concepts, but the "End-to-end pipeline" comment block (Steps 0–6) duplicates the detailed Workflow section, and the script-table descriptions repeat Step 3 details verbatim. Anchor 4 (efficient, minor instances that could be trimmed) fits better than 5 ("every token earns its place") because of this structural duplication, and better than 3 since the redundancy is deliberate map-vs-detail rather than padding.

4 / 5

Actionability

Most steps are copy-paste ready — exact commands with flags ("python scripts/setup_and_fetch_builds.py --pipelines pipelines.md --db scripts/monitor.db"), an exact API URL, full SQL DDL, and a literal WARN log format. It falls short of anchor 5 because Step 4 — the core agent task of triage — defers entirely to references/triage-workflow.md with no inline classification criteria, and Step 7 (bisect) is five high-level bullets without commands; it is above anchor 3 because the executable machinery is complete.

4 / 5

Workflow Clarity

Steps 0–7 are explicitly sequenced and labeled deterministic-vs-agent, with a dedicated validation gate (Step 5: 24 checks, exit 1 on failure), an explicit bounded feedback loop (Step 5a: "up to 3 retries, only while failure count decreases" with a WARN-and-proceed path), and report generation gated on validation. This squarely matches anchor 5 (explicit validation steps, feedback loops for error recovery); the batch-operation cap does not apply since validation is thorough.

5 / 5

Progressive Disclosure

References are well-signaled and one level deep — "See [references/triage-workflow.md](references/triage-workflow.md) for full instructions", plus prerequisites.md, validation-checks.md, verbatim-rules.md, and templates — giving a clear overview-plus-detail structure. It stops short of anchor 5 because ~65 lines of SQL DDL are inlined in SKILL.md where anchor 5 expects content appropriately split out; no bundle files were provided to verify the referenced files exist, so scoring reflects the body's structure as written.

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.

A strong description: it explicitly states what the skill does and gives three concrete, natural trigger phrases in a clearly bounded niche (.NET runtime CI on Azure DevOps). The only room for improvement is broader synonym coverage (e.g., "build failures", "flaky tests") and mentioning secondary capabilities like GitHub issue matching.

DimensionReasoningScore

Specificity

"Monitors .NET runtime CI test pipelines on Azure DevOps" names the domain, and the trigger clause lists three concrete actions ("monitor CI pipeline test results, triage CI test failures across ADO pipelines, or generate CI test monitoring reports"). This matches anchor 4 (several specific actions, minor gaps) — not 3, since more than 1–2 actions are given, and not 5, since body capabilities like GitHub issue matching and regression bisecting are unmentioned.

4 / 5

Completeness

Both questions are explicitly answered: what = "Monitors .NET runtime CI test pipelines on Azure DevOps", 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" — three concrete trigger phrases. This matches anchor 5 (explicit what AND when with concrete triggers) and is not 4, where the when would be less specific.

5 / 5

Trigger Term Quality

Natural phrases users would say are present — "CI pipeline", "test results", "test failures", "triage", "monitor", "reports" — with the "Azure DevOps"/"ADO" synonym pair covering both forms. Good coverage but a few natural terms are missing (e.g., "build failures", "flaky tests"), so anchor 4 rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

".NET runtime CI test pipelines on Azure DevOps" carves out a clear niche anchored by project (".NET runtime") and platform ("Azure DevOps"/"ADO") qualifiers, so it would not fire for generic CI, build, or document skills. Minimal conflict risk matches anchor 5; it is not 4 because the qualifiers leave no meaningful overlap with closely related skills.

5 / 5

Total

18

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 9 missing

Warning

referenced_paths_exist

Referenced path issues: 34 missing

Warning

Total

14

/

16

Passed

Repository

dotnet/runtime

Path

.github/skills/ci-pipeline-monitor/SKILL.md

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.