Knowledge Base Copilot
A help section that answers this month's questions, not the ones from launch day
The problem
The [FAQ & Knowledge Base Builder](/toolbox/faq-knowledge-base-builder) writes a solid help section once, and then reality starts drifting away from it: customers invent new questions, the answers to old ones change, and the article everyone actually needed never gets written because nobody was tracking what people keep asking. A knowledge base is not a document, it is a garden, and gardens need a gardener with a memory. This skill installs one.
The tool
Once installed, this skill turns your assistant into the keeper of your help content. Seed it with the articles you have (built with the FAQ Builder or pasted from wherever they live), and then feed it the raw signal as it happens: two-line reports of what a customer asked, which article failed to answer, what changed in the business.
The standing loop is the value. Every reported question gets logged against the knowledge base: answered by an existing article (noted, so demand is measurable), answered badly (the article gets a proposed fix), or unanswered (it joins the to-write list ranked by how often it comes up). When something changes in the business (a price, a policy, a process), one report sweeps every affected article and returns the exact edits. And the monthly read tells you the three things a help section can uniquely reveal: what customers ask most, which answers are working, and which question keeps arriving even though the article exists, which usually means the article is unfindable or the product is confusing, and it says which it suspects.
What's inside
- Seeding from your existing help content, whatever shape it is in
- Question logging from two-line reports, mapped to articles: answered, answered badly, missing
- A ranked to-write list built from real demand, not guesses
- Change sweeps: report one business change, get every affected article's exact edit
- Draft articles in your voice for anything on the to-write list, on request
- A monthly read: top questions, failing articles, and the repeat-question flag with a suspected cause
How to use it
- 1Click "Install skill" on this page and copy the install prompt.
- 2Paste it into your AI assistant (Claude, ChatGPT, anything that accepts pasted text).
- 3Seed it with your current articles, even messy ones.
- 4Report questions as they arrive, two lines each; that habit is the entire system.
- 5Monthly, read the report, approve the proposed edits, and publish the top item on the to-write list.
Example
An online pottery-supplies shop seeds the skill with eleven help articles. Over a month, the owner reports questions as they land. The log shows the shipping article answering well (nine hits), the clay-shrinkage article answering badly (three customers asked follow-ups; a fix is proposed with plainer numbers), and a question with no article at all arriving five times: "can I mix your glazes with brand X?" That becomes the top of the to-write list, drafted the same day, in the shop's voice, with the honest "we have tested these six combinations" framing the owner gives it. When the shop changes its free-shipping threshold, one report returns the four articles that mention it with exact edits. The monthly read flags that "where is my order" keeps arriving despite a good article, and suspects the confirmation email is not linking it, which turns out to be true.
Pro tip
Report the question in the customer's words, not your summary; "do your glazes work on stoneware" and "glaze compatibility" are the same topic and different search behavior, and the article should carry their phrasing. Pair the skill with the [Customer Support Autopilot](/toolbox/customer-support-autopilot): the autopilot answers with the knowledge base, and this skill is what keeps the knowledge base worth answering with.
Related tools
Want this customized and automated for your business?
We take the tools in this toolbox and wire them into your business: your data, your brand voice, running on autopilot.
Talk to Vexlo