microsoft-style-guide

Enforce Microsoft Learn writing style conventions in technical documentation.

1|Updated Oct 1, 2025

Search Tags:#documentation #content review #technical writing #style guide #microsoft learn #writing conventions

Ready to run

npx skills add https://github.com/diberry/microsoft-mcp-doc-generation --skill microsoft-style-guide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: microsoft-style-guide
Source: https://github.com/diberry/microsoft-mcp-doc-generation/tree/main/.squad/skills/microsoft-style-guide
Command: npx skills add https://github.com/diberry/microsoft-mcp-doc-generation --skill microsoft-style-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all documentation content adheres to the official Microsoft Writing Style Guide, maintaining a consistent, professional, and user-friendly tone across Microsoft Learn.

Core Features & Use Cases

Style Enforcement: Checks for adherence to voice, tone, person, and tense guidelines.
Formatting Consistency: Validates correct usage of headings, sentence structure, and word choice.
Inclusive Language: Promotes bias-free and globally-ready communication.
Use Case: An AI assistant reviewing a draft article for Microsoft Learn would use this Skill to identify and correct instances of passive voice, incorrect heading capitalization, or jargon.

Quick Start

Review the provided text to ensure it conforms to the Microsoft Writing Style Guide.

Frequently Asked Questions about microsoft-style-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check technical documentation for Microsoft Learn writing conventions?▼

To check technical documentation for Microsoft Learn writing conventions, you can review your text against the Microsoft Writing Style Guide to validate voice, tone, active voice, present tense, and sentence case headings.

What is the Microsoft Writing Style Guide standard for technical content review?▼

The Microsoft Writing Style Guide standard for technical content review enforces clear and consistent communication by requiring active voice, present tense, short sentences, sentence case headings, and inclusive, bias-free language.

How do I fix passive voice and incorrect heading capitalization in technical writing?▼

To fix passive voice and incorrect heading capitalization in technical writing, review your draft to convert passive sentences to active voice and apply sentence case to all headings, ensuring adherence to established style guides.

Does the Microsoft Learn style guide require inclusive language for documentation?▼

Yes, the Microsoft Learn style guide requires inclusive language for documentation to promote bias-free and globally-ready communication, validating content during the review and editing processes.

What are the limitations of using a style guide Skill for content review?▼

A limitation of using a style guide Skill for content review is that it primarily focuses on formatting, voice, and tense conventions, requiring a basic implementation depth that validates text consistency rather than generating new documentation.