cost-estimation
Forecast Azure spend and price planned resources or workloads. WHEN: "forecast Azure spending", "project next month cost", "compare forecast to my planning target", "how much will Azure cost", "estimate VM cost", "compare storage tiers", "compare Azure regions", "retail price", "EA rate card", "negotiated pricesheet". DO NOT USE FOR: configured budget health or alerts, bill analysis, cost spikes, rightsizing, or commitments.
소스 정보
- 저장소
- microsoft/skills
- 최근 소스 활동
- 2026년 9월 23일 11:05
- 감지된 SKILL.md 언어
- 영어
- 스타
- 3,063
- 포크
- 351
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
8 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- cost-estimation
- description
- Forecast Azure spend and price planned resources or workloads. WHEN: "forecast Azure spending", "project next month cost", "compare forecast to my planning target", "how much will Azure cost", "estimate VM cost", "compare storage tiers", "compare Azure regions", "retail price", "EA rate card", "negotiated pricesheet". DO NOT USE FOR: configured budget health or alerts, bill analysis, cost spikes, rightsizing, or commitments.
- license
- MIT
- metadata
- {"author":"Microsoft","version":"1.1.1"}
# Azure Cost Estimation
## Quick Reference
| Intent | Workflow | Primary tools |
|--------|----------|---------------|
| Forecast existing spend | [Cost forecast](references/cost-forecast/workflow.md) | `forecast_costs` |
| Price planned resources | [Pricing estimate](references/pricing-estimate.md) | Pricing tools |
## When to Use This Skill
Use for forecasts, pricing, and planning targets.
## MCP Tools
| Tool | Use |
|------|-----|
| `forecast_costs` | Forecast a scope. |
| `get_retail_prices` | Get public prices. |
| `start_pricesheet_download`, `get_pricesheet_status` | Get Enterprise Agreement (EA) or Microsoft Customer Agreement (MCA) prices. |
Fallback: [API mappings](references/tool-fallback.md).
## Workflow
1. Distinguish forecasts from hypothetical pricing.
2. Confirm scope, assumptions, period, region, OS, and currency.
3. Load the matching workflow and label every value type.
4. Never transform MCP results in a shell or interpreter; request tool-side
filtering or bounded follow-up queries.
## Error Handling
| Error | Action |
|-------|--------|
| Ambiguous meter | Ask for OS, term, tier, or usage. |
| Forecast unavailable | Explain the history requirement. |
| Pricesheet pending | Honor the returned polling interval. |
| Multiple currencies | Never combine currencies. |
| Server error | Retry once; then report the trace ID. |
GitHub에서 보기