FAQ Builder from Support
Most FAQ sections are written by marketing — questions nobody asks, answered in language nobody uses. The FAQ Builder from Support starts from your actual ticket queue and produces an FAQ that demonstrably drops volume.
What this skill does
A good FAQ is a deflection system, not a marketing page. The FAQ Builder from Support starts from real tickets, chat logs, and emails — not from what the team thinks customers should ask. It runs the SORT framework: Surface the real questions (cutting through the emotional context to the underlying ask), Organise by category along the customer journey, Rank by ticket volume and impact, Transform into answers that resolve the issue.
Customer language is treated as non-negotiable. People search in their own words, not yours. "How do I cancel?" gets through the search; "Subscription termination process" does not. The skill keeps verbatim phrasing from real tickets wherever it appears repeatedly, and resists the marketing-team instinct to soften everything into corporate voice.
Answers follow three rules: direct response in the first sentence, no preamble ("Great question! Let me explain how our billing system works..." is rejected), and end with a next step if the answer might not cover every edge case. Cap at 3-4 sentences for simple questions; numbered steps for process questions; link to a deeper article when the answer earns one. Length discipline is what separates a useful FAQ from a wall of policy text.
The top five questions get featured at the top because that's where most FAQ visitors stop. If 74% of tickets cluster on five questions, ranking them by volume and putting them in the prime slot is worth more than the other 50 entries combined. The skill quantifies this from the raw data you paste — frequency counts, ticket categories, and the questions that correlate with churn signals so they jump the queue.
Maintenance is treated as part of the deliverable, not an afterthought. Every output includes an internal-notes section flagging questions that came up but didn't make the cut, emerging themes that need more data before adding, and a recommended review cadence. A FAQ that never gets updated loses accuracy fast — new features, retired integrations, policy shifts all leak in within a quarter. The skill ships the document AND the routine to keep it honest.
When this triggers
- ·You have months of support tickets and the same five questions keep landing in the queue
- ·Your current FAQ was written before launch and reads nothing like how customers actually phrase things
- ·You want a help page that deflects tickets rather than one that exists for SEO appearance
- ·You're hiring a second support agent and need to ship the obvious deflections before they start
- ·You've launched a new feature and the same misunderstanding is coming up in every ticket
Example
Trigger
User pastes 60 raw support messages from the last quarter. SaaS product, 800 customers, common themes around billing, exports, and login.
Output
FAQ — [Product Name] Top 5 Questions (74% of queue) Q: How do I cancel my subscription? A: Go to Settings → Billing → Cancel Plan. You keep access until the end of the current billing period and you won't be charged again. You can reactivate from the same page if you change your mind. Q: Why was I charged twice this month? A: This usually means your plan upgraded mid-cycle. The smaller charge is a prorated top-up for the new tier; the larger one is the next full month at the new rate. You can see the breakdown under Settings → Billing → History. Q: How do I export my data as a CSV? A: Open any report, click Export top-right, choose CSV, click Download. Exports include the filters you have applied. For multi-report exports, see [link]. [+ 12 more, grouped by Getting Started, Features, Billing, Troubleshooting, Account] FAQ Maintenance Notes (Internal) Questions to add next: 4 emerging themes around the new Reports v2 launch — too early to confirm pattern, revisit in 4 weeks. Questions removed: 3 questions about the old Slack integration retired last quarter. Review schedule: monthly.
Get this skill + 7 more
Get the full Customer Support pillar (8 skills) or the complete library.
Get the full stack — $299What you get
- 161-line SKILL.md, ready to drop into ~/.claude/skills/
- Tested through 3 Karpathy-loop iterations (versions v1.0.0 → v1.3.0)
- Triggers automatically when relevant — no command to remember
- Lifetime updates as the skill is refined further
More from Customer Support
Not generic "just checking in" messages — strategic outreach timed to customer milestones, usage patterns, and relationship stages that make clients feel valued and remind them why they're paying
Takes messy ticket threads — multiple back-and-forth messages, emotional context, technical details — and distill them into a summary that lets the next person pick up the case immediately without…
Writes for frustrated, impatient users who want answers fast — not for people browsing leisurely
Writes responses that resolve the situation professionally — whether that means granting the refund gracefully, offering an alternative, or declining while preserving the relationship
Takes a product or service, identify the 10 most common support scenarios, and create templated response frameworks for each
Doesn't just answer the question — it reads the emotional temperature of the message, match the appropriate escalation level, resolve the issue clearly, and leave the customer feeling heard and helped
Browse the full library
297 skills across 31 categories. One purchase, lifetime updates.
See all bundles