faq-builder
Skill0 starsChanged 48 days agoMITView on GitHub
Build cited FAQs from supplied approved documents, with explicit no-answer behavior when policy or pricing is absent.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- kesslernity/awesome-mistral-vibe-skillstheir own version, first seen Oct 20, 2026
- kesslernity/awesome-copilot-agent-skillstheir own version, first seen Oct 13, 2026
- nawazxz/20-claude-skills-for-businesstheir own version, first seen Aug 12, 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
- nawazxz/20-claude-skills-for-business★ 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 repository9 other files it gives its agents.
- content-qaSkill
- eval-engineering-liteSkill
- evidence-contentSkill
- failure-analyzerSkill
- meeting-to-actionsSkill
- project-handoffSkill
- requirement-clarifierSkill
- research-synthesizerSkill
- workflow-plannerSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Use when a user supplies source documents and needs audience-specific questions answered from those sources.
- Very specific: line 28
Write only the supported portion.
- Distinctive: line 29
Check each citation points to the asserted fact and preserves qualifications.
- Very specific: line 42
Run python3 tests/validate.py from the repository root to check this skill's contract and example provenance.
“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
Purpose
Produce a traceable FAQ without inventing policies, prices or citations.
When to Use
Use when a user supplies source documents and needs audience-specific questions answered from those sources.
Inputs
source_docs: [{id,text,visibility,approved}], audience, questions[].
Outputs
faq: [{question,answer,citation_ids,status}], unanswered[], source_gaps[].
Workflow
- Reject or quarantine documents not approved for this audience.
- For each question, identify exact supporting source spans before drafting the answer.
- Write only the supported portion; if no span suffices, set status
NO_ANSWER. - Check each citation points to the asserted fact and preserves qualifications.
- Return unanswered questions as explicit knowledge gaps for human review.
Failure Handling
Missing or conflicting sources produce NO_ANSWER or CONFLICT, never a guessed answer. Private source material must not be copied into a public FAQ.
Example
synthetic_unverified: a fictional guide says support is 09:00–17:00, so cite its ID; a pricing question without a source is unanswered.
Tests
Run python3 tests/validate.py from the repository root to check this skill's contract and example provenance. This is a structural test, not model-quality evidence.
Limitations
Citations are only as trustworthy and current as the supplied documents; there is no independent fact verification.
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.