Name: azure-devops
Rating: 55.2 (1 reviews)
Author: membranedev

azure-devops

Azure DevOps integration. Manage data, records, and automate workflows. Use when the user wants to interact with Azure DevOps data.

Quality

62%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-devops/SKILL.md

Quality

Content

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

The body is highly actionable with concrete commands and a well-sequenced, validated connection workflow, but it opens with conceptual padding Claude does not need. Removing the introductory product-description paragraph would improve token efficiency.

Suggestions

Delete or trim the opening "Azure DevOps is a suite of cloud-based services..." paragraph; Claude already knows what Azure DevOps is.

Remove filler sentences like "Use action names and parameters as needed" that add no executable guidance.

Consider extracting the proxy flags table and clientAction state details into a reference file to keep SKILL.md lean.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("Azure DevOps is a suite of cloud-based services... It provides features like version control, CI/CD...") explains a concept Claude already knows, and filler like "Use action names and parameters as needed" pads the doc, matching the mostly-efficient-but-includes-unnecessary-explanation anchor.	3 / 5
Actionability	Concrete executable commands abound (npm install, membrane login, connection ensure, action list/run, request with a flags table), with only minor gaps like the CONNECTION_ID/QUERY/actionId placeholders, matching the mostly-executable-guidance anchor.	4 / 5
Workflow Clarity	The connection flow is a clear sequence (install → login → ensure → poll for READY) with explicit checkpoints and a feedback loop (handle CLIENT_ACTION_REQUIRED then re-poll, check CONFIGURATION_ERROR), matching the clear-sequence-with-most-checkpoints anchor.	4 / 5
Progressive Disclosure	The single SKILL.md is well organized into Overview, Install, Authentication, Connecting, Searching, Running actions, Proxy, and Best practices with no nested references; it exceeds 50 lines so the simple-skill exception does not apply, but structure is good with only minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

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

The description cleanly identifies a distinct product niche and includes an explicit use-when trigger, but its capability list is generic rather than naming Azure DevOps' actual features. Tightening the actions to concrete terms (work items, pipelines, repos) would lift specificity and trigger quality.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Azure DevOps capabilities such as work items, queries, pipelines, repositories, and pull requests.

Add natural trigger variations users say, e.g. "Use when the user mentions Azure DevOps, ADO, Boards, Repos, or Pipelines."

Keep the existing explicit "Use when..." clause — it is the strongest part of the description.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Azure DevOps integration") but its actions — "Manage data, records, and automate workflows" — are generic verbs rather than concrete capabilities like work items, pipelines, or repos; it matches the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	It has both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Azure DevOps data"), but the "what" is generic rather than concrete trigger phrases, so it stops short of the level-5 anchor.	4 / 5
Trigger Term Quality	"Azure DevOps" is a strong natural keyword and "Use when the user wants to interact with Azure DevOps data" gives a clear trigger phrase, but common variations/synonyms (ADO, Boards, Repos, Pipelines, work items) are missing, matching the anchor for some relevant keywords with gaps.	3 / 5
Distinctiveness Conflict Risk	"Azure DevOps integration" is a clear, product-specific niche with a distinct trigger, but the generic action list ("manage data, records, automate workflows") creates minor overlap risk with other data-management integrations, matching the mostly-distinct anchor rather than the minimal-conflict one.	4 / 5
	Total	13 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/azure-devops/SKILL.md
Commit: f484c82

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.