agentleFS
MicrosoftKnown publishermicrosoft/azure-skills/.github/plugins/azure-advisor/skills/azure-advisor-cost-optimization/SKILL.md

azure-advisor-cost-optimization

Skill1.6k starsChanged 18 days agoMITView on GitHub

Analyze Azure Advisor Cost/IdleResources findings and prevalidate deletion safety, including Service Groups. WHEN: \"find unused Azure resources\", \"what resources am I paying for but no longer using\", \"idle-resource savings\", \"historical idle-resource savings\", \"are these idle resources safe to delete\". Generic Cost, other subcategories, and cross-category requests use azure-advisor.

2 other projects use a version of this, 1 of them edited.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 3 mentionsMay 2026: 0 mentionsJun 2026: 1 mentionJul 2026: 1 mentionAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 21 mentionsNov 2026: 24 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the microsoft/azure-skills repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about microsoft/azure-skills

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use existing Advisor tools only with category=Cost and sub-category=IdleResources.

    line 12
  2. Distinctive:

    Never substitute billing, inventory or runtime KQL.

    line 13
  3. Distinctive:

    Use only returned structured retail savings.

    line 18
  4. Very specific:

    Every monetary answer or proposal visibly shows Currency and Pricing basis: <basis> from the calculated measure or its documented source.

    line 22
  5. Distinctive:

    Before each flow, read its matching references below, including when using supplied results.

    line 30
  6. Distinctive:

    Before scoped calls, read Scope resolution.

    line 31
  7. Distinctive:

    If a required file is unavailable, report it and stop the affected flow.

    line 33
  8. Distinctive:

    Use the matching scenario guidance.

    line 35
  9. Very specific:

    Use shared headings and column order across models, with documented scope/lifecycle variations.

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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: <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

FlowRequired reference
Discovery and type expansionWorkflow
Counts, savings field mapping and pricing-source interpretationOutput and savings
Tables and selected resourcesTable format
Completed/historical reportsLifecycle
State changesState updates
Selection/remediation handoffSelection
Explicit prevalidation/safety checksSelection
Filters/errorsTools and recovery
Routing examplesExamples

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.