azure-advisor
Use Azure Advisor. WHEN: "show recommendations", "top Advisor actions", "prioritize recommendations", "service retirements", "update status". Unused-resource discovery and Cost/IdleResources requests use azure-advisor-cost-optimization; generic Cost and cross-category requests stay here. DO NOT USE FOR: fixes (use azure-advisor-actionability).
- License 许可
- MIT
- 所属仓库
- microsoft/skills
- 最近更新
- 2026-11-14
- Stars
- ★ 3.2k
- Forks
- 368
01 前言 Front Matter
- name
- azure-advisor
- license
- MIT
- metadata
- { "author": "Microsoft", "version": "1.0.3" }
- description
- Use Azure Advisor. WHEN: "show recommendations", "top Advisor actions", "prioritize recommendations", "service retirements", "update status". Unused-resource discovery and Cost/IdleResources requests use azure-advisor-cost-optimization; generic Cost and cross-category requests stay here. DO NOT USE FOR: fixes (use azure-advisor-actionability).
02 资源文件 1
- 参考文档references/workflow.md4.1 KB
03 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=Costandsub-category=IdleResources, loadazure-advisor-cost-optimizationfirst. 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:<yyyy-MM-dd>"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.
04 同仓库更多 Skills
azure-advisor-cost-optimization
Analyze Azure Advisor Cost/IdleResources findings and prevalidate deletion safety, including Service Groups. WHEN: "find unused Azure resources", "what resources am I paying for but no longer using", "idle-resource savings", "historical idle-resource savings", "are these idle resources safe to delete". Generic Cost, other subcategories, and cross-category requests use azure-advisor.
skill-creator
Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating existing skills.
podcast-generation
Generate AI-powered podcast-style audio narratives using Azure OpenAI's GPT Realtime Mini model via WebSocket. Use when building text-to-speech features, audio narrative generation, podcast creation from content, or integrating with Azure OpenAI Realtime API for real audio output. Covers full-stack implementation from React frontend to Python FastAPI backend with WebSocket streaming.
microsoft-docs
Understand Microsoft technologies by querying official documentation. Use whenever the user asks how something works, wants tutorials, needs configuration options, limits, quotas, or best practices for any Microsoft technology (Azure, .NET, M365, Windows, Power Platform, etc.)—even if they don't mention "docs." If the question is about understanding a concept rather than writing code, this is the right skill.
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP), Node/TypeScript (MCP SDK), or C#/.NET (Microsoft MCP SDK).
kql
KQL language expertise for writing correct, efficient Kusto Query Language queries. Covers syntax gotchas, join patterns, dynamic types, datetime pitfalls, regex patterns, serialization, memory management, result-size discipline, and advanced functions (geo, vector, graph). USE THIS SKILL whenever writing, debugging, or reviewing KQL queries — even simple ones — because the gotchas section prevents the most common errors that waste tool calls and cause expensive retry cascades. Trigger on: KQL, Kusto, ADX, Azure Data Explorer, Fabric Real-Time Intelligence, EventHouse, Log Analytics, log analysis, data exploration, time series, anomaly detection, summarize, where clause, join, extend, project, let statement, parse operator, extract function, any mention of pipe-forward query syntax.