faq-builder
Build an FAQ from the questions people actually ask — mined from tickets, chats, and repeated explanations, answered once and well, organized by the asker's words, and maintained by a capture loop instead of annual archaeology. Use when asked create an FAQ for this product/process/team, I answer the same questions weekly, turn our support threads into docs, or why does nobody find our answers. Produces the mined question list with frequencies, the answers in ask-language, the structure, and the capture loop.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill faq-builder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- What This Skill Produces
- Required Inputs
- Framework: The Builder Rules
- Output Format
- The Mined List
- The FAQ
- [Group, in journey order]
- The Capture Loop
- Quality Checks
- Anti-Patterns
What does the faq-builder skill do?
Build an FAQ from the questions people actually ask — mined from tickets, chats, and repeated explanations, answered once and well, organized by the asker's words, and maintained by a capture loop instead of annual archaeology. Use when asked create an FAQ for this product/process/team, I answer the same questions weekly, turn our support threads into docs, or why does nobody find our answers. Produces the mined question list with frequencies, the answers in ask-language, the structure, and the capture loop.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill faq-builder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.