CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

discover-azure-skills

Searches the Azure skills catalog and recommends installable agent skills by matching an Azure task to skill metadata and plugin installation guidance. WHEN: before starting any task that involves an Azure or Microsoft-cloud service, product, or data source, when no currently loaded skill or tool already covers it.

Quality

83%

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

86%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 lean, well-structured instruction skill: the discovery workflow is sequenced with concrete GitHub API endpoints, and installation detail is properly deferred to real, one-level-deep reference files. The main improvement opportunities are adding explicit edge-case handling (no-match or API failure) and literal command examples for the API calls.

DimensionReasoningScore

Conciseness

The ~35-line body is lean and instruction-only: numbered steps, exact API URLs, and only necessary interpretation notes ("each entry whose `type` is `dir` is a plugin directory") plus a brief earned rationale ("a plugin's name may be different from its directory name"). No padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Every step includes concrete, ready-to-use endpoints ("https://api.github.com/repos/microsoft/azure-skills/contents/.github/plugins?ref=main" and templated raw URLs) plus result-interpretation rules, matching 'mostly executable guidance; concrete commands with minor gaps'. Not a 5 because no literal executable command form (e.g., curl/gh api invocation) or example response snippet is given, and the elimination criteria in step 3 are left to judgment.

4 / 5

Workflow Clarity

A clearly sequenced 5-step workflow (list plugins → list skills → filter by name then description → resolve plugin names → report with install instructions) where the two-pass name-then-description elimination acts as an implicit checkpoint, matching 'clear sequence with most checkpoints present; minor validation gaps'. Not a 5 because there is no explicit feedback loop or handling for edge states (API failure, no matching skills); not a 3 because the sequence and its checkpoints are better defined than the anchor-3 example.

4 / 5

Progressive Disclosure

The core discovery workflow stays inline while client-specific installation detail is split into three clearly labeled one-level-deep references ([Copilot CLI](./references/install/copilot-cli.md), [Claude Code](./references/install/claude-code.md), [Other](./references/install/other.md)), all of which exist in the bundle — matching the 'clear overview with well-signaled one-level-deep references; easy navigation' anchor.

5 / 5

Total

18

/

20

Passed

Description

75%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 description that explicitly covers both what the skill does and when to use it, with a distinct niche and good trigger terms. Minor gaps: no concrete user-utterance trigger phrases or specific Azure service-name examples, and the action list is slightly mechanism-flavored.

DimensionReasoningScore

Specificity

"Searches the Azure skills catalog and recommends installable agent skills by matching an Azure task to skill metadata and plugin installation guidance" names the domain plus several concrete actions (search, recommend, match, installation guidance), matching the 'several specific actions; minor gaps' anchor. Not a 5 because 'matching... to skill metadata and plugin installation guidance' is a mechanism description rather than a crisp, comprehensive action list.

4 / 5

Completeness

Both parts are explicit: the 'what' ("Searches the Azure skills catalog and recommends installable agent skills...") and an explicit 'WHEN:' clause ("before starting any task that involves an Azure or Microsoft-cloud service... when no currently loaded skill or tool already covers it"). Not a 5 because the when-clause states a task-level condition rather than concrete user-utterance trigger phrases (e.g., 'when the user mentions Azure...').

4 / 5

Trigger Term Quality

"Azure", "Microsoft-cloud service, product, or data source", and "task" give good keyword coverage including a synonym variation (Microsoft-cloud), matching the 'good keyword coverage; a few natural terms missing' anchor. Not a 5 because it lacks specific service-name variations users would naturally say (e.g., 'Azure Storage', 'Cosmos DB'); not a 3 because coverage goes well beyond a single generic keyword.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (Azure skill discovery/recommendation, not doing Azure work itself) and "when no currently loaded skill or tool already covers it" reduces overlap, matching 'mostly distinct; minor overlap risk'. Not a 5 because the broad trigger 'any task that involves an Azure or Microsoft-cloud service' can still fire alongside Azure-specific skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 3 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

microsoft/azure-skills

Path

.github/plugins/azure-skills/skills/discover-azure-skills/SKILL.md

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.