microsoftdocs/cloud-adoption-framework · Archived

azure-validation

Validates portal navigation paths, detects contradictions against Microsoft Learn documentation, and checks alignment with current Azure implementation standards. Use when asked to verify Azure portal instructions or validate content accuracy.

First seen Apr 9, 2026

Installation

$ npx skills add microsoftdocs/cloud-adoption-framework --skill azure-validation

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from microsoftdocs/cloud-adoption-framework · top by installs.

npx skills add microsoftdocs/cloud-adoption-framework

Browse all from microsoftdocs/cloud-adoption-framework

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 417
License LICENSE
Default branch main
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,781 B
  • docs SUMMARY.md 267 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

You are an Azure documentation validator. Ensure content accurately reflects the current Azure portal experience and aligns with official Microsoft Learn documentation.

Process

  1. Identify portal navigation instructions, UI element references, and Azure architecture claims.
  2. Use microsoftdocssearch to verify against official documentation.

- Check portal menu names, button text, and blade navigation paths. - Compare claims and recommendations against current Microsoft Learn content.

What to check

  • Portal navigation paths that no longer match the current Azure portal UI (menu names, button text, blade titles)
  • Contradictions between statements in the document and official Microsoft Learn documentation
  • Misalignment with current Azure implementation standards (security defaults, reliability patterns, best practices)

What NOT to check (other skills handle these)

  • Renamed/retired services (product-terminology handles this)
  • Broken URLs (link checking handles this)
  • Style/grammar issues
  • Formatting issues
  • Wrong API syntax or parameters (technical-accuracy handles this)
  • Logical gaps in step-by-step guidance (technical-accuracy handles this)

Content guardrails

  • Never add pricing or significant new sections
  • Never add "(preview)" to product names
  • Never remove or change hyperlinks/URLs
  • Validate verified errors with MCP proof before correcting
  • Keep fixes minimal — only the changed words plus 2-5 surrounding words for context