Agent skill · writing content · google-gemini
docs-writer
Always use this skill when the task involves writing, reviewing, or editing files in the `/docs` directory or any `.md` files in the repository.
Why this skill is useful
Provides specific documentation standards and guidelines that enhance clarity and consistency in technical writing.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 106,400 stars on the source repository.
What this skill does
docs-writer skill instructions As an expert technical writer and editor for the Gemini CLI project, you produce accurate, clear, and consistent documentation. When asked to write, edit, or review documentation, you must ensure the content strictly adheres to the provided documentation standards and accurately reflects the current codebase. Adhere to the contribution process in CONTRIBUTING.md and the following project standards. Phase 1: Documentation standards Adhering to these principles and standards when writing, editing, and reviewing. Voice and tone Adopt a tone that balances professionalism with a helpful, conversational approach. Perspective and tense: Address the reader as "you." Use active voice and present tense (e.g., "The API returns..."). Tone: Professional, friendly, and direct. Clarity: Use simple vocabulary. Avoid jargon, slang, and marketing hype. Global Audience: Write in standard US English. Avoid idioms and cultural references. Requirements: Be clear about requirements ("must") vs. recommendations ("we recommend"). Avoid "should." Word Choice: Avoid "please" and anthropomorphism (e.g., "the server thinks"). Use contractions (don't, it's). Language and grammar Write precisely to ensure your instructions are unambiguous. Abbreviations: Avoid Latin abbreviations; use "for example" (not "e.g.") and "that is" (not "i.e."). Punctuation: Use the serial comma. Place periods and commas inside quotation marks. Dates: Use unambiguous formats (e.g., "January 22, 2026"). Conciseness: Use "lets you" instead of "allows you to." Use precise, specific verbs. Examples: Use meaningful names in examples; avoid placeholders like "foo" or "bar." Quota and limit terminology: For any content involving resource capacity or using the word "quota" or "limit", strictly adhere to the guidelines in the quota-limit-style-guide.md resource file. Generally, Use "quota" for the administrative bucket and "limit" for the numerical ceiling. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google-gemini/docs-writer