azure-devops

Manage Azure DevOps projects, work items, repos, PRs, pipelines, wikis, test plans, security alerts, variable groups, environments/approvals, branch policies, and attachments. Use when user asks to: manage sprints, create/update work items, list repos, create PRs, run pipelines, search code, manage wiki pages, check security alerts, manage variable groups, approve deployments, or configure branch policies. Covers 13 domains with 99 tools via REST API.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

76%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 dense, highly actionable CLI command reference organized cleanly by domain with well-signaled one-level-deep references to the bundled scripts. Its main weaknesses are the absence of validation/verification checkpoints around destructive and batch operations and a large inline reference that could benefit from splitting.

Suggestions

Add validation/confirmation steps before destructive and batch operations (delete, complete-pr, abandon-pr, reject, batch-get, add-children) — e.g. list affected items first, confirm intent, then verify the resulting state — to lift workflow_clarity above the destructive-ops cap.

Provide explicit multi-step workflows with checkpoints for cross-domain processes (e.g. PR lifecycle: create-pr -> add-reviewer -> list-evaluations -> complete-pr) including a verify-after step, rather than only flat per-command listings.

Consider splitting the per-domain command reference into separate files under references/ linked from SKILL.md, keeping only quick-start and high-value examples inline, to reduce body length and improve progressive_disclosure.

Dimension	Reasoning	Score
Conciseness	The body is a lean command reference with no concept padding and assumes Claude's competence, but recurring flag-variant example pairs (e.g. 'list-prs' then 'list-prs --status completed --top 5') add tokens that could be tightened, so it sits above the mostly-efficient 3 but below the every-token-earns-its-place 5.	4 / 5
Actionability	Fully executable, copy-paste-ready CLI commands with real flags and argument examples covering common cases across all 13 domains, matching the top anchor precisely.	5 / 5
Workflow Clarity	The First-Time Setup section is sequenced, but destructive and batch operations (delete, complete-pr, abandon-pr, reject, batch-get, add-children) carry no validation or verification checkpoints, which per the rubric caps this dimension at 3 even though sections are otherwise clearly organized.	3 / 5
Progressive Disclosure	The 16 script bundle files are each referenced one-level-deep via clearly signaled section headers ('## Core (scripts/core.py)'), giving good structure and easy navigation; it does not reach 5 because the large inline command reference across 13 domains could be split into per-domain reference files.	4 / 5
	Total	16 / 20 Passed

Description

100%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, third-person description that explicitly states capabilities and provides a comprehensive 'Use when' trigger list across all 13 domains. It cleanly satisfies the what/when requirements with concrete, natural trigger phrases.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions across a comprehensive set of domains ('create/update work items, list repos, create PRs, run pipelines, search code ... approve deployments, configure branch policies'), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.	5 / 5
Completeness	Explicitly answers both 'what' (Manage Azure DevOps projects, work items, repos, PRs, pipelines ...) and 'when' (Use when user asks to: ...) with concrete trigger phrases, exactly matching the top anchor.	5 / 5
Trigger Term Quality	The 'Use when user asks to:' clause enumerates eleven natural trigger phrases users would actually say (manage sprints, create PRs, run pipelines, search code, approve deployments), giving comprehensive natural-term coverage; it does not fall to 4 because few common variations are missing.	5 / 5
Distinctiveness Conflict Risk	The Azure DevOps niche with domain-specific triggers (sprints, work items, pipelines, branch policies) is clearly distinct with minimal conflict risk against other skills; not the minor-overlap anchor at 4.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: sanjay3290/ai-skills
Path: skills/azure-devops/SKILL.md
Commit: 281d88d

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.