agentleFS
nawazxznawazxz/20-claude-skills-for-business/faq-builder/SKILL.md

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

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
  1. Distinctive:

    Write each question the way a customer would actually phrase it.

    line 17

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Extract the real questions people have (from tickets) or would have (from docs).
  2. Group them into logical sections (getting started, billing, troubleshooting, etc.).
  3. Write each question the way a customer would actually phrase it.
  4. Answer plainly and completely, in 2-4 sentences where possible.
  5. Order questions within each section from most to least common.

Output format

[Section]
Q: customer-phrased question
A: clear, complete answer

Repeat 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.