Name: azure-cost
Rating: 66.4 (1 reviews)
Author: microsoft

azure-cost

Azure cost management: query costs, forecast spending, optimize to reduce waste. WHEN: "Azure costs", "Azure bill", "cost breakdown", "how much am I spending", "forecast spending", "optimize costs", "reduce spending", "orphaned resources", "rightsize VMs", "cost spike", "reduce storage costs", "AKS cost". DO NOT USE FOR: deploying resources, provisioning, diagnostics, or security audits.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/plugins/azure-skills/skills/azure-cost/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, well-organized overview, but its progressive-disclosure promise is broken: most referenced detail files do not exist, and the body itself contains no executable steps or validation checkpoints for the destructive operations it routes to.

Suggestions

Ship the referenced bundle files (cost-query/workflow.md, cost-optimization/workflow.md, cost-forecast/workflow.md, the service-specific Redis/Storage pages, and the SDK reference) so the overview's links resolve.

Add at least one executable example in the body (e.g., a minimal az rest or REST call to Microsoft.CostManagement/query) so core tasks are actionable without the missing workflow files.

Include explicit validation/approval checkpoints for destructive optimization steps (rightsizing, orphaned-resource deletion) rather than deferring them entirely to absent files.

Dimension	Reasoning	Score
Conciseness	Lean ~35-line body of well-organized tables and reference data with no over-explanation of concepts Claude already knows; every section earns its place.	5 / 5
Actionability	Provides concrete API endpoints, scope patterns, and required roles, but no executable code/commands, and the actual step-by-step execution lives in workflow files that are not present, leaving key details missing.	3 / 5
Workflow Clarity	The routing table gives a clear intent-to-workflow entry sequence, but the actual multi-step workflows and validation checkpoints are delegated to missing files; for destructive/batch operations (rightsizing, orphaned-resource deletion) the in-body validation is absent, capping the score at 3.	3 / 5
Progressive Disclosure	The overview is well-signaled with one-level-deep references, but scored against the actual bundle structure 6 of 7 referenced files (all three workflows, both service files, and the SDK file) are missing, so navigation leads to dead ends and the disclosure does not function.	3 / 5
	Total	14 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that clearly states capabilities, provides comprehensive natural trigger phrases, and includes explicit use/non-use boundaries. The only minor weakness is that one capability phrase is slightly generic.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete actions ("query costs, forecast spending, optimize to reduce waste"), but "optimize to reduce waste" is comparatively generic, so it falls short of the comprehensive multi-action 5 anchor.	4 / 5
Completeness	Explicitly answers "what" (query costs, forecast, optimize) and "when" with concrete WHEN triggers, plus a DO NOT USE FOR boundary, matching the 5 anchor exactly.	5 / 5
Trigger Term Quality	Extensive natural trigger phrases users would actually say ("how much am I spending", "cost spike", "Azure bill") plus synonyms and service-specific terms ("rightsize VMs", "AKS cost"), matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Clear Azure-cost niche with distinct triggers and an explicit negative boundary ("DO NOT USE FOR: deploying resources, provisioning, diagnostics, or security audits"), minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 6 missing, 3 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: microsoft/azure-skills
Path: .github/plugins/azure-skills/skills/azure-cost/SKILL.md
Commit: 9d46511

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.