Enforce Microsoft Style Guide documentation standards across squads.
npx skills add https://github.com/quaid-app/quaid --skill docs-standards-quaid-app
Please help me install this Agent Skill. Skill: docs-standards Source: https://github.com/quaid-app/quaid/tree/main/.copilot/skills/docs-standards Command: npx skills add https://github.com/quaid-app/quaid --skill docs-standards-quaid-app
Inconsistent documentation and divergent writing patterns across squads hinder clarity and discoverability. This Skill provides a standardized baseline by combining the Microsoft Style Guide with squad-specific conventions to improve readability and cohesion.
Audit an existing documentation page and rewrite it to conform to the Microsoft Style Guide and squad conventions.
High-intent search queries and answers about installing and using this skill.
To enforce consistent documentation across squads, apply a standardized style guide baseline combined with squad-specific conventions. This ensures uniform headings, active voice, and second-person narration, resolving divergent writing patterns and improving content readability and discoverability.
The Microsoft Style Guide baseline for technical documentation is a set of rules enforcing title case, active voice, present tense, and second-person narration. It establishes uniform tone and formatting patterns for scannability, warnings, and cross-references to maintain content clarity and cohesion.
To audit and rewrite an existing documentation page, evaluate it against style guide conformance rules and rewrite it to enforce required frontmatter metadata, title case, and a defined page structure including a title, warning, overview, and content sections.
Yes, this documentation standardization approach works for onboarding pages and scenario documentation. It applies a structured page blueprint with predictable layouts, including H1 titles, callouts, "Try this" prompts, and content sections, ensuring consistency across various technical guide formats.
Required frontmatter metadata and page structure elements for squad-wide documentation include an H1 title, warning or callout sections, "Try this" prompts, an overview, and defined content sections. These elements ensure predictable page layouts and conformance to established style guidelines.
ThejanaJayalathGenerate long-form articles, guides, and newsletters from raw notes using brand voice profiles.
Tobbe3108Automate static site deployment to GitHub Pages via gh-pages and CI/CD workflows.
Golnaz89Enforce Microsoft Style Guide rules and squad-specific formatting in documentation.
barichterValidate documentation against Microsoft Style Guide and Squad-specific conventions.
