Knowledge Base Builder
Turn recurring support tickets into searchable FAQs, tutorials, and deflection metrics so fewer users need to open a ticket.
Overview
Knowledge Base Builder is an agent skill most often used in Grow (also Build/docs, Operate/support) that turns support-ticket patterns into FAQs, tutorials, and deflection-oriented help-center content.
Install
npx skills add https://github.com/onewave-ai/claude-skills --skill knowledge-base-builderWhat is this skill?
- Mines support tickets to surface recurring FAQ themes and priority article topics
- Produces step-by-step tutorials with explicit screenshot placement notes
- Includes video script guidance for visual walkthrough content
- Writes search-optimized KB copy aimed at self-service discovery
- Tracks self-service deflection metrics to quantify documentation impact
Adoption & trust: 516 installs on skills.sh; 173 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are answering the same support questions in chat and email instead of publishing findable help articles that scale.
Who is it for?
Solo founders with live users, a backlog of support tickets, and no dedicated docs team who want deflection-focused help content fast.
Skip if: Teams with no support data yet, purely internal API reference-only docs, or cases where you only need a one-off marketing landing page with no self-service intent.
When should I use this skill?
User asks for help with knowledge base content, FAQs from support, tutorials, or reducing tickets through documentation—e.g. "Help me with [use case]", "Generate [output type]", "Create [deliverable]".
What do I get? / Deliverables
You get structured KB drafts—FAQs, tutorials with media guidance, SEO-oriented copy, and deflection metrics—plus actionable recommendations to publish and measure ticket reduction.
- Markdown KB package with FAQs, tutorials, and video script guidance
- Search-optimization notes for article titles and headings
- Deflection metrics framing and recommendation next steps
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Self-service documentation and ticket deflection are core Grow outcomes once you have real users asking the same questions repeatedly. Support is the canonical shelf because the skill starts from ticket analysis and optimizes for reducing inbound support volume.
Where it fits
Cluster last month's tickets into FAQ candidates and draft articles that answer the top five repeat issues.
Bootstrap a help center structure with tutorials and screenshot notes before public launch.
Publish onboarding walkthroughs that cut launch-week support spikes from new signups.
How it compares
Use instead of free-form chat summaries of tickets when you need repeatable article templates and deflection tracking, not ad-hoc replies.
Common Questions / FAQ
Who is knowledge-base-builder for?
Solo and indie builders running customer-facing products who handle support themselves and want ticket-driven documentation that users can find without contacting them.
When should I use knowledge-base-builder?
In Grow/support when ticket themes pile up; in Build/docs when standing up a help center; in Operate/support when measuring whether published articles reduce repeat contacts—especially after launches or pricing changes spike questions.
Is knowledge-base-builder safe to install?
Treat pasted ticket text as sensitive customer data; review the Security Audits panel on this Prism page before installing, and avoid sending secrets or full PII into the agent context.
SKILL.md
READMESKILL.md - Knowledge Base Builder
# Knowledge Base Builder FAQ identification from support tickets, step-by-step tutorial creation, screenshot/video script guidance, search optimization, and self-service deflection tracking. ## Instructions You are an expert knowledge management specialist. Analyze support tickets to identify recurring questions and create comprehensive knowledge base articles. Generate: FAQ sections, step-by-step tutorials with screenshots placement, video script guidance, search-optimized content, and self-service deflection metrics. Focus on reducing ticket volume through excellent documentation. ### Output Format ```markdown # Knowledge Base Builder Output **Generated**: {timestamp} --- ## Results [Your formatted output here] --- ## Recommendations [Actionable next steps] ``` ### Best Practices 1. **Be Specific**: Focus on concrete, actionable outputs 2. **Use Templates**: Provide copy-paste ready formats 3. **Include Examples**: Show real-world usage 4. **Add Context**: Explain why recommendations matter 5. **Stay Current**: Use latest best practices for customer-support ### Common Use Cases **Trigger Phrases**: - "Help me with [use case]" - "Generate [output type]" - "Create [deliverable]" **Example Request**: > "[Sample user request here]" **Response Approach**: 1. Understand user's context and goals 2. Generate comprehensive output 3. Provide actionable recommendations 4. Include examples and templates 5. Suggest next steps Remember: Focus on delivering value quickly and clearly!