docs-writer

Generate and update Gemini CLI documentation following the Google Developer Documentation Style Guide.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/PHNX3NT/expert-lamp --skill docs-writer-phnx3nt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-writer
Source: https://github.com/PHNX3NT/expert-lamp/tree/main/.gemini/skills/docs-writer
Command: npx skills add https://github.com/PHNX3NT/expert-lamp --skill docs-writer-phnx3nt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill assists in creating and updating documentation for the Gemini CLI project, ensuring accuracy, clarity, and adherence to project standards.

Core Features & Use Cases

  • Documentation Generation: Drafts new documentation pages or modifies existing ones based on user requests.
  • Codebase Investigation: Analyzes relevant code to ensure documentation is technically accurate.
  • Style Guide Adherence: Follows Google Developer Documentation Style Guide and project-specific formatting.
  • Use Case: When a new feature is added to Gemini CLI, this Skill can be used to write the corresponding documentation in the docs/ directory.

Quick Start

Use the docs-writer skill to add a new section about the 'search' command to the 'cli-commands.md' file.

Frequently Asked Questions about docs-writer

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

FAQPage Schema
How do I generate technical documentation for the Gemini CLI?

To generate Gemini CLI documentation, this skill analyzes your codebase and drafts new pages or updates existing files in the docs/ directory. It ensures technical accuracy by reading the relevant code before writing the markdown files.

Does the documentation generated follow a specific technical writing style guide?

The generated documentation strictly follows the Google Developer Documentation Style Guide. This ensures your Gemini CLI project maintains consistent formatting, clarity, and professional technical writing standards across all markdown files.

How do I update existing markdown files when a new feature is added?

To update existing markdown files, the skill uses file system tools like replace and write_file to modify the docs/ directory. It identifies the relevant documents and adjusts the text to reflect the new feature accurately.

Can I use this to analyze code and automatically write the corresponding developer docs?

Yes, you can use this to automatically write developer docs by analyzing your codebase. It investigates the relevant source code to ensure the generated documentation accurately describes the implementation and CLI commands.

What is the best way to maintain consistency across project documentation?

The best way to maintain project documentation consistency is enforcing adherence to the Google Developer Documentation Style Guide. This skill applies those project-specific standards automatically when creating or updating markdown files in the docs/ directory.