skills.rest
sudhakrms
sudhakrmsCOMMUNITY
Explore all skills by this author →
GitHub

docs-standards

Enforce Microsoft Style Guide-based standards on documentation pages.

1|Updated Apr 17, 2026
Search Tags:#documentation#markdown#patterns#quality#style-guide#squad#scannability
One-click install
npx skills add https://github.com/sudhakrms/CalendarControl --skill docs-standards-sudhakrms
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-standards
Source: https://github.com/sudhakrms/CalendarControl/tree/main/coffee/.copilot/skills/docs-standards
Command: npx skills add https://github.com/sudhakrms/CalendarControl --skill docs-standards-sudhakrms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad documentation often lacks consistency and scannability, yielding trust issues and confusing readers.

Core Features & Use Cases

  • Microsoft Style Guide Rules: sentence-case headings, active voice, second person, present tense, no ampersands in prose.
  • Squad Formatting Patterns: scannability-first narratives, "Try this" prompts, experimental warnings, cross-references at bottom.
  • Structure & Test Sync: clear page structure and a rule to update test assertions when new docs are added.

Quick Start

Apply the docs-standards pattern to the current document to ensure compliant structure and clear formatting.

Frequently Asked Questions about docs-standards

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

FAQPage Schema
How do I enforce consistent documentation formatting across my team?▼

Enforce consistent documentation formatting by applying a Microsoft Style Guide baseline to your markdown files, ensuring standardized sentence-case headings, active voice, and present tense across all squad pages.

What is the best way to structure technical documentation for scannability?▼

Structure technical documentation for scannability by using squad formatting patterns like scannability-first narratives, clear page structures, and required sections such as "What problem does it solve?" and "Quick Start".

How does a Microsoft Style Guide baseline improve markdown documentation quality?▼

A Microsoft Style Guide baseline improves markdown documentation quality by enforcing active voice, second person, present tense, and cross-references at the bottom, eliminating prose ampersands and confusing reader experiences.

Can I use standard documentation patterns for getting started pages and references?▼

Yes, you can apply standard documentation patterns to getting started pages and references, ensuring consistent tone, mandatory YAML frontmatter presence, and standardized structural sections across all squad documents.

What documentation requirements ensure valid YAML frontmatter and structure?▼

Valid documentation requires YAML frontmatter with name and description fields, alongside enforced structural sections for "Core Features & Use Cases" and "Quick Start" to maintain consistency and build reader trust.

When do I need to update test assertions for squad documentation?▼

Update test assertions for squad documentation whenever new docs are added, synchronizing page structure validation rules to ensure continuous compliance with the standardized Microsoft Style Guide baseline.

Related Skills

Explore More Content & Communication Skills→
tkstangtkstang

oat-project-revise

Create revision tasks from post-PR feedback and manage project state.

Community
Advanced
JongsixJongsix

moai-docs-generation

Generate technical documentation from source code and API definitions.

Community
Advanced
louloulinlouloulin
19

skill-md-validator

Validate SKILL.md files for YAML frontmatter, required fields, and content.

Community
Basic
Golnaz89Golnaz89

docs-standards

Enforce Microsoft Style Guide rules and squad-specific formatting in documentation.

Community
Intermediate