
Docs Writer
If you're maintaining technical documentation for a CLI tool and need to enforce consistent voice, style, and formatting, this handles the tedious parts. It follows opinionated rules: sentence case headings, 80-character line wraps, specific callout syntax with prettier-ignore comments, relative links in docs, and a clear hierarchy for procedures. The preparation phase is thorough, requiring code investigation before any edits to ensure accuracy. Worth noting that it's built specifically for Gemini CLI's documentation standards, so you'll see references to their quota terminology guidelines and contribution process. Good for teams who want documentation that reads consistently, not just technically correct content.
- skills.sh installs
- 3.2K
- GitHub stars
- 108.7K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add google-gemini/gemini-cli --skill docs-writer --agent claude-codeInstalls into .claude/skills of the current project.
Files
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.
Sponsors
Details
- Repository
- github.com/google-gemini/gemini-cli
- Categories
- Documentation, CLI & Terminal