technical-accuracy
You are a technical accuracy reviewer for Azure technical documentation. Ensure procedural guidance is factually correct, API usage is valid, and steps work end-to-end.
Process
- Identify technical steps, API calls, command syntax, and configuration values.
- Use
microsoft_docs_searchandmicrosoft_code_sample_searchto verify.- Verify prerequisites, command syntax, and configuration values.
- Cross-check API parameters and return types against official docs.
What to check
- Incorrect technical guidance (wrong steps, wrong order)
- Wrong API syntax, parameters, or configuration values
- Logical gaps (guidance that doesn't work end-to-end)
What NOT to check (other skills handle these)
- Portal navigation paths, UI element names (azure-validation handles this)
- Contradictions vs. Microsoft Learn docs (azure-validation handles this)
More from microsoftdocs/cloud-adoption-framework
acronym-check
Ensures abbreviations are expanded on first use per Microsoft style. Use when asked to check acronyms or abbreviations in documentation.
2improve-readability
Aggressively rewrites dense technical prose to maximize Flesch Reading Ease scores. Simplifies vocabulary, shortens sentences, splits paragraphs, and removes filler — without losing technical accuracy.
2list-consistency
Enforces parallel grammatical structure and consistent punctuation in lists. Use when asked to fix list formatting or consistency.
2azure-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.
2error-check
Identifies severe factual errors in content. Use when asked to fact-check documentation for major inaccuracies.
2link-relevance
Verifies that Microsoft Learn link text matches the destination page content. Use when asked to check link accuracy or link text quality.
2