google-dev-docs
Use when writing API documentation, READMEs, tutorials, reference guides, error messages, or any technical content for developers using the Google developer documentation style guide.
Install
With your agent
Install OMGSkills skill "surendranb/writing-skills:skills/google-dev-docs" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/surendranb/writing-skills /tmp/writing-skills && ln -s /tmp/writing-skills/skills/google-dev-docs ~/.claude/skills/google-dev-docsFrom README
Google Developer Documentation Style Write precise, task-oriented technical documentation with second-person address and active voice. The core rule Task-oriented headings, present tense, second person ("you"), active voice. Workflow: state user goal in title → prerequisites first → numbered steps with concrete code examples → verification step. Mechanics Second person. Address the developer directly as "you"; avoid "we", "us", or third-person generalities. Present tense. Describe current system behavior in present tense ("Returns a 200 OK status", not "Will return"). Task-oriented headings. Start headings with gerunds or action verbs ("Configuring authentication", not "Authentication overview"). Active voice. "The server processes the request" rather than "The request is processed by the server". Code blocks with context. Every code snippet must include necessary imports, , and expected output. Pronoun clarity. Ensure "this", "that", and "it" clearly point to a preceding noun.
More from this repo
asd-ste100
Used when writing technical procedures, instructions, warnings, maintenance manuals, or any text where every reader...
business-writing
Used to write executive-grade business communication with BLUF (bottom line up front), active verbs, and zero buzzwords.
corporate-communication
Used to write internal corporate communications — announcements, org changes, policy updates, launch messages — with...