mcpbeat Sign in

Docs Page Generator Agent Skill

When the user wants to create, optimize, or structure a documentation site. Also use when the user mentions "docs," "documentation site," "docs subdomain," "docs.yourdomain.com," "help center," "knowledge base," "Getting Started," "API Reference," "user guides," or "tutorials." For API marketing landing, use api-page-generator.

840 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
836
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/kostja94/marketing-skills --skill docs-page-generator

The instruction itself

10 sections, as written by the author

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
  • 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
  • howto-section-generator: HowTo step blocks in guides/tutorials; TechArticle + HowTo alignment
  • content-strategy: Doc content planning

Other skills for the same job

different authors, same section of the catalogue
Notion Template Business
by ComeOnOliver
×2

Expert in building and selling Notion templates as a business - not just making templates, but building a sustainable digital product business. Covers template design, pricing, marketplaces, marketing, and scaling to real revenue. Use when: notion template, sell templates, digital product, notion business, gumroad.

4k tokens
Draw
by lingxling
×1

Vector graphics and diagram creation, format conversion (ODG/SVG/PDF) with LibreOffice Draw.

1k tokens
Binary Re Synthesis
by ComeOnOliver
×1

Use when ready to document findings, generate a report, or summarize binary analysis results. Compiles analysis findings into structured reports - correlates facts from triage/static/dynamic phases, validates hypotheses, generates documentation with evidence chains. Keywords - "summarize findings", "generate report", "document analysis", "what did we find", "write up results", "export findings

5k tokens
Exam Ready
by github
vendor

> Activate this skill when a student provides study material (PDF or pasted notes) and a syllabus, and wants to prepare for an exam. Extracts key definitions, points, keywords, diagrams, exam-ready sentences, and practice questions strictly from the provided material.

988 tokens
Xiaohongshu Makeup
by anbeime

小红书美妆内容创作技能,支持笔记生成、笔记优化、文生图描述创作;适用于美妆护肤产品的内容创作、测评和营销推广

13k tokens zh
Proposal Writer
by jezweb

Write a client proposal, quote, scope of work, or engagement letter for a service business. Covers project understanding, scope, timeline, pricing presentation, and terms. Use whenever the user asks for a proposal, quote, project proposal, client proposal, SOW, statement of work, engagement letter, or B2B service engagement document — for web dev, consulting, trades, or any service business.

3k tokens
Startup Positioning
by ferdinandobons

Market positioning strategy using the April Dunford framework, enriched with JTBD discovery, Moore positioning statement, and Neumeier's Onliness Test. Produces a complete positioning document, positioning statement, competitive alternatives map, and market category analysis. Use when the user wants to define or refine their market positioning, find their unique position, differentiate from competitors, craft a positioning statement, choose a market category, or figure out "how should we position this product." Triggers for "positioning", "how to position", "market position", "differentiation strategy", "positioning statement", "competitive positioning", "category strategy", "where do we fit in the market", "how are we different", "unique value proposition", or any request to define, sharpen, or rethink positioning. Works standalone — no prior startup-design or startup-competitors session needed, but leverages their output if available.

19k tokens
Content Brief Authoring
by rampstackco

How to author a content brief that actually guides a writer (human or AI) to produce a piece that ranks, converts, or both. Per-piece editorial brief: target keyword and cluster, search intent, audience and JTBD, heading structure, entity coverage for AEO/GEO, internal linking strategy, success criteria. The middle path between thin briefs (a keyword and a deadline) and thick briefs (a 4-page document nobody reads). Triggers on content brief, brief the writer, brief the article, brief authoring, content brief template, brief audit, per-piece brief, editorial brief, target keyword brief, search intent brief. Also triggers when briefing a human writer or an AI agent on a single content piece.

18k tokens

How to use it

Copy the folder

Take kostja94/docs-page-generator from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.