faq-builder
Skill0 starsChanged 3 months agoMITView on GitHub
Build an FAQ from product docs, support tickets, or notes. Use when someone has raw material about a product or service and wants a clean set of question-and-answer pairs customers can self-serve from.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- zhouey314-cloud/ai-agent-skillstheir own version, first seen Oct 20, 2026
- kesslernity/awesome-mistral-vibe-skillstheir own version, first seen Oct 20, 2026
- kesslernity/awesome-copilot-agent-skillstheir own version, first seen Oct 13, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- kesslernity/awesome-copilot-agent-skills★ 16same name
- kesslernity/awesome-mistral-vibe-skills★ 1same name
- zhouey314-cloud/ai-agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- ad-copySkill
- blog-writerSkill
- cold-outreachSkill
- content-repurposerSkill
- contract-summarizerSkill
- crm-note-cleanerSkill
- data-cleanerSkill
- expense-summarySkill
- follow-up-emailSkill
- invoice-builderSkill
- lead-qualifierSkill
- meeting-notesSkill
- newsletter-writerSkill
- proposal-writerSkill
- review-responderSkill
- social-post-packSkill
- sop-writerSkill
- support-replySkill
- weekly-reportSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Write each question the way a customer would actually phrase it.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
FAQ Builder
Turn what customers keep asking into answers they can find themselves.
Inputs needed
- The source material: docs, a list of past questions, tickets, or product notes.
- (Optional) The audience and the tone wanted.
Steps
- Extract the real questions people have (from tickets) or would have (from docs).
- Group them into logical sections (getting started, billing, troubleshooting, etc.).
- Write each question the way a customer would actually phrase it.
- Answer plainly and completely, in 2-4 sentences where possible.
- Order questions within each section from most to least common.
Output format
[Section]
Q: customer-phrased question
A: clear, complete answerRepeat per section. Note any questions the source couldn't answer, so someone can fill them.
Voice & rules
- Phrase questions in the customer's words, not internal jargon.
- Answer the question actually asked; don't dodge into marketing.
- Flag gaps rather than making up an answer.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

