CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

85%

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

77%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.

An exceptionally actionable, well-sequenced runbook whose main weaknesses are repetition (WorkIQ setup, build-error guidance) and monolithic structure — everything is inlined in one large SKILL.md while referenced script files are absent from the bundle.

Suggestions

Move the four subagent prompt templates and the troubleshooting details into files under references/ (e.g., references/subagent-templates.md, references/troubleshooting.md), keeping only a one-line pointer in SKILL.md.

Verify the three data-collection scripts (check-pipeline-health.ps1, check-vs-pr-status.ps1, check-vmr-codeflow.ps1) actually ship with the skill bundle at the referenced paths, since no scripts/ directory exists.

De-duplicate the WorkIQ install instructions — state them once and reference that section from the subagent template and troubleshooting entries.

DimensionReasoningScore

Conciseness

The body is densely operational with no concept re-teaching, but WorkIQ install instructions are repeated three times (prerequisites, subagent template, troubleshooting) and the "For build errors" guidance is duplicated across four prompt templates — more than minor trimming would fix.

3 / 5

Actionability

Guidance is fully executable: exact script paths and commands, concrete JSON field names for every table column, emoji mappings, pipeline IDs/URLs, and copy-paste-ready WorkIQ queries with working examples.

5 / 5

Workflow Clarity

Phase 1→2→3 is clearly sequenced with an explicit problem-detection checklist, a hard gate ("If there are no problems ... Do not proceed to Phase 2"), and a troubleshooting section providing feedback loops for each failure mode.

5 / 5

Progressive Disclosure

The single 385-line file inlines ~150 lines of subagent prompt templates and a long troubleshooting section that belong in reference files, and the three referenced PowerShell scripts (.github/skills/pipelines-health-check/*.ps1) are not present in the skill bundle, leaving dangling references.

3 / 5

Total

16

/

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 with an explicit what/when split, natural trigger terms, and a highly specific niche. It could list the investigation and root-cause-analysis capabilities it actually performs and add a few more natural trigger synonyms.

DimensionReasoningScore

Specificity

The description lists three concrete actions in a named domain ("Check health of MSBuild CI pipelines, VS repo PR insertion statuses, and VMR codeflow PRs"), but omits capabilities the body delivers (failure investigation, root-cause categorization, ownership lookup), leaving minor coverage gaps.

4 / 5

Completeness

It explicitly answers both what ("Check health of MSBuild CI pipelines, VS repo PR insertion statuses, and VMR codeflow PRs") and when ("Use when asked about pipeline health, build failures, ... or for periodic health monitoring") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Triggers like "pipeline health, build failures, infrastructure issues, CI status, insertion PR status" are phrases a user would naturally say, though common variations such as "is the build broken", "checks failing", or "red build" are missing.

4 / 5

Distinctiveness Conflict Risk

The MSBuild/VS-insertion/VMR-codeflow niche is unmistakable; these specific system names and triggers are unlikely to match any other skill.

5 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 missing

Warning

Total

15

/

16

Passed

Repository

dotnet/msbuild

Path

.github/skills/pipelines-health-check/SKILL.md

Revision

86743d0

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill