CtrlK
BlogDocsLog inGet started
Tessl Logo

pipelines-health-check

Check health of MSBuild CI pipelines, VS repo PR insertion statuses, and VMR codeflow PRs. Use when asked about pipeline health, build failures, infrastructure issues, CI status, insertion PR status, VMR codeflow status, or for periodic health monitoring.

70

Quality

86%

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

78%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 thorough, highly actionable runbook with a clear phased workflow and concrete commands. The main weaknesses are repeated content (notably WorkIQ install steps) and heavy inlining of subagent/troubleshooting material that would benefit from reference files.

Suggestions

Move the large subagent prompt-template blocks (Phase 2) and the Troubleshooting section into a references/ file (e.g. SUBAGENT_TEMPLATES.md, TROUBLESHOOTING.md) and link to them from the body, keeping SKILL.md as an overview.

De-duplicate the WorkIQ install instructions: state them once in Prerequisites and reference that single source from Phase 2 and Troubleshooting instead of repeating the full npm install block.

Add an explicit re-validation / retry checkpoint for Phase 2 (e.g., what to do when a subagent returns inconclusive results) to round out the workflow feedback loop.

DimensionReasoningScore

Conciseness

Mostly efficient with executable commands, tables, and subagent templates that earn their tokens, but WorkIQ install instructions are repeated in three places and a few failure-category lists recur, which could be trimmed.

4 / 5

Actionability

Fully executable guidance throughout: concrete PowerShell invocations, specific Azure DevOps URLs and pipeline IDs, exact table schemas, and copy-paste-ready subagent prompts with real commands.

5 / 5

Workflow Clarity

Clear Phase 1→2→3 sequence with an explicit 'no problems → stop, do not proceed to Phase 2' checkpoint and parallel subagent dispatch; minor gaps in that no re-validation loop is specified if subagents return inconclusive results.

4 / 5

Progressive Disclosure

Good sectioning and clearly signaled one-level references to external skills, but no bundle files are provided so the ~140-line subagent prompt templates and troubleshooting content are fully inlined rather than split into reference files.

3 / 5

Total

16

/

20

Passed

Description

95%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, well-targeted description that clearly states capabilities and provides rich, natural trigger phrases. The only minor weakness is that the action verbs stay at a 'check' level rather than enumerating the deeper investigation/diagnosis actions the skill actually performs.

DimensionReasoningScore

Specificity

Names the domain plus three concrete actions ('Check health of MSBuild CI pipelines, VS repo PR insertion statuses, and VMR codeflow PRs'), but the verbs stay at the 'check' level without enumerating deeper operations, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (check pipeline/insertion/codeflow health) and when, with a concrete 'Use when asked about...' clause listing concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms and variations ('pipeline health, build failures, infrastructure issues, CI status, insertion PR status, VMR codeflow status, periodic health monitoring') that a user would naturally say.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (MSBuild CI, VS insertion PRs, VMR codeflow) with distinct, domain-specific triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 missing

Warning

Total

15

/

16

Passed

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