CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-devops

Access Azure DevOps resources (PRs, builds, pipelines, releases, variable groups) for the Cupix organization. TRIGGER when: user pastes a dev.azure.com URL; user mentions Azure DevOps, ADO, az pr, az pipeline, build status, release status, or deploy status for Cupix projects; user asks about PR reviews, build logs, pipeline runs, or release progress. SKIP: general git questions not about Azure DevOps; GitHub-only workflows.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

83%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 comprehensive executable commands and clear per-resource structure, weakened only by minor verbosity in the token-handling prose and the absence of explicit validation checkpoints for write/run operations.

Suggestions

Tighten the Token Caching and Error Handling prose — drop reassurance lines like 'The token command is fast (~200ms) so there's no performance concern' that add no actionable information.

Add an explicit validation/retry checkpoint for write and run operations (e.g. after `az pipelines run` or `az repos pr create`, verify status before reporting success).

Consider splitting the per-resource REST API detail (releases, variable groups, build logs) into a reference file referenced one level deep, leaving SKILL.md as a concise overview.

DimensionReasoningScore

Conciseness

The body is mostly lean — commands and field lists are direct and assume Claude's competence — but a few lines restate known facts (e.g. 'The token command is fast (~200ms) so there's no performance concern', 'Always get a fresh token before calling the vsrm endpoint') that could be trimmed slightly.

4 / 5

Actionability

It provides fully executable, copy-paste-ready az and curl commands for every resource type, with specific jq filters, parameter extraction guidance, and concrete key field names covering the common cases.

5 / 5

Workflow Clarity

Multi-step log-fetching flows are clearly sequenced (get token → get timeline → match task id → fetch log) with numbered steps, but there is no explicit validate/retry checkpoint for destructive or batch operations like pipeline runs or PR creation.

4 / 5

Progressive Disclosure

Content is well-organized into clearly signaled sections per resource type with a useful URL-parsing table, but all reference material is inlined in SKILL.md with no bundle files to split the per-resource API detail into one-level-deep references.

4 / 5

Total

17

/

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.

This is an exemplary skill description: it states concrete capabilities, provides explicit and natural trigger terms, clearly answers both what and when, and includes an explicit skip clause that sharply bounds its activation scope.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions across distinct resource types — 'PRs, builds, pipelines, releases, variable groups' — plus concrete sub-tasks like 'PR reviews, build logs, pipeline runs, or release progress', giving comprehensive coverage.

5 / 5

Completeness

It explicitly answers both 'what' (Access Azure DevOps resources...) and 'when' via a clearly labeled 'TRIGGER when:' clause with concrete trigger phrases, plus a 'SKIP:' boundary clause.

5 / 5

Trigger Term Quality

It includes natural user phrases and synonyms users actually say ('Azure DevOps, ADO, az pr, az pipeline, build status, release status, or deploy status') plus the URL trigger, covering both conversational and file-paste triggers comprehensively.

5 / 5

Distinctiveness Conflict Risk

The Cupix organization scoping plus the explicit 'SKIP: general git questions not about Azure DevOps; GitHub-only workflows' clause carves a clear niche with minimal conflict risk against generic git/GitHub skills.

5 / 5

Total

20

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
olion500/skills
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.