Skills

Skill 8 of 53

Azure Advisor

Use Azure Advisor. WHEN: “show recommendations”, “top Advisor actions”, “prioritize recommendations”, “service retirements”, “update status”.

1 minute · 271 words · 3 sections

Install

$ npx skills add microsoft/azure-skills --skill azure-advisor

$ npx skills add microsoft/azure-skills

» /plugin marketplace add microsoft/azure-skills

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

Quick reference

Prefer Azure Advisor MCP tools. Use their current schemas for parameters and limits; discover unfamiliar parameters rather than inventing them.

Intent	Tool
Counts, totals, breakdowns, or distributions	`advisor_recommendation_summary`; non-prioritized, with the requested `group-by`
Broad priorities: top recommendations/actions, most important, critical, or fix-first advice	`advisor_recommendation_summary`; `prioritized: true` (automatically groups by recommendation type)
Individual recommendations or affected resources, including status-filtered records	`advisor_recommendation_list`; no prior summary required; for priority ordering within a known type, pass `recommendation-type-id` and `prioritized: true`
Complete, dismiss, postpone, or reactivate	`advisor_recommendation_update`
Browse recommendation types	`advisor_metadata_list`
Get one type by ID	`advisor_metadata_get`
Fix or remediate a recommendation	`azure-advisor-actionability` skill; it owns remediation tool calls and safeguards

Workflow

Reuse known scope and identifiers. Pass the requested count as top: groups for summary, records for list. “Critical” means priority, not an impact value.
For savings priorities, use category: "Cost". Top retirements use prioritized summary, not list, with sub-category: "ServiceUpgradeAndRetirement" and retirement-date: "le:<yyyy-MM-dd>" for on-or-before cutoffs.
For drill-downs, preserve scope and filters; pass the selected recommendation-type group’s actual GUID key as list recommendation-type-id. Retain prioritized: true after a prioritized summary and add category: "Cost" for a Cost type. Do not copy summary top to list.
If broad priorities require status or tracking-ids, explain that cross-type ranking is unavailable. Use filtered, non-prioritized list and explicitly label results unranked, not “top”. Never silently drop unsupported constraints.
Present returned data in server ranking order; disclose errors and truncation. Never count a capped list or filter capped results to simulate a server-side date query.

“Top actions” and “what should I fix first?” ask for prioritization advice, not permission to remediate.

Safety

Ask for and wait for user confirmation before recommendation-state updates. The actionability skill owns remediation safeguards.

About this skill

Trigger

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

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Licence: MIT
Source: .github/plugins/azure-advisor/skills/azure-advisor/SKILL.md

Colophon for this issue

Colophon

How this issue was made

Source

github.com/microsoft/azure-skills, branch main, last pushed 6 November 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

53 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 11 distinct layouts observed: .github/plugins/aks-skills/skills/*/SKILL.md, .github/plugins/azure-advisor/skills/*/SKILL.md, .github/plugins/azure-cost/skills/*/SKILL.md, .github/plugins/azure-kusto-graph-skills/skills/*/SKILL.md, .github/plugins/azure-local-skills/skills/*/SKILL.md, .github/plugins/foundry-iq-skills/skills/*/SKILL.md, skills/*/SKILL.md, skills/azure-kubernetes/*/SKILL.md, skills/microsoft-foundry/*/SKILL.md, skills/microsoft-foundry/models/deploy-model/*/SKILL.md, skills/microsoft-foundry/models/*/SKILL.md.

Duplicates collapsed

35 mirror copies folded into their canonical skill — republished for GitHub. Copies match on content hash and on position once a leading per-agent prefix is stripped, because the same skill is routinely shipped under a dozen agent directories with a dozen different hashes.

Issue colours

Resolved from a curated brand profile — hue 251°, chroma 0.167. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Removed “Azure Advisor”, a leading h1 that duplicated the skill title.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Microsoft, declaring 7 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /microsoft/azure-skills.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

Quick reference

Prefer Azure Advisor MCP tools. Use their current schemas for parameters and limits; discover unfamiliar parameters rather than inventing them.

Intent	Tool
Counts, totals, breakdowns, or distributions	`advisor_recommendation_summary`; non-prioritized, with the requested `group-by`
Broad priorities: top recommendations/actions, most important, critical, or fix-first advice	`advisor_recommendation_summary`; `prioritized: true` (automatically groups by recommendation type)
Individual recommendations or affected resources, including status-filtered records	`advisor_recommendation_list`; no prior summary required; for priority ordering within a known type, pass `recommendation-type-id` and `prioritized: true`
Complete, dismiss, postpone, or reactivate	`advisor_recommendation_update`
Browse recommendation types	`advisor_metadata_list`
Get one type by ID	`advisor_metadata_get`
Fix or remediate a recommendation	`azure-advisor-actionability` skill; it owns remediation tool calls and safeguards

Workflow

Reuse known scope and identifiers. Pass the requested count as top: groups for summary, records for list. “Critical” means priority, not an impact value.

For savings priorities, use category: "Cost". Top retirements use prioritized summary, not list, with sub-category: "ServiceUpgradeAndRetirement" and retirement-date: "le:<yyyy-MM-dd>" for on-or-before cutoffs.

For drill-downs, preserve scope and filters; pass the selected recommendation-type group’s actual GUID key as list recommendation-type-id. Retain prioritized: true after a prioritized summary and add category: "Cost" for a Cost type. Do not copy summary top to list.

If broad priorities require status or tracking-ids, explain that cross-type ranking is unavailable. Use filtered, non-prioritized list and explicitly label results unranked, not “top”. Never silently drop unsupported constraints.

Present returned data in server ranking order; disclose errors and truncation. Never count a capped list or filter capped results to simulate a server-side date query.

“Top actions” and “what should I fix first?” ask for prioritization advice, not permission to remediate.