mcclowes/google-style-guide
Use when writing or reviewing technical documentation to follow Google's documentation style guide — enforce active voice and present tense, apply sentence case to headings, fix list and procedure formatting, mark code/UI elements correctly, flag non-inclusive terminology, and remove time-specific phrasing. Triggers on tasks involving technical writing, doc review, style consistency, inclusive language, or formatting standards.
64
80%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
README.md
Google Style Guide
Google's documentation style guide for technical writing - https://developers.google.com/style
Structure
SKILL.md- Main skill instructionsreferences/- Detailed documentation loaded as neededscripts/- Executable code for deterministic operationsassets/- Templates, images, or other resources
Usage
This skill is automatically discovered by Claude when relevant to the task.
Attribution and license
This skill adapts material from the Google developer documentation style guide, © Google, licensed under CC BY 4.0. The content has been condensed and restructured into skill form.
Because it is a derivative of CC BY 4.0 material, this skill is distributed under CC BY 4.0 (not the MIT license used by the rest of this repository). Changes: original guide condensed into SKILL.md plus topic reference files.