azure-advisor Skill
获取 Azure Advisor 建议。适用场景:"show Advisor recommendations"、"service retirements"、"update recommendation status"。不要用于修复或整改(请用 azure-advisor-actionability)。
安装方式:把技能目录放入 ~/.claude/skills/(Claude Code)或在 claude.ai 设置中启用;也可复制右侧安装命令一键添加。
技能指令原文(SKILL.md)
Azure Advisor
Prefer Advisor MCP tools over Resource Graph or generic ARM calls.
Reuse supplied scope and identifiers; ask only for missing input.
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 one recommendation-type-ids array entry 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
- For unused-resource discovery, including "what are we paying for that is no longer
being used", or combined category=Cost and sub-category=IdleResources, load
azure-advisor-cost-optimization first. It owns scope, sequencing and response templates;
broad discovery must not skip to resource details.
- Generic/prioritized Cost outside IdleResources, cross-category and other requests stay here.
Preserve requested filters; never silently add IdleResources.
- Before generic calls or reporting, read Workflow.
- For remediation, load
azure-advisor-actionability; it owns execution safeguards.
- Reuse known scope and identifiers. Pass the requested count as
top: groups for summary, records for list. "Critical" means priority, not animpactvalue. - For savings priorities, use
category: "Cost". Top retirements use prioritized summary, not list, withsub-category: "ServiceUpgradeAndRetirement"andretirement-date: "le:"for on-or-before cutoffs. - For drill-downs, preserve scope and filters; pass the selected recommendation-type group's actual GUID
keyas the sole entry in listrecommendation-type-ids. Retainprioritized: trueafter a prioritized summary and addcategory: "Cost"for a Cost type. Do not copy summarytopto list. - If broad priorities require
statusortracking-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.
On every model, visibly present results/proposals before dependent questions.
Missing data stays Unavailable, not zero.