add-azuredevops

Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.

Quality

87%

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

82%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 tightly written, highly actionable skill body that leads Claude through a concrete six-step workflow with exact commands and targeted code fixes. The main improvement opportunity is adding an explicit build-fail recovery loop to elevate workflow clarity.

Suggestions

Add an explicit feedback loop in Step 5: 'If the build fails, fix the TypeScript errors and re-run npm run build until it passes before proceeding.'

De-duplicate the shared-instructions reference — link it once near the top rather than repeating it in Step 1.

Consider a brief verification step after the HttpRequest fix (e.g., run a sample WIQL query) to confirm the rename took effect before building.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence — no padding about what Azure DevOps or connectors are — with efficient BEFORE/AFTER diffs, though the shared-instructions link is repeated and the workflow overview line slightly duplicates the step headers.	4 / 5
Actionability	Guidance is fully executable: a concrete 'pa app add data-source' command, exact file paths for three files, complete BEFORE/AFTER snippets, a runnable HttpRequest example, and 'npm run build', covering the common cases copy-paste ready.	5 / 5
Workflow Clarity	Six steps are clearly numbered with an overview line and a build checkpoint ('Fix TypeScript errors before proceeding. Do NOT deploy yet.'), but there is no explicit build-fail → fix → rebuild feedback loop, leaving it just short of the score-5 anchor.	4 / 5
Progressive Disclosure	Content is well split into step sections with clearly signaled, one-level-deep references to shared files (shared-instructions.md, connector-reference.md) for cross-cutting detail, though this skill owns no bundle files of its own and the core fix content is necessarily inline.	4 / 5
	Total	17 / 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 strong, third-person description that crisply states both the skill's purpose and concrete trigger conditions with multiple specific actions. The only minor gap is keyword coverage of additional ADO surface area such as boards, repos, and pull requests.

Dimension	Reasoning	Score
Specificity	The description lists four concrete actions — 'querying work items, creating bugs, managing pipelines, or making ADO API calls' — giving comprehensive coverage of the skill's capabilities, matching the score-5 anchor.	5 / 5
Completeness	It explicitly states the what ('Adds Azure DevOps connector to a Power Apps code app') and the when ('Use when querying work items, creating bugs, managing pipelines, or making ADO API calls') with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	Natural phrases like 'querying work items', 'creating bugs', and 'managing pipelines' plus the 'ADO' synonym give good keyword coverage, but common variations such as 'boards', 'repos', or 'pull requests' are absent, so it falls just short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	The combination of 'Azure DevOps connector' within 'a Power Apps code app' carves a clear niche with distinct triggers, keeping conflict risk minimal.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 4 missing, 4 deeper-than-1-level	Warning

	Total	13 / 16 Passed

Repository: microsoft/power-platform-skills
Path: plugins/code-apps/skills/add-azuredevops/SKILL.md
Commit: 4c284ab

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.