
Documentation Engineer
Generate READMEs, API references, architecture notes, and validated doc structure while you build or ship a product.
Overview
Documentation Engineer is an agent skill most often used in Build (also Ship, Launch) that produces READMEs, API docs, comments, and architecture documentation from your project context.
Install
npx skills add https://github.com/charon-fan/agent-playbook --skill documentation-engineerWhat is this skill?
- Four documentation types: README, API docs, code comments, and architecture overviews
- Built-in API endpoint template with methods, parameters, response JSON, and error codes
- README template covering overview, quick start, installation, usage, and configuration
- Python scripts to generate doc structure and validate documentation completeness
- Aligned with Google Developer Documentation Style Guide and Diátaxis framework
- 4 documentation types in the type table (README, API Docs, Code Comments, Architecture)
- 2 Python helper scripts: generate_docs.py and validate_docs.py
Adoption & trust: 569 installs on skills.sh; 58 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your product works but newcomers and API consumers cannot onboard because README and endpoint documentation are missing or inconsistent.
Who is it for?
Solo developers shipping APIs, CLIs, or SaaS who want template-driven docs and script-assisted validation in the same repo.
Skip if: Teams needing regulated compliance manuals, video courses, or fully automated doc portals without human review of accuracy.
When should I use this skill?
You ask the agent to write documentation for an API, create a README, or document code in the repository.
What do I get? / Deliverables
You get structured README and API documentation plus optional validation passes so agents and humans can install, configure, and integrate faster.
- README draft
- API endpoint documentation
- Architecture or inline comment guidance
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Documentation is authored during Build when the codebase exists, even though the same skill supports launch and onboarding copy later. Docs subphase is the primary shelf for README, API, inline comments, and architecture artifacts.
Where it fits
Draft API endpoint docs with parameters and error tables right after shipping a new route.
Add inline code comments and architecture notes while refactoring a service boundary.
Refresh README install steps and configuration before a version tag.
Polish public-facing overview and quick start for GitHub or product landing backlinks.
How it compares
Skill-packaged doc templates and validators—not a hosted documentation platform or OpenAPI-only generator.
Common Questions / FAQ
Who is documentation-engineer for?
Indie builders and agent users who maintain their own repo and need README, API, and architecture docs without a technical writing team.
When should I use documentation-engineer?
Use it in Build while implementing features; in Ship before tagging a release; and at Launch when publishing developer-facing pages or integration guides.
Is documentation-engineer safe to install?
It runs local Python doc scripts on your filesystem—review the Security Audits panel on this page and inspect scripts before executing in CI.
SKILL.md
READMESKILL.md - Documentation Engineer
# Documentation Engineer > A Claude Code skill for creating clear, comprehensive documentation. ## Installation This skill is part of the [agent-playbook](../../README.md) collection. ## Usage ``` You: Write documentation for this API You: Create a README You: Document this code ``` ## Documentation Types | Type | Description | |------|-------------| | **README** | Project overview and quick start | | **API Docs** | Endpoint/function documentation | | **Code Comments** | Inline explanations | | **Architecture** | System design documentation | ## Scripts Generate documentation structure: ```bash python scripts/generate_docs.py ``` Validate documentation: ```bash python scripts/validate_docs.py ``` ## Resources - [Google Developer Documentation Style Guide](https://developers.google.com/tech-writing/one) - [Diátaxis Framework](https://diataxis.fr/) # API Documentation Template ## Endpoint: /resource **Method:** GET | POST | PUT | DELETE **Description:** What the endpoint does. ### Parameters - `id` (string, required) - Resource identifier ### Response ```json { "data": {} } ``` ### Errors - `400` Bad Request - `401` Unauthorized - `404` Not Found # README Template ## Overview Describe what the project does and why it exists. ## Quick Start 1. Install dependencies 2. Configure environment 3. Run the main command ## Installation - Requirements - Setup steps ## Usage Provide common usage examples. ## Configuration List environment variables and configuration options. ## Development How to lint, test, and build locally. ## Contributing Explain how to propose changes. # Documentation Style Guide ## Headings - Use sentence case - Keep headings short and specific ## Code Blocks - Always specify a language - Keep examples minimal and runnable ## Links - Use relative links for internal docs - Prefer stable URLs for external references #!/usr/bin/env python3 # Template generator for documentation scaffold. from pathlib import Path import argparse import textwrap def write_output(path: Path, content: str, force: bool) -> bool: if path.exists() and not force: print(f"{path} already exists (use --force to overwrite)") return False path.parent.mkdir(parents=True, exist_ok=True) path.write_text(content, encoding="utf-8") return True def main() -> int: parser = argparse.ArgumentParser(description="Generate documentation scaffold.") parser.add_argument("--output", default="docs/README.md", help="Output file path") parser.add_argument("--name", default="example", help="Product or service name") parser.add_argument("--owner", default="team", help="Owning team") parser.add_argument("--force", action="store_true", help="Overwrite existing file") args = parser.parse_args() content = textwrap.dedent( f"""\ # Documentation ## Overview Describe {args.name} and its purpose. ## Ownership - Owner: {args.owner} - Support channel: TBD ## Quickstart 1. Install dependencies 2. Configure environment 3. Run the service ## Configuration - Required environment variables - Feature flags ## Usage Examples for {args.name}. ## API Reference - Endpoints or SDK methods ## Troubleshooting - Common errors and fixes ## Changelog - Recent updates """ ).strip() + "\n" output = Path(args.output) if not write_output(output, content, args.force): return 1 print(f"Wrote {output}") return 0 if __name__ == "__main__": raise SystemExit(main()) #!/usr/bin/env python3 # Template validator for documentation scaffold. from pathlib import Path import argparse DEFAULT_REQUIRED = [ "## Overview", "## Ownership", "## Quickstart", "## Configuration", "## Usage", "## Troubleshooting", ] def main() -> int: parser = argparse.ArgumentPa