Apply Google documentation style to technical documentation drafts.
npx skills add https://github.com/mcclowes/omg --skill google-style-guide
Please help me install this Agent Skill. Skill: google-style-guide Source: https://github.com/mcclowes/omg/tree/main/.claude/skills/google-style-guide Command: npx skills add https://github.com/mcclowes/omg --skill google-style-guide
This Skill eliminates guesswork in technical writing by automatically applying Google's proven style guidelines for clarity and professionalism.
Review the attached documentation draft and suggest improvements based on Google's style guide principles.
Review this paragraph for style guide compliance: 'The user will be prompted to enter their credentials before access is granted'.
High-intent search queries and answers about installing and using this skill.
Apply Google's style guide principles to your documentation by converting passive voice to active voice, using present tense, adopting sentence-case headings, and ensuring inclusive language. This Skill automatically rectifies inconsistent technical docs—software documentation, API references, developer guides, and internal docs—to meet Google's standards for clarity and professionalism.
Accessible technical writing requires active voice, clear sentence structure, inclusive language free of ableist or gendered terms, and proper code formatting conventions. Google's style guide addresses these accessibility considerations, and this Skill applies them automatically to improve readability and reach for all users.
Active voice replaces indirect constructions with direct, actionable instructions. For example, 'the user will be prompted to enter credentials' becomes 'enter your credentials.' This Skill detects passive constructions across your documentation and converts them to active voice, making instructions clearer and more engaging.
Yes. This Skill applies Google's style guidance to API references, developer guides, software documentation, and internal docs. It handles active voice, present tense, numbered and bulleted lists, code formatting conventions, placeholders, and accessibility considerations across all technical documentation types.
Inclusive language excludes ableist, gendered, or violent terminology in favor of neutral alternatives. This Skill automatically detects and replaces such language throughout your documentation, ensuring your technical writing is accessible and professional for all readers.
revokslabAutomate consistent Markdown documentation with structured templates and style guidelines.
amanhsnManage document control systems for ISO 13485 and 21 CFR Part 11 compliance.
ntaksh42Format Markdown documents with TOC generation and style guides.
ekremmkasapEnforce Python code style with ruff, mypy, and Google-style docstrings.
