Support Docs
When the user needs to create help center articles, FAQs, troubleshooting guides, API documentation, or getting-started guides for customers.
Install
npx skills add shawnpang/startup-founder-skills --skill support-docsgit clone --depth 1 https://github.com/shawnpang/startup-founder-skills.git /tmp/startup-founder-skills
mkdir -p ~/.claude/skills
cp -r /tmp/startup-founder-skills/skills/support-docs ~/.claude/skills/support-docsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Support Documentation ## When to Use Activate when a founder or team member needs to create customer-facing documentation that helps users solve problems independently. This includes prompts like "write a help center article," "create an FAQ," "document our API," "write a troubleshooting guide," "build a getting-started guide," or "our support tickets keep asking the same questions." ## Context Required - **From startup-context:** product type, target user technical level, existing documentation (if any), top support ticket categories, and tools used for docs hosting (e.g., Notion, GitBook, Zendesk, ReadMe). - **From the user:** the specific topic to document, the target audience (end users, admins, developers), the user's technical sophistication, common failure modes or confusion points, and whether this is a new article or an update to existing content. ## Workflow 1. **Identify document type** — Determine which template fits: help center article, FAQ, troubleshooting guide, API reference, or getting-started guide. Each serves a different user intent. 2. **Define the user's entry point** — How will someone find this document? Search query, error message, support agent link, in-app help button? This determines the title and opening line. 3. **Write in problem-solution format** — Lead with the user's problem (in their words), then provide the solution. Never start with product architecture explanations.
Details
- Skill name
support-docs- Repository
- shawnpang/startup-founder-skills
- Path
skills/support-docs/SKILL.md- License
- MIT
- Repo updated
- 16 March 2026
FAQ
What does the Support Docs skill do?
When the user needs to create help center articles, FAQs, troubleshooting guides, API documentation, or getting-started guides for customers.
How do I install the Support Docs skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add shawnpang/startup-founder-skills --skill support-docs. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Support Docs popular?
It lives in shawnpang/startup-founder-skills, which has 393 GitHub stars and 46 forks.
Related skills
Accelerator Application
393shawnpang/startup-founder-skills
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC application", "Techstars", "accelerator", or "apply to programs".
Architecture Design
393shawnpang/startup-founder-skills
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure topology, database selection, or dependency analysis. Also activate for "design the system", "how should I architect this", "monolith vs microservices", or architecture decision records.
Board Update
393shawnpang/startup-founder-skills
When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to stakeholders.
Aria Specialist
449Community-Access/accessibility-agents
ARIA roles, states and properties for custom widgets and dynamic content.
Social Content
393shawnpang/startup-founder-skills
When the user needs to build a LinkedIn authority system, create social content strategy, define content pillars, write posts, or establish thought leadership positioning. Activate on "LinkedIn strategy," "content pillars," "what should I post," or "build my personal brand.
HTML Artifacts
161dogum/html-artifacts
Produce a self-contained HTML artifact instead of a markdown document when the content benefits from spatial layout, color, real diagrams, interactivity, or a round-trip editor. Use when the user asks for a "doc," "writeup," "plan," "spec," "report," "explainer," "comparison," "review," "PR description," "mockup," "diagram," "flowchart," "deck," "slides," "status update," "post-mortem," "dashboard," "chart," "playground," or a one-off "editor" or "tool" for triaging, reordering, or tuning something, even without saying "HTML" or "artifact." Also when asked to "explain," "compare," "explore opt
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.