docs-writer

Write and refine Gemini CLI documentation in Markdown files.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/clevergadget/hierophage-cli --skill docs-writer-clevergadget
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-writer
Source: https://github.com/clevergadget/hierophage-cli/tree/main/.gemini/skills/docs-writer
Command: npx skills add https://github.com/clevergadget/hierophage-cli --skill docs-writer-clevergadget

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams write, review, and refine Gemini CLI documentation to ensure clarity, consistency, and accuracy.

Core Features & Use Cases

  • Write and update docs for Gemini CLI features, primarily in the /docs directory and across any Markdown files.
  • Review wording, terminology, and tone for consistency with the project's style guide.
  • Validate links and references against CONTRIBUTING.md and project standards to maintain navigability.

Quick Start

Review and update the Gemini CLI docs in the /docs directory to reflect the latest release notes.

Frequently Asked Questions about docs-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review and update Gemini CLI documentation for consistency?

Review and update Gemini CLI documentation by applying the project's style guide and CONTRIBUTING.md standards to ensure proper tone, terminology, and link integrity across all Markdown files. This skill refines wording for clarity and accuracy.

How do I validate links in Markdown files for Gemini CLI docs?

Validate links in Markdown files by checking references against CONTRIBUTING.md and project standards to maintain navigability. This ensures all documentation links remain intact and functional across the /docs directory.

Does this skill work with the /docs directory and existing Markdown files?

Yes, this skill works with the /docs directory and all Markdown files for Gemini CLI. It handles writing new content, reviewing existing pages, and editing contributions directly within those project locations.

What is the best way to write new content for Gemini CLI documentation?

The best way to write new Gemini CLI documentation content is to follow the project's style guide and CONTRIBUTING.md. This ensures proper tone, accurate terminology, and consistent formatting across all newly created Markdown pages.

Can I use this to ensure terminology consistency across Gemini CLI docs?

Yes, you can use this to ensure terminology consistency. It reviews wording and terminology across Markdown files to align with the project's style guide, maintaining a unified voice throughout the Gemini CLI documentation.