generate-agent-docs
Generates documentation and usage guides for agents, skills, prompts, and instructions. Works with GitHub Copilot, Claude Code, Codex, OpenCode, and other providers. Use when onboarding team members, creating README files for your customizations, or generating usage examples for existing agents.
Best use case
generate-agent-docs is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generates documentation and usage guides for agents, skills, prompts, and instructions. Works with GitHub Copilot, Claude Code, Codex, OpenCode, and other providers. Use when onboarding team members, creating README files for your customizations, or generating usage examples for existing agents.
Teams using generate-agent-docs should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/generate-agent-docs/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How generate-agent-docs Compares
| Feature / Agent | generate-agent-docs | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generates documentation and usage guides for agents, skills, prompts, and instructions. Works with GitHub Copilot, Claude Code, Codex, OpenCode, and other providers. Use when onboarding team members, creating README files for your customizations, or generating usage examples for existing agents.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Generate Agent Documentation
Creates user-friendly documentation for AI coding assistant customization files.
## Provider Folder Reference
This skill works across multiple AI coding assistant providers:
| Provider | Base Folder |
|----------|-------------|
| GitHub Copilot | `.github/` |
| Claude Code | `.claude/` |
| Codex | `.codex/` |
| OpenCode | `.config/opencode/` |
**Throughout this document, `<provider>/` represents your chosen provider's base folder.**
## When to Use
- Onboarding new team members to your agent ecosystem
- Creating a catalog of available agents and skills
- Generating usage examples for specific agents
- Documenting your customization setup for reference
## Documentation Types
### Individual Item Documentation
Generate detailed docs for a single agent, skill, prompt, or instruction.
### Catalog Documentation
Generate a comprehensive overview of all customization files.
## Output Templates
### Agent Documentation
```markdown
# Agent: [Agent Name]
## Overview
[What this agent does and why it exists]
## When to Use This Agent
Use `@[agent-name]` when:
- [Scenario 1]
- [Scenario 2]
- [Scenario 3]
**Don't use** when:
- [Anti-pattern 1]
- [Anti-pattern 2]
## How It Behaves
This agent will:
- [Behavior 1]
- [Behavior 2]
- [Behavior 3]
## Example Conversations
### Example 1: [Scenario Title]
**You:** [Example user message]
**Agent:** [How agent responds - summarized]
### Example 2: [Scenario Title]
**You:** [Example user message]
**Agent:** [How agent responds - summarized]
## Tips for Best Results
- [Tip 1 for effective usage]
- [Tip 2 for effective usage]
- [Common mistake to avoid]
## Related
- **[Related Agent]**: Use for [distinction]
- **[Related Skill]**: This agent uses this for [purpose]
```
### Skill Documentation
```markdown
# Skill: [Skill Name]
## Purpose
[What this skill accomplishes]
## Triggers
This skill activates when:
- [Trigger keyword/scenario 1]
- [Trigger keyword/scenario 2]
## What It Does
[Step-by-step of what the skill does]
## Used By
- [Agent 1] - for [purpose]
- [Agent 2] - for [purpose]
## Example
**Scenario:** [Description]
**Input:** [What's provided]
**Output:** [What's produced]
```
### Prompt Documentation
```markdown
# Prompt: [Prompt Name]
## Purpose
[What task this prompt accomplishes]
## Mode
`[mode]` - [explanation of what this mode does]
## Variables
| Variable | Description | Example |
|----------|-------------|---------|
| `{{var1}}` | [what it's for] | [example value] |
## How to Use
1. [Step 1]
2. [Step 2]
## Example
**With these values:**
- `{{var1}}` = [value]
**Produces:**
[Example output]
```
### Instruction Documentation
```markdown
# Instructions: [Name]
## Applies To
Files matching: `[glob pattern]`
## Purpose
[What guidance these instructions provide]
## Key Rules
1. [Rule 1]
2. [Rule 2]
3. [Rule 3]
## When Active
These instructions automatically apply when you're working with files that match the pattern above.
## Examples of Affected Files
- `[example path 1]`
- `[example path 2]`
```
### Catalog Documentation
```markdown
# AI Coding Assistant Customizations
This document catalogs all custom agents, skills, prompts, and instructions configured for this project.
## Provider
[Specify which provider folder is used: `.github/`, `.claude/`, `.codex/`, `.config/opencode/`, `.gemini/`]
## Quick Reference
### Agents (User-Invokable)
| Agent | Purpose | Invoke With |
|-------|---------|-------------|
| [name] | [brief purpose] | `@[name]` |
### Sub-Agents (Workflow Components)
| Sub-Agent | Purpose | Used By |
|-----------|---------|---------|
| [name] | [brief purpose] | [parent workflow agent] |
### Skills
| Skill | Purpose | Triggers |
|-------|---------|----------|
| [name] | [brief purpose] | [keywords] |
### Prompts
| Prompt | Mode | Purpose |
|--------|------|---------|
| [name] | [mode] | [brief purpose] |
### Instructions
| Instructions | Applies To | Purpose |
|--------------|------------|---------|
| [name] | [pattern] | [brief purpose] |
## Detailed Documentation
[Full documentation for each item]
## Usage Guidelines
[General guidance on how to use these customizations effectively]
```
## Generation Process
### Step 1: Read Source File
Load the agent/skill/prompt/instruction file.
### Step 2: Extract Key Information
- Name and description from frontmatter
- Behaviors and rules from body
- Examples if present
- Related items (skills, handoffs)
### Step 3: Enhance with Context
- Generate additional examples based on purpose
- Identify related items from the ecosystem
- Add tips based on common patterns
### Step 4: Format Output
Apply appropriate template based on item type.
## Quality Guidelines
Generated documentation should be:
1. **Clear** - No jargon without explanation
2. **Practical** - Real, actionable examples
3. **Complete** - Covers all key aspects
4. **Concise** - No unnecessary padding
5. **Current** - Reflects actual file contents
## Additional Examples
When generating examples beyond those in the source:
- Cover different use case variations
- Show edge cases and how they're handled
- Demonstrate integration with other items
- Illustrate common mistakes to avoidRelated Skills
review-docs
Review documentation (README.md and CLAUDE.md) for quality, completeness, and consistency. Use when asked to review docs, check documentation, validate README files, or audit CLAUDE.md coverage.
reindex-docs
Re-index all PDF and HTML documents, update index.html, and commit/push changes to the repository
readme-generate
Generate comprehensive README files from code analysis
pitchdocs-suite
One-command generation and audit of the full public repository documentation set — README, CHANGELOG, ROADMAP, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, issue templates, PR template, and discussion templates. Use when setting up a new repo or auditing an existing one.
organize-agent-docs
Organize project agentic documentation into universal (AGENTS.md) and agent-specific files (CLAUDE.md, GEMINI.md, etc.). Use when asked to "organize agent docs", "separate agent instructions", "restructure AGENTS.md", or when a project has agent documentation that mixes universal and tool-specific content.
openclaw-docs-sync
Sync OpenClaw + ClawHub + Skills docs into a local mirror for the QMD memory backend.
moai-docs-unified
Enhanced docs unified with AI-powered features. Enhanced with Context7 MCP for up-to-date documentation.
maintain-docs
Periodic documentation maintenance audit. Finds orphaned docs, detects drift between .cursor/rules/ and docs/developer/, validates doc correctness against source code, tracks structural issues in a persistent backlog, and opens PRs to close highest-priority gaps per run. Use when the user asks to audit documentation, sync docs, or maintain the knowledge base.
maintain-dev-docs
Maintain project /docs/: specs, tasks, features, readme. Use for: project setup, feature additions, instruction improvements, or syncing documentation with code.
ln-120-reference-docs-creator
Creates reference documentation structure + smart documents (ADRs/Guides/Manuals) based on TECH_STACK. Only creates justified documents (nontrivial technology choices). L2 Worker in ln-100-documents-pipeline.
google-docs-manager
Expert in Google Docs management. Use when creating, reading, updating, formatting, or managing Google Docs with markdown support, advanced formatting, tables with full manipulation, images with styling, lists, headers/footers, and table of contents.
genesis-tools:living-docs
Self-maintaining documentation system. Bootstraps, validates, refines, and optimizes codebase documentation. Creates minimal, token-efficient doc chunks. Use when creating, updating, or auditing project documentation.