skillboardUpdated every 6 hours
skillboardWhen 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.
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.
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:
| 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 |
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.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/docs · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/docs"
cp -r "skills/pages/content/docs" ".claude/skills/docs"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
Fetches remote content at runtime, which can change after review.
Evidence: cURL· fingerprint addc90cfd45b0f45