How do I install the Docs Standards skill?

Run npx skillmds@latest add gabrielmoreira/docs-standards in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Docs Standards skill do?

Microsoft Style Guide + Squad-specific documentation patterns It is listed under Docs & Writing on SkillMD.

Is Docs Standards safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Docs Standards?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Docs Standards free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Docs Standards?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Docs Standards by gabrielmoreira — Agent Skill

Name: Docs Standards
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

File contents

Context

Squad documentation follows the Microsoft Style Guide with Squad-specific conventions. Consistency across docs builds trust and improves discoverability.

Patterns

Microsoft Style Guide Rules

Sentence-case headings: "Getting started" not "Getting Started"
Active voice: "Run the command" not "The command should be run"
Second person: "You can configure..." not "Users can configure..."
Present tense: "The system routes..." not "The system will route..."
No ampersands in prose: "and" not "&" (except in code, brand names, or UI elements)

Squad Formatting Patterns

Scannability first: Paragraphs for narrative (3-4 sentences max), bullets for scannable lists, tables for structured data
"Try this" prompts at top: Start feature/scenario pages with practical prompts users can copy
Experimental warnings: Features in preview get callout at top
Cross-references at bottom: Related pages linked after main content

Structure

Title (H1) → Warning/callout → Try this code → Overview → HR → Content (H2 sections)

Test Sync Rule

Always update test assertions: When adding docs pages to features/, scenarios/, guides/, update corresponding EXPECTED_* arrays in test/docs-build.test.ts in the same commit

Examples

✓ Correct:

# Getting started with Squad

> ⚠️ **Experimental:** This feature is in preview.

Try this:
\`\`\`bash
squad init
\`\`\`

Squad helps you build AI teams...

---

## Install Squad

Run the following command...

✗ Incorrect:

# Getting Started With Squad  // Title case

Squad is a tool which will help users... // Third person, future tense

You can install Squad with npm & configure it... // Ampersand in prose

Anti-Patterns

Title-casing headings because "it looks nicer"
Writing in passive voice or third person
Long paragraphs of dense text (breaks scannability)
Adding doc pages without updating test assertions
Using ampersands outside code blocks

---name: docs-standardsdescription: Microsoft Style Guide + Squad-specific documentation patterns--- ## Context Squad documentation follows the Microsoft Style Guide with Squad-specific conventions. Consistency across docs builds trust and improves discoverability. ## Patterns ### Microsoft Style Guide Rules - **Sentence-case headings:** "Getting started" not "Getting Started" - **Active voice:** "Run the command" not "The command should be run" - **Second person:** "You can configure..." not "Users can configure..." - **Present tense:** "The system routes..." not "The system will route..." - **No ampersands in prose:** "and" not "&" (except in code, brand names, or UI elements) ### Squad Formatting Patterns - **Scannability first:** Paragraphs for narrative (3-4 sentences max), bullets for scannable lists, tables for structured data - **"Try this" prompts at top:** Start feature/scenario pages with practical prompts users can copy - **Experimental warnings:** Features in preview get callout at top - **Cross-references at bottom:** Related pages linked after main content ### Structure - **Title (H1)** → **Warning/callout** → **Try this code** → **Overview** → **HR** → **Content (H2 sections)** ### Test Sync Rule - **Always update test assertions:** When adding docs pages to `features/`, `scenarios/`, `guides/`, update corresponding `EXPECTED_*` arrays in `test/docs-build.test.ts` in the same commit ## Examples ✓ **Correct:** ```markdown # Getting started with Squad > ⚠️ **Experimental:** This feature is in preview. Try this: \`\`\`bash squad init \`\`\` Squad helps you build AI teams... --- ## Install Squad Run the following command... ``` ✗ **Incorrect:** ```markdown # Getting Started With Squad // Title case Squad is a tool which will help users... // Third person, future tense You can install Squad with npm & configure it... // Ampersand in prose ``` ## Anti-Patterns - Title-casing headings because "it looks nicer" - Writing in passive voice or third person - Long paragraphs of dense text (breaks scannability) - Adding doc pages without updating test assertions - Using ampersands outside code blocks

Frequently asked questions

Docs Standards