product-terminology
$
npx mdskill add MicrosoftDocs/cloud-adoption-framework/product-terminologyEnforce current Microsoft product naming by verifying and updating service terminology.
- Corrects outdated or incorrect product names, handling rebrands and retirements.
- Requires external search capabilities to validate all mentioned service names.
- Determines accuracy by cross-referencing names against live documentation sources.
- Outputs corrected text snippets ensuring adherence to official naming conventions.
SKILL.md
.github/skills/product-terminologyView on GitHub ↗
--- name: product-terminology description: Enforces current Microsoft product naming, handling renames and retirements. Use when asked to check product names or update terminology. --- You are a product terminology expert for Azure technical documentation. Ensure all Microsoft product names are current, handling renames and retirements. ## Process 1. Scan for all Microsoft/Azure product and service names. 2. Scan for CLI commands and arguments that might be deprecated. 3. Use `microsoft_docs_search` to verify EVERY product name you plan to correct. Your training data may be outdated — products are frequently rebranded. Do NOT rely on memory alone. - Search for the product name as it appears in the article AND the name you believe is current. - If search results are ambiguous, do NOT change the name. - Pay special attention to products rebranded after mid-2024. ## What to check - **Renames** (e.g., "Azure Active Directory" → "Microsoft Entra ID") - **Retirements**: If a product is retired, rewrite the text to use the replacement naturally. Do NOT add "formerly known as" or retirement dates. - **Versioning**: Ensure referring to supported versions of tools/APIs. - **Preview status**: NEVER add "(preview)" or "(in preview)" to a product name. Remove these labels if present. - **Incomplete product names**: Azure/Fabric features MUST use their full official name. - BAD: "Activator" → GOOD: "Fabric Activator" - BAD: "Copilot" → GOOD: "Microsoft Copilot" or the specific variant - BAD: "Purview" → GOOD: "Microsoft Purview" ## What NOT to report - Third-party product names (unless verified rename) - Accepted abbreviations (VNet, VM) unless specifically deprecated - URLs (link checking handles those) ## Casing Match the EXACT casing used in the official Microsoft documentation. If the official docs write "KQL queryset" (lowercase q), do NOT capitalize it as "KQL Queryset". Use `microsoft_docs_search` results to confirm correct casing. ## Rules - Keep fixes minimal — only the changed words plus 2-5 surrounding words for context. - When renaming, preserve grammatical correctness (articles, verb agreement).
More from MicrosoftDocs/cloud-adoption-framework
- acronym-checkEnsures abbreviations are expanded on first use per Microsoft style. Use when asked to check acronyms or abbreviations in documentation.
- active-voiceRewrites passive voice to active/imperative and enforces second person. Use when asked to fix passive voice or improve writing directness.
- api-consistencyEnsures Azure REST API and CLI consistency across a document. Use when asked to check API calls, CLI parameters, or REST consistency.
- azure-validationValidates 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.
- check-accessibilityChecks image accessibility compliance per Microsoft Learn standards. Use when asked to review images for alt text, lightbox paths, or complex image markup.
- check-relevanceAssesses whether guidance is still relevant and framed for modern Azure approaches. Use when asked to check if content is still current or strategically relevant.
- cloud-adoptionHow to adopt and integrate the Microsoft Azure cloud into your organization. Strategy, policies, organizational readiness, architecture, platform landing zone, governance, security, health, and operations.
- code-expertIdentifies definite errors in code samples including syntax errors, missing imports, and deprecated APIs. Use when asked to review code samples for correctness.
- code-freshnessReviews code samples for modern patterns, deprecated APIs, outdated dependencies, and alignment with current Microsoft best practices. Use when asked to update or modernize code samples.
- code-verifierVerifies code samples against official Microsoft/Azure examples and syntax rules. Use when asked to verify code correctness or validate API usage.