3.2k microsoft

azure-advisor-cost-optimization Skill

分析 Azure Advisor 的成本/闲置资源发现,并预校验删除安全性,包括 Service Groups。触发场景:"查找未使用的 Azure 资源"、"我付着钱但已不再使用的资源有哪些"、"闲置资源节省"、"历史闲置资源节省"、"这些闲置资源删除安全吗"。通用成本、其他子类及跨类别请求请使用 azure-advisor。

安装方式:把技能目录放入 ~/.claude/skills/(Claude Code)或在 claude.ai 设置中启用;也可复制右侧安装命令一键添加。

查看源码

技能指令原文(SKILL.md)

Azure Advisor Cost Optimization

Use existing Advisor tools only with category=Cost and sub-category=IdleResources.
Never substitute billing, inventory or runtime KQL. Preserve selected scope, type and tenant;
pass supplied identities unchanged.

Shared rules

Use only returned structured retail savings; MCP owns calculations. Never annualize,
reconstruct amounts from dates, or fall back to legacy annualSavingsAmount/savingsAmount
or raw pricing. Cost is accumulated Advisor cost, not monthly spend or yearly savings.
Completed reports use Realized savings.
Every monetary answer or proposal visibly shows Currency and Pricing basis:
from the calculated measure or its documented source. Missing amounts are Unavailable,
not zero; numeric zero stays zero. Preserve a known basis even when amounts are missing.
Potential savings depend on validating and deleting eligible resources. Estimates do not
establish inactivity or safe deletion and never authorize remediation.

Workflow

Before each flow, read its matching references below, including when using supplied results.
Before scoped calls, read Scope resolution.
Reuse already loaded references.
If a required file is unavailable, report it and stop the affected flow.

Use the matching scenario guidance; Reference index.

Quick reference

| Flow | Required reference |
|---|---|
| Discovery and type expansion | Workflow |
| Counts, savings field mapping and pricing-source interpretation | Output and savings |
| Tables and selected resources | Table format |
| Completed/historical reports | Lifecycle |
| State changes | State updates |
| Selection/remediation handoff | Selection |
| Explicit prevalidation/safety checks | Selection |
| Filters/errors | Tools and recovery |
| Routing examples | Examples |

Response guidance

Use shared headings and column order across models, with documented scope/lifecycle variations.
Visibly show results/proposals before dependent questions; reasoning, tool output or text
inside ask_user does not count. Ask directly for missing input.