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
Quality
80%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Securityby
Passed
No known issues
tile.json
{
"name": "mcclowes/google-style-guide",
"version": "0.1.0",
"summary": "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.",
"skills": {
"google-style-guide": {
"path": "SKILL.md"
}
},
"private": false
}