CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

azure-advisor

Use Azure Advisor recommendations. WHEN: "show Advisor recommendations", "service retirements", "update recommendation status". DO NOT USE FOR: fixes or remediation (use azure-advisor-actionability).

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/plugins/azure-advisor/skills/azure-advisor/SKILL.md

The canonical home for this skill is azure-advisor in microsoft/GitHub-Copilot-for-Azure

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.

The body is a model of token-efficient skill authoring: a tight intent-to-tool routing table, a short sequenced workflow with safety checkpoints for state-changing operations, and clean section organization. The only meaningful improvement would be a small example of tool invocation parameters to close the minor actionability gap.

DimensionReasoningScore

Conciseness

The body is a lean ~37 lines of table plus numbered steps with zero padding and no explanation of concepts Claude already knows; terse directives like "Never count a capped list" and "Resource-group scope requires a subscription" assume full competence. Every token earns its place, matching anchor 5.

5 / 5

Actionability

The intent-to-tool table assigns concrete, specific tools for each intent (advisor_recommendation_summary for aggregates, advisor_recommendation_update for state changes), which is actionable guidance for an instruction-only skill. It falls short of anchor 5 only in lacking parameter or invocation examples (e.g., the expected scope format).

4 / 5

Workflow Clarity

A clear 4-step sequence with a checkpoint before the risky operation ("Confirm before recommendation-state updates") and an output-verification step ("Present only returned data, including truncation, access limitations, and errors"). There is no error-recovery/feedback loop, so it does not reach anchor 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external references; per the rubric's guideline, well-organized sections (Quick reference, Workflow, Safety) earn a 5, and the body has exactly that with no inlined content that belongs in separate files.

5 / 5

Total

18

/

20

Passed

Description

52%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 has excellent distinctiveness thanks to the explicit DO NOT USE FOR routing clause and an explicit WHEN clause with natural trigger phrases. Its main weakness is the vague 'what' — it never states the concrete capabilities (summarize, list, update recommendation states) that the skill body clearly supports.

Suggestions

Replace the generic 'Use Azure Advisor recommendations' with the concrete capabilities the skill supports, e.g. 'Retrieve Azure Advisor recommendation summaries, list individual recommendations and affected resources, browse recommendation metadata, and update recommendation status (complete, dismiss, postpone, reactivate)'.

Broaden trigger coverage with natural variations users would say, such as "Advisor score", "cost/security/reliability recommendations", "dismiss a recommendation", or "postpone a recommendation".

Fold the capability list and the trigger list into the canonical 'what. Use when...' shape so the 'what' is as explicit as the already-strong 'when'.

DimensionReasoningScore

Specificity

The description names the domain ("Use Azure Advisor recommendations") but the stated action is generic, with no concrete capabilities such as retrieving summaries, listing affected resources, or dismissing/postponing recommendations. It names the domain with minimal actions (anchor 2) rather than listing 1-2 concrete actions (anchor 3).

2 / 5

Completeness

The 'when' is explicit and concrete (a WHEN clause with trigger phrases plus a DO NOT USE FOR boundary), but the 'what' is vague — "Use Azure Advisor recommendations" barely states what the skill actually does. It exceeds anchor 2 (the 'when' is clearly present) but the weak 'what' keeps it below anchor 4.

3 / 5

Trigger Term Quality

The quoted triggers ("show Advisor recommendations", "service retirements", "update recommendation status") are natural user phrasings, but coverage is narrow with no synonyms or common variations such as "Advisor score", "cost/security recommendations", or "recommendation types". This matches 'some relevant keywords but missing common variations' more than 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

"DO NOT USE FOR: fixes or remediation (use azure-advisor-actionability)" explicitly de-conflicts against the most likely overlapping sibling skill, and the named product niche with distinct trigger phrases gives minimal conflict risk, matching anchor 5.

5 / 5

Total

13

/

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

microsoft/azure-skills

Path

.github/plugins/azure-advisor/skills/azure-advisor/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.