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
/plugin marketplace add surendranb/writing-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add surendranb/writing-skills --skill google-dev-docsgit clone --depth 1 https://github.com/surendranb/writing-skills.git /tmp/writing-skills
mkdir -p ~/.claude/skills
cp -r /tmp/writing-skills/skills/google-dev-docs ~/.claude/skills/google-dev-docsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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
1. **Second person.** Address the developer directly as "you"; avoid "we", "us", or third-person generalities.
2. **Present tense.** Describe current system behavior in present tense ("Returns a 200 OK status", not "Will return").
3. **Task-oriented headings.** Start headings with gerunds or action verbs ("Configuring authentication", not "Authentication overview").
4. **Active voice.** "The server processes the request" rather than "The request is processed by the server".
5. **Code blocks with context.** Every code snippet must include necessary imports, setup, and expected output.
6. **Pronoun clarity.** Ensure "this", "that", and "it" clearly point to a preceding noun.
7. **Consistent terminology.** Use identical terms across guides, API references, and UI labels.
8. **Concise error messages.** Explain what went wrong and how to fix it immediately.
## Verify
- Headings use gerunds or action verbs describing tasks
- Sentences consistently use second person ("you")
- Code snippets are complete, syntactically valid, and tested
- Active voice used throughout instructionsDetails
- Skill name
google-dev-docs- Repository
- surendranb/writing-skills
- Path
skills/google-dev-docs/SKILL.md- License
- MIT
- Repo updated
- 2 September 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Google Dev Docs skill do?
Use when writing API documentation, READMEs, tutorials, reference guides, error messages, or any technical content for developers using the Google developer documentation style guide.
How do I install the Google Dev Docs skill?
Claude Code plugin: /plugin marketplace add surendranb/writing-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Google Dev Docs popular?
It lives in surendranb/writing-skills, which has 55 GitHub stars and 3 forks, and is included in 1 curated skill list.
Related skills
Asd Ste100
55surendranb/writing-skills
Use when writing technical procedures, instructions, warnings, maintenance manuals, or any text where every reader including non-native English speakers must understand exactly one meaning.
Bob Ross
55surendranb/writing-skills
Write calm, soothing, gently instructional prose in the voice of Bob Ross. Use when the user wants encouraging guidance, mistakes reframed as opportunities, a serene step-by-step tone, or down-to-earth warmth for nervous readers.
Business Writing
55surendranb/writing-skills
Write executive-grade business communication with BLUF (bottom line up front), active verbs, and zero buzzwords. Use when the user writes memos, status updates, emails to leadership, decision briefs, meeting recaps, or any business/corporate communication.
Gov Uk Style
55surendranb/writing-skills
Use when writing public-facing content, government or civic communication, help pages, policy summaries, or content requiring maximum-scope readability according to GOV.UK standards.
Corporate Communication
55surendranb/writing-skills
Write internal corporate communications — announcements, org changes, policy updates, launch messages — with clarity, honesty, and calibrated warmth. Use when the user writes company-wide emails, leadership messages, change communications, or sensitive internal news.
Jack Sparrow
55surendranb/writing-skills
Write flamboyant, mischievously grand, baroque-pirate prose in the voice of Captain Jack Sparrow. Use when the user wants playful, swashbuckling, theatrical, or entertainingly evasive writing; humor with pageantry; or anything that needs to be more fun, ornate, and less straight-laced.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.