Technical writing and editing for Gemini CLI documentation with strict style adherence.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add google-gemini/gemini-cli --skill docs-writerCompatible with
Supported agents
Enforces comprehensive documentation standards covering voice, tone, grammar, formatting, and structure to ensure consistency across all .md files and /docs directory content
Requires investigation of relevant code and existing documentation before making changes, with checks for impacted pages and sidebar navigation updates
Applies specific rules for headings, lists, procedures, links, and access
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondocs-writerExecute the skills CLI command in your project's root directory to begin installation:
epx add google-gemini/gemini-cli --skill docs-writerFetches docs-writer from google-gemini/gemini-cli and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/docs-writer
Restart Cursor to activate docs-writer. Access via /docs-writerin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
tencent-docs
zrong/skills · Documents · tag: docs
voltagent-docs-bundle
voltagent/skills · Documents · tag: docs
openai-docs
openai/skills · AI/ML · tag: docs
portfolio-case-study-writer
paramchoudhary/resumeskills · Productivity · tag: writer
resume-bullet-writer
paramchoudhary/resumeskills · Productivity · tag: writer
academic-research-writer
endigo/claude-skills · Productivity · tag: writer
Useful defaults in docs-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for docs-writer matched our evaluation — installs cleanly and behaves as described in the markdown.
docs-writer has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in docs-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
docs-writer has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: docs-writer is focused, and the summary matches what you get after install.
I recommend docs-writer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
docs-writer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend docs-writer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added docs-writer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 42