CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/azuredevops-bug-workflow

Authors and triages Bug work items in Azure DevOps Boards via the Work Item Tracking REST API (api-version 7.1) - Bug creation with JSON Patch, state transitions across New/Active/Resolved/Closed, and WIQL queries for triage queues and duplicate detection. Deep operational blocks (field-value fetch, PR / build artifact links, bulk close, az boards CLI, CI wiring) live in references/. Use when programmatically managing Azure DevOps Bug lifecycle states: creating from CI failures, triaging open defect queues, transitioning states in bulk, or attaching traceability links to builds and pull requests.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An actionable, well-structured skill with executable code, clear sequencing, validation checkpoints, and clean progressive disclosure into a single real reference file. The main weakness is mild redundancy — the inline-cited links are repeated in the References section and the worked example re-derives an already-shown WIQL query.

Suggestions

Drop the duplicated learn.microsoft link list from the References section (or keep only the ones not already cited inline) since each is already linked in its section — this tightens token usage.

In the Worked example, reuse wiql_search via a shared helper for the dedupe query rather than restating the full WIQL string, pointing to the Search-via-WIQL snippet instead.

Consider inlining a one-line validation note for bulk-close (e.g., 'confirm count before PATCH' ) rather than only deferring it to references, since batch destructive ops benefit from an explicit checkpoint in the main body.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no PDF-style concept padding), but the trailing References section re-lists the five learn.microsoft links already cited inline and the Worked example restates the WIQL query from the Search-via-WIQL section — tightenable redundancy that fits the 'mostly efficient but could be tightened' anchor rather than 3.

2 / 3

Actionability

Complete, executable Python functions (create_bug, set_state, wiql_search) with exact endpoints, JSON-Patch bodies, headers, and a copy-paste worked example — fully executable rather than pseudocode.

3 / 3

Workflow Clarity

Sequenced How-to-use (1–4) and Worked-example (1–4) flows with explicit validation checkpoints: dedupe-before-create guard, optimistic-concurrency 'test /rev' op, $top-truncation check guidance, and raise_for_status calls.

3 / 3

Progressive Disclosure

SKILL.md is a clear overview with a well-signaled, one-level-deep reference to the verified references/azure-devops-wit-reference.md (linked from How-to-use, WIQL, Worked example, and References); advanced ops (field fetch, artifact links, bulk close, az CLI, CI wiring) are appropriately split out with no nested-reference chains.

3 / 3

Total

11

/

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 high-quality description: third-person, concrete capabilities, explicit 'Use when' triggers, and a clear niche that avoids sibling-skill conflicts. No vagueness or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Bug creation with JSON Patch', 'state transitions across New/Active/Resolved/Closed', 'WIQL queries for triage queues and duplicate detection', plus operational blocks (bulk close, artifact links, az CLI, CI wiring) — matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers what ('Authors and triages Bug work items ...') and when via a clear 'Use when programmatically managing Azure DevOps Bug lifecycle states:' clause with enumerated triggers.

3 / 3

Trigger Term Quality

Natural phrasing a user would say appears throughout: 'creating from CI failures', 'triaging open defect queues', 'transitioning states in bulk', 'attaching traceability links to builds and pull requests' — good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Scoped to 'Azure DevOps Boards via the Work Item Tracking REST API (api-version 7.1)' with distinct lifecycle-state triggers, clearly separable from the jira/linear/github sibling skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents