docs-page-generator
/install docs-page-generator
Pages: Documentation Site
Guides documentation site structure, navigation, and content organization. Typically hosted on docs.* or help.* subdomain. Includes Getting Started, guides, tutorials, API Reference (endpoint docs), and troubleshooting. Distinct from API introduction page (api-page-generator).
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and use cases.
Identify:
- Product type: Software, API, hardware, service
- Audience: End users, developers, admins
- Content sources: Markdown, MDX, Git, CMS
- Subdomain: docs., help., or path (/docs)
Documentation Structure
| Section | Purpose | Typical Content |
|---|---|---|
| Getting Started | Onboarding, first steps | Quick start, installation, first task |
| Guides / Tutorials | Step-by-step learning | How-to articles, workflows |
| Concepts | Background, architecture | Key concepts, glossary links |
| API Reference | Endpoint docs | Auth, request/response, examples; part of docs, not separate page |
| Troubleshooting | Problem solving | FAQ, common errors, support links |
Best Practices
Information Architecture
- Progressive disclosure: Start simple, link to depth
- Sidebar navigation: Hierarchical, collapsible sections
- Search: Full-text search for long doc sets
- Breadcrumbs: For deep hierarchies
API Reference (within Docs)
API Reference is a section of docs, not a standalone page. Include: endpoints by resource, auth, request/response schemas, error codes, rate limits, code examples (cURL, SDKs). Use OpenAPI/Swagger for consistency.
Content
- Task-oriented: "How to X" not "X feature"
- Code examples: Copy-paste ready, multiple languages if relevant
- Screenshots/videos: For UI-heavy products
- Versioning: Document product/API version when applicable
SEO and Discovery
- Index docs: Unless internal-only; use robots if needed
- Internal links: Cross-link related articles, link to main site
- Schema: TechArticle, HowTo for guides
Output Format
- Structure (sections, hierarchy)
- Navigation design (sidebar, top-level)
- Getting Started outline
- Content checklist per section
- Subdomain/path recommendation
Related Skills
- api-page-generator: API intro page links to docs
- sidebar-generator: Docs sidebar design
- faq-page-generator: FAQ can live in docs or main site
- content-strategy: Doc content planning
- 确保已安装 OpenClaw(本地或 Docker 部署)
- 在对话框中输入安装命令:
/install docs-page-generator - 安装完成后,直接呼叫该 Skill 的名称或使用
/docs-page-generator触发 - 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
docs-page-generator 是什么?
When the user wants to create, optimize, or structure a documentation site. Also use when the user mentions "docs," "documentation site," "docs subdomain," "... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 183 次。
如何安装 docs-page-generator?
在 OpenClaw 或 Claude Code 对话框中运行命令「/install docs-page-generator」即可一键安装,无需额外配置。
docs-page-generator 是免费的吗?
是的,docs-page-generator 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。
docs-page-generator 支持哪些平台?
docs-page-generator 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。
谁开发了 docs-page-generator?
由 Kostja Zhang(@kostja94)开发并维护,当前版本 v1.0.1。