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.
Install
With your agent
Install OMGSkills skill "google-gemini/gemini-cli:docs-writer" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, 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/google-gemini/gemini-cli /tmp/gemini-cli && ln -s /tmp/gemini-cli/.gemini/skills/docs-writer ~/.claude/skills/docs-writerFrom README
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.