CtrlK
BlogDocsLog inGet started
Tessl Logo

045-planning-azure-devops

Use when you need Azure DevOps CLI guidance to verify installation, configure organization and project context, discover work item IDs by optional WIQL filters, and execute safe work-item create/update operations. Uses an interactive install gate - if `az` or the Azure DevOps extension is missing, ask whether to show installation guidance before any work item commands. This should trigger for requests such as Azure DevOps work item list; List Azure Boards work item IDs; Azure DevOps WIQL query; Azure DevOps CLI planning workflow. Part of Plinth Toolkit

75

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The content delivers actionable, executable Azure DevOps CLI guidance with a clearly sequenced interactive workflow and a clean single-level reference for detail. The only weakness is moderate repetition of the install-gate directive across sections, which costs some token efficiency.

Suggestions

Consolidate the interactive install-gate instructions into one authoritative section and cross-reference it from the Workflow/Constraints lists to reduce repetition and save tokens.

Move the bulk of the detailed Step 1 install guidance (per-OS commands and the stop->ask->wait dialog) into the reference file, keeping SKILL.md to a concise gate summary plus the link.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes competence, but the interactive install-gate instruction is restated across the intro, Constraints, and Workflow sections (e.g. 'stop, ask whether the user wants installation guidance, wait'), adding repetition that could be tightened.

2 / 3

Actionability

It provides fully executable commands such as 'az boards work-item create --type "User Story" --title "Add feature placeholder"' and 'az boards work-item update --id 123 --state "Active"', plus concrete install and config commands that are copy-paste ready.

3 / 3

Workflow Clarity

The steps are explicitly sequenced with validation checkpoints: an interactive stop->ask->wait install gate, authentication/defaults verification before private operations, and confirmation of target ID before destructive or state-changing actions.

3 / 3

Progressive Disclosure

SKILL.md acts as a concise overview with a single well-signaled one-level-deep reference (references/045-planning-azure-devops.md) that exists in the bundle, keeping navigation shallow and organized.

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.

The description is specific, trigger-rich, complete, and clearly scoped to an Azure DevOps work-item ID niche. It opens with an explicit 'Use when' clause and lists natural trigger phrases alongside concrete capabilities.

DimensionReasoningScore

Specificity

The description enumerates concrete actions: 'verify installation, configure organization and project context, discover work item IDs by optional WIQL filters, and execute safe work-item create/update operations', listing multiple specific actions rather than vague language.

3 / 3

Completeness

It answers both 'what' (ID discovery, WIQL, create/update operations) and 'when' via an explicit 'Use when...' clause followed by concrete trigger scenarios, so neither half is missing or only implied.

3 / 3

Trigger Term Quality

It includes natural user phrases such as 'Azure DevOps work item list', 'List Azure Boards work item IDs', 'Azure DevOps WIQL query', and 'Azure DevOps CLI planning workflow' that a user would plausibly say.

3 / 3

Distinctiveness Conflict Risk

The Azure DevOps Boards / WIQL / work-item ID niche is specific with distinct triggers, making it unlikely to fire for unrelated 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.

Repository
jabrena/plinth
Reviewed

Table of Contents

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.