cost-governance
Govern Azure costs with budgets, alerts, tags, and policy restrictions. WHEN: "Azure budget health", "configured budget overrun", "list Azure budgets", "create Azure budget", "budget alerts", "budget coverage", "missing CostCenter tags", "allowed VM SKUs", "allowed Azure regions", "would this SKU be denied", "cost guardrails". DO NOT USE FOR: planning-target forecasts, bill investigations, pricing, rightsizing, or commitments.
73
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
W009: Direct money access capability detected (payment gateways, crypto, banking).
What this means
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
Why it was flagged
The skill documentation describes managing Azure budgets, cost guardrails, alerts, and tags (including tools like `create_budget`, `list_budgets`, and budget configuration). Under the core rules for Direct Financial Execution Authority, managing cloud infrastructure budgets (like Azure cloud spend budgets) falls under managing ad spend or cloud budgets/financial thresholds via specific administrative APIs. Specifically, the rule states: "Managing Ad Spend Budgets (specifically the API to update the budget, not just viewing ads)". Similarly, configuring and creating cloud cost budgets (`create_budget`) constitutes managing spend limits/budgets through a specialized API interface, qualifying it as a direct financial execution capability regarding cloud spend.
- Repository
- microsoft/GitHub-Copilot-for-Azure
- Commit
fcf2f3b
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.