documentation-engineer

charon-fan/agent-playbook · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/charon-fan/agent-playbook --skill documentation-engineer
0 commentsdiscussion
summary

Expert in creating clear, comprehensive, and maintainable technical documentation.

skill.md

Documentation Engineer

Expert in creating clear, comprehensive, and maintainable technical documentation.

When This Skill Activates

Activates when you:

  • Ask to write documentation
  • Request README creation
  • Mention "docs" or "document this"
  • Need API documentation

Documentation Types

1. README

Every project should have a README with:

# Project Name

Brief description (what it does, why it exists)

## Quick Start

Installation and usage in 3 steps or less.

## Installation

Detailed installation instructions.

## Usage

Examples of common usage patterns.

## Configuration

Environment variables and configuration options.

## Development

How to run tests, build, and develop locally.

## Contributing

Guidelines for contributors.

## License

License information.

2. API Documentation

For each endpoint/function:

  • Description: What it does
  • Parameters: Name, type, required/optional, description
  • Return value: Type and structure
  • Errors: Possible errors and conditions
  • Examples: Usage examples

3. Code Comments

Comment why, not what:

// Bad: Sets the count to zero
count = 0;

// Good: Reset count for new measurement cycle
count = 0;

// Bad: Check if user is admin
if (user.role === 'admin') {

// Good: Only admins can bypass approval workflow
if (user.role === 'admin') {

4. Architecture Documentation

  • System overview
  • Component relationships
  • Data flow
  • Design decisions
  • Trade-offs considered

Documentation Principles

  1. Be Clear: Use simple, direct language
  2. Be Concise: Respect the reader's time
  3. Be Accurate: Keep docs in sync with code
  4. Be Complete: Cover all public interfaces
  5. Be Current: Update docs when code changes

Writing Guidelines

Headings

  • Use sentence case for headings
  • Start with a verb or noun
  • Be descriptive

Code Examples

  • Show before/after when appropriate
  • Include import statements
  • Show expected output
  • Handle edge cases

Links

  • Use relative links for internal docs
  • Include anchors for sections
  • Test that links work

Diagrams

  • Use Mermaid for flowcharts and sequences
  • Keep diagrams simple
  • Add a title and legend

Documentation Checklist

README

  • Project description
  • Quick start guide
  • Installation instructions
  • Usage examples
  • Configuration guide
  • Contributing guidelines

Code Docs

  • All public functions documented
  • Parameters and returns documented
  • Examples provided for complex functions
  • Edge cases documented

API Docs

  • All endpoints documented
  • Request/response schemas
  • Authentication requirements
  • Error responses documented
  • Rate limits documented

Scripts

Generate documentation structure:

python scripts/generate_docs.py

Validate documentation:

python scripts/validate_docs.py

References

  • references/readme-template.md - README template
  • references/api-template.md - API documentation template
  • references/style-guide.md - Documentation style guide
how to use documentation-engineer

How to use documentation-engineer on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add documentation-engineer
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/charon-fan/agent-playbook --skill documentation-engineer

The skills CLI fetches documentation-engineer from GitHub repository charon-fan/agent-playbook and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/documentation-engineer

Reload or restart Cursor to activate documentation-engineer. Access the skill through slash commands (e.g., /documentation-engineer) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ 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.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.656 reviews
  • Chaitanya Patil· Dec 28, 2024

    documentation-engineer reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Arya Smith· Dec 28, 2024

    documentation-engineer has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Liam Park· Dec 24, 2024

    Registry listing for documentation-engineer matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Aisha Martin· Dec 16, 2024

    documentation-engineer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Piyush G· Nov 19, 2024

    I recommend documentation-engineer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Arya Zhang· Nov 19, 2024

    documentation-engineer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Arya Tandon· Nov 15, 2024

    Useful defaults in documentation-engineer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Anika Abbas· Nov 7, 2024

    documentation-engineer has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Anika Bansal· Oct 26, 2024

    Solid pick for teams standardizing on skills: documentation-engineer is focused, and the summary matches what you get after install.

  • Shikha Mishra· Oct 10, 2024

    Useful defaults in documentation-engineer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 56

1 / 6