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

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

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

Highly actionable with executable commands and clear workflows, but token efficiency and file structure hold it back: command examples are repeated across sections and large reference material sits inline instead of a separate file.

Suggestions

Move the 20-row product-build parameter table (and the per-command option tables) into a reference file (e.g. references/parameters.md) and link to it, keeping SKILL.md as an overview.

Collapse the "Common Workflows" section into brief scenario pointers that reuse the command forms already documented, instead of re-listing full command blocks.

Add an explicit error-recovery step to the testing workflow (e.g. on a failed build, download the failing log, fix the YAML, then re-queue) to close the workflow-clarity feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no concept-fluff, but the "Common Workflows" section repeats queue/cancel/status commands already shown in the dedicated sections, adding redundant tokens; could be tightened to a 4.	3 / 5
Actionability	Copy-paste-ready bash commands throughout, concrete parameter examples with allowed values, and full option tables cover the common cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	Clear sequenced workflows with status polling and an explicit cancel-before-queue checkpoint; not a 5 because the error-recovery feedback loop (what to do when a queued build fails) is only implied via troubleshooting.	4 / 5
Progressive Disclosure	Section structure is clean and the azure-pipeline.ts reference is clearly signaled, but ~320 lines with a 20-row inlined product-build parameter table and no separate reference file leaves reference content inline, matching the "could be better organized" anchor.	3 / 5
	Total	15 / 20 Passed

Description

92%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 precise, third-person description that gives both a clear trigger and a concrete action list with minimal conflict risk. Keyword coverage is strong but lacks a few synonyms/file extensions, keeping trigger_term_quality at 4.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions ("queueing builds, checking build status, viewing logs, and iterating on pipeline YAML changes"), matching the comprehensive-coverage anchor; not a 4 because coverage is broad rather than a minor gap.	5 / 5
Completeness	Explicitly answers both — "Use when validating Azure DevOps pipeline changes for the VS Code build" (when) and "Covers queueing builds, checking build status, viewing logs..." (what) — matching the anchor with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms a user would say are present ("Azure DevOps pipeline changes", "VS Code build", "CI runs", "pipeline YAML"), but synonyms/extensions like ".yml" or "Azure Pipelines" are absent, so it sits below the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	A narrow niche (VS Code Azure DevOps pipeline validation) with distinct triggers and minimal overlap risk; clearly not the broad-overlap anchors 3-4.	5 / 5
	Total	19 / 20 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: 75a1182

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