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

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%

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 health-check skill with a clear phased workflow and explicit validation gates. Its weaknesses are token efficiency — the body is long with some redundancy and verbose inline templates — and progressive disclosure, since everything lives inline in SKILL.md with no bundled reference files to offload detail into.

Suggestions

Trim the redundant opening paragraph (it restates the frontmatter description) and condense the verbose per-task bullet lists inside each subagent prompt template; keep the seed prompts lean since Claude can expand them.

Move the large subagent prompt templates into a bundled reference file (e.g. references/subagent-templates.md) referenced one level deep from SKILL.md, so SKILL.md stays an overview and progressive disclosure improves.

Relocate the "Reference Information" pipeline/URL tables and/or the Troubleshooting section into a separate reference file, reducing inline bulk while keeping the quick-start phases prominent in the main body.

Dimension	Reasoning	Score
Conciseness	The body is largely operational rather than padded with concept explanations, but at ~384 lines / 20KB it is not lean: the opening paragraph restates the frontmatter description, the subagent prompt templates are verbose, and several troubleshooting notes explain basics ("This is normal for newly created PRs. The checks take time to queue and run.") that could be tightened.	2 / 3
Actionability	It provides fully executable PowerShell commands with concrete script paths, specific Azure DevOps URLs, exact table field mappings, and copy-paste-ready WorkIQ query examples ("workiq ask -q \"Who owns the {failing service/task name} service...\""), matching the executable-and-copy-paste-ready anchor.	3 / 3
Workflow Clarity	A clear three-phase sequence (Collect → Investigate → Report) with explicit gating checkpoints — "If there are no problems, report ✅ ALL CLEAR ... and stop. Do not proceed to Phase 2" — a six-item problem checklist, and feedback loops (retry pipelines, re-analyze binlogs) satisfies the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	Sections are well organized, but the content is monolithic: the large subagent prompt templates and troubleshooting material are inline in SKILL.md, and the three referenced .ps1 scripts are not present in any bundle (no references/scripts/assets dirs), so it does not meet the one-level-deep, appropriately-split reference structure of the top anchor.	2 / 3
	Total	10 / 12 Passed

Description

100%

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, third-person description that concisely states concrete capabilities across three distinct targets and pairs them with a rich, explicit "Use when" trigger clause. It clearly answers both what the skill does and when to invoke it, and occupies a niche unlikely to collide with other skills.

Dimension	Reasoning	Score
Specificity	It lists multiple concrete, specific actions on named targets — "Check health of MSBuild CI pipelines, VS repo PR insertion statuses, and VMR codeflow PRs" — which matches the multiple-specific-actions anchor rather than the vague or partially-comprehensive anchors.	3 / 3
Completeness	It explicitly answers both what (check health of the three pipeline/PR types) and when (an explicit "Use when asked about..." clause with multiple triggers), satisfying the both-what-and-when anchor.	3 / 3
Trigger Term Quality	The "Use when asked about pipeline health, build failures, infrastructure issues, CI status, insertion PR status, VMR codeflow status, or for periodic health monitoring" clause gives good coverage of natural phrasings a developer would actually say.	3 / 3
Distinctiveness Conflict Risk	The MSBuild-CI / VS-insertion / VMR-codeflow niche is highly specific with distinct triggers, making conflict with other skills unlikely; it is written in third-person imperative voice with no first/second-person phrasing to penalize.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 5 missing	Warning

	Total	15 / 16 Passed

Repository: dotnet/msbuild
Path: .github/skills/pipelines-health-check/SKILL.md
Commit: c88db8e

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.