FAQ Builder Skill

FAQs fail when they're written from the inside: questions the team wishes people asked ("What makes our approach unique?"), phrased in the team's vocabulary, frozen at launch. The working FAQ is mined — from tickets, chat searches, and the questions someone answers every week — phrased in the asker's words (findability is vocabulary-matching; nobody searches for "provisioning cadence" when their question is "how long until it works"), answered once and well, and kept alive by a capture loop: every newly-repeated question flows in, because the FAQ is a cache of answers and caches need writes.

What This Skill Produces

• The mined question list — real questions with rough frequencies and sources, deduplicated by intent
• The answers — direct-first (the answer, then the caveat), in ask-language, each with an owner
• The structure — ordered by frequency within asker-journey groups, question-phrased headings
• The capture loop — the answered-it-twice rule that keeps the FAQ current

Required Inputs

Ask for these if not provided:

• The question sources — tickets, chat logs, inbox searches, the team's "I keep explaining…" list; mining needs raw material, and the wish-list questions are explicitly not it
• The askers — customers, new hires, other teams? Their vocabulary (from the actual questions) becomes the headings' language
• The answer authority — who signs off that each answer is correct (an FAQ with confident wrong answers is worse than none); per-topic owners named
• Where it will live — the wiki, the docs site, the bot's knowledge base — findability mechanics differ, and answers should be written to be found there