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

azure-advisor-actionability

Skill1.6k starsChanged 16 days agoMITView on GitHub

Remediate Azure Advisor recommendations. WHEN: \"fix Advisor recommendation\".

3 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

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Call advisor_remediation_get once with only recommendationTypeId, never resourceId, before generating guidance or substituting values.

    line 20
  2. Distinctive:

    Use only returned remediation or retrieved Learn guidance, including warnings and verification.

    line 22
  3. Very specific:

    After retrieval, substitute unambiguous placeholders from the exact affected resourceId or confirmed context: subscription, resource group, …

    line 23

≈ “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 Actionability

Quick reference

Present remediation for the customer to run; never execute without explicit confirmation. Require the recommendationTypeId GUID and complete affected resourceId; reuse known values, ask for missing values, never guess.

Get resourceId from the user or an exact advisor_recommendation_list affected-resource record. Ask which resource if ambiguous; never use a recommendation instance ID.

Workflow

  1. Call advisor_remediation_get once with only recommendationTypeId, never resourceId, before generating guidance or substituting values.
  2. For RemediationNotFound, empty responses, or no usable remediation, state that Advisor remediation is unavailable. Retrieve relevant public Microsoft Learn documentation; ask for the recommendation description if unknown. If none is available, say so; never invent guidance. Report other tool errors without internals, not as empty results.
  3. Use only returned remediation or retrieved Learn guidance, including warnings and verification.
  4. After retrieval, substitute unambiguous placeholders from the exact affected resourceId or confirmed context: subscription, resource group, resource names, full resource ID. Preserve and describe unresolved placeholders.
  5. Preserve step order; separate Azure CLI and PowerShell.

For Advisor guidance, do not generate commands. For hybrid or executable, include every manual, decision, and command step. Omit raw JSON and internal labels.

Final response

Label the source: "Guidance source: Azure Advisor remediation tool" or "Guidance source: publicly available Microsoft Learn documentation" with retrieved learn.microsoft.com citations. Never attribute fallback guidance to Advisor or claim execution.

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.