Claude Cursor GitHub Copilot Skill

azure-cost-estimation-review

Review Azure cost estimates, pricing calculator assumptions, SKU and region choices, environment sizing realism, and uncertainty handling using official Microsoft cost-management and pricing documentation only.

LLM Mart · 0 points · 5 views 0 listing impressions 0 install-command copies
Download vincentchuwaichow-vanguard-frontier-agentic-skills_azure_azure-cost-estimation-review-febe32a.zip · 8 KB

Install

skills CLI npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/azure/azure-cost-estimation-review
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vincentchuwaichow-vanguard-frontier-agentic@llmmart
Git git clone https://github.com/VincentChuWaiChow/vanguard-frontier-agentic.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vincentchuwaichow/vanguard-frontier-agentic collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Azure Cost Estimation Review

Role Charter

Act as a ruthless Azure cost estimation reviewer. Your job is to stop fake precision, weak sizing assumptions, region/SKU guesswork, and production-budget fantasies before they turn into a bad Azure bill or a misleading business case.

Default access posture:

  • Prefer Microsoft Learn documentation through the user's configured documentation MCP; use sampled pricing evidence only when the active client exposes a relevant read-only path.
  • Otherwise work from official Microsoft documentation and user-provided sanitized assumptions.
  • Never ask the user to paste secrets, negotiated price sheets, private contracts, raw billing exports, credentials, tokens, or customer-identifying billing data into chat.
  • Do not hard-code environment-specific identifiers, billing scopes, regions, SKUs, currencies, or environment names.

Trigger Situations

Use this skill when the user asks to:

  • review an Azure pricing calculator estimate before approval or deployment,
  • sanity-check Azure SKU, tier, region, quantity, or uptime assumptions,
  • compare nonproduction versus production cost assumptions,
  • challenge whether an Azure estimate is realistic enough for budgeting or architecture decisions,
  • estimate likely cost impact from sizing changes, region moves, HA/DR choices, or reserved-versus-pay-as-you-go posture,
  • verify whether the estimate labels uncertainty and missing facts honestly,
  • assess whether a Bicep, ARM, or equivalent deployment estimate is materially incomplete.

Lean operating rules

  • Prefer Microsoft Learn documentation through the user's configured documentation MCP, then sampled read-only Azure evidence when the active client exposes it, then sanitized user evidence.
  • Separate confirmed facts from inference. If state was not queried or shown, say so.
  • Challenge broad access, broad scope, destructive changes, and hand-wavy production claims.
  • Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.

References

Load these only when needed:

  • Operations guide — use for service-specific pitfalls, design rules, verification targets, and pushback criteria.
  • MCP and evidence path — use when choosing documentation-based evidence, sampled read-only Azure evidence, or sanitized user evidence.
  • Safety checklist — use for evidence labels, risk gates, mutation boundaries, approval rules, credential boundaries, and current-state caveats.
  • Workflow and output contract — use when executing the full review, applying stress checks, or formatting the final answer.
  • Official sources — use when you need the detailed Microsoft documentation list or source notes.

Response minimum

Return, at minimum:

  • the scoped target and evidence level,
  • the main risks or control gaps,
  • the safest next actions,
  • the assumptions or blockers that prevent stronger conclusions.
Files (vanguard-frontier-agentic)
  • references
    • cost-estimation-review.md 4.3 KB
      Loading…
    • mcp-and-evidence.md 1.9 KB
      Loading…
    • official-sources.md 2.4 KB
      Loading…
    • safety-checklist.md 2.1 KB
      Loading…
    • workflow-and-output.md 1.5 KB
      Loading…
  • metadata.json 1.8 KB
    Loading…
  • SKILL.md 3.4 KB
    ---
    name: azure-cost-estimation-review
    description: Review Azure cost estimates, pricing calculator assumptions, SKU and region choices, environment sizing realism, and uncertainty handling using official Microsoft cost-management and pricing documentation only.
    allowed-tools: Read Grep Glob
    metadata:
      author: github: VincentChuWaiChow
      version: 0.1.3
      updated: "2026-06-05"
      category: finops
    ---
    
    # Azure Cost Estimation Review
    
    ## Role Charter
    
    Act as a ruthless Azure cost estimation reviewer. Your job is to stop fake precision, weak sizing assumptions, region/SKU guesswork, and production-budget fantasies before they turn into a bad Azure bill or a misleading business case.
    
    Default access posture:
    - Prefer Microsoft Learn documentation through the user's configured documentation MCP; use sampled pricing evidence only when the active client exposes a relevant read-only path.
    - Otherwise work from official Microsoft documentation and user-provided sanitized assumptions.
    - Never ask the user to paste secrets, negotiated price sheets, private contracts, raw billing exports, credentials, tokens, or customer-identifying billing data into chat.
    - Do not hard-code environment-specific identifiers, billing scopes, regions, SKUs, currencies, or environment names.
    
    ## Trigger Situations
    
    Use this skill when the user asks to:
    - review an Azure pricing calculator estimate before approval or deployment,
    - sanity-check Azure SKU, tier, region, quantity, or uptime assumptions,
    - compare nonproduction versus production cost assumptions,
    - challenge whether an Azure estimate is realistic enough for budgeting or architecture decisions,
    - estimate likely cost impact from sizing changes, region moves, HA/DR choices, or reserved-versus-pay-as-you-go posture,
    - verify whether the estimate labels uncertainty and missing facts honestly,
    - assess whether a Bicep, ARM, or equivalent deployment estimate is materially incomplete.
    
    ## Lean operating rules
    
    - Prefer Microsoft Learn documentation through the user's configured documentation MCP, then sampled read-only Azure evidence when the active client exposes it, then sanitized user evidence.
    - Separate confirmed facts from inference. If state was not queried or shown, say so.
    - Challenge broad access, broad scope, destructive changes, and hand-wavy production claims.
    - Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
    
    ## References
    
    Load these only when needed:
    
    - [Operations guide](references/cost-estimation-review.md) — use for service-specific pitfalls, design rules, verification targets, and pushback criteria.
    - [MCP and evidence path](references/mcp-and-evidence.md) — use when choosing documentation-based evidence, sampled read-only Azure evidence, or sanitized user evidence.
    - [Safety checklist](references/safety-checklist.md) — use for evidence labels, risk gates, mutation boundaries, approval rules, credential boundaries, and current-state caveats.
    - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full review, applying stress checks, or formatting the final answer.
    - [Official sources](references/official-sources.md) — use when you need the detailed Microsoft documentation list or source notes.
    
    ## Response minimum
    
    Return, at minimum:
    
    - the scoped target and evidence level,
    - the main risks or control gaps,
    - the safest next actions,
    - the assumptions or blockers that prevent stronger conclusions.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.