azure-pipelines

Use when validating Azure DevOps pipeline changes for the VS Code build. Covers queueing builds, checking build status, viewing logs, and iterating on pipeline YAML changes without waiting for full CI runs.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 highly actionable, well-sequenced command skill, but it is token-heavy due to repeated command paths and a redundant workflows section, and it does not split its large reference material across bundle files.

Suggestions

Introduce a short alias for the long 'node .github/skills/azure-pipelines/azure-pipeline.ts' invocation (e.g., define it once and refer to it) to remove ~30 repetitions and tighten conciseness.

Collapse or prune the 'Common Workflows' section, which re-lists queue/status/cancel commands already documented above, keeping only workflows that combine steps in a new way.

Move the full product-build parameter table and/or troubleshooting into reference files under references/ and link to them, so the overview stays lean and the signaled bundle structure is real.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command reference and parameter tables, but the 'Common Workflows' section restates queue/status/cancel examples already shown and the full 'node .github/skills/azure-pipelines/azure-pipeline.ts' path repeats ~30 times; could be tightened with a short alias.	2 / 3
Actionability	Fully executable copy-paste commands plus detailed parameter tables with defaults and allowed values, matching the copy-paste-ready anchor.	3 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with explicit checkpoints — cancel obsolete builds before queueing, a polling/`--watch` feedback loop, and a `--dry-run` guard on the destructive cancel operation.	3 / 3
Progressive Disclosure	Content is a single monolithic file with the large parameter table and troubleshooting inline, and the only signaled reference ('./azure-pipeline.ts') has no corresponding bundle file present to verify.	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 with an explicit 'Use when' trigger and a concrete enumeration of supported actions, well-scoped to a distinct niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'queueing builds, checking build status, viewing logs, and iterating on pipeline YAML changes' — matching the multi-action anchor rather than the single-domain score 2.	3 / 3
Completeness	Explicitly answers both 'what' ('Covers queueing builds...') and 'when' ('Use when validating Azure DevOps pipeline changes for the VS Code build'), so it is not capped at 2 for a missing trigger clause.	3 / 3
Trigger Term Quality	Natural user-facing terms ('Azure DevOps pipeline changes', 'VS Code build', 'build status', 'logs', 'pipeline YAML') cover what a user would actually say, beyond jargon-only or partial coverage.	3 / 3
Distinctiveness Conflict Risk	Scoped to Azure DevOps pipeline validation for the VS Code build — a clear niche unlikely to fire for unrelated skills.	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: 3 missing	Warning

	Total	15 / 16 Passed

Repository: posit-dev/positron
Path: .github/skills/azure-pipelines/SKILL.md
Commit: b87c504

Reviewed: 2 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.