Preface

Customer service and operations teams often scatter Q&A across chat records, support tickets, and community threads. Manually organizing FAQs is time-consuming, and it’s difficult to merge different phrasings of the same question. Relying solely on general conversation to have a model “write an FAQ” often lacks frequency statistics, similar question merging, and alignment with actual customer service responses.

Below is an introduction to the SkillHub community skill FAQ Auto-Extraction (@user_70c2f807/faq-auto-extractor, v1.0.0). It constrains the Agent through a standard SKILL.md: when users provide anonymized conversation data, it extracts high-frequency questions, generates standard answers, and outputs categorized results according to fixed steps. It’s suitable as a preparatory step for knowledge base maintenance.

What Is This

FAQ Auto-Extraction is a community Skill published on SkillHub (Category: knowledge-management), coordinates @user_70c2f807/faq-auto-extractor, published by user_70c2f807, current version 1.0.0, with tags indicating requires_api_key=false (no separate API Key configuration needed for installation and use).

Positioning: Identify questions from customer service chat records, user feedback, or community conversations; merge similar questions; sort by occurrence frequency; and generate standard answers based on customer service responses in the conversations. Supports classification by topic and various text-based outputs (lists, tables, Q&A pairs). The Skill description explicitly states it is not for building customer service systems, chatbot development, or knowledge graph construction.

Official entry points:

  • SkillHub Page: https://www.skillhub.cn/skills/user_70c2f807/faq-auto-extractor
  • API Coordinates: https://api.skillhub.cn/user_70c2f807/faq-auto-extractor

(SkillHub page shows a score of 100000; fetched metadata indicates approximately 878 downloads.)

Core Features

The following capabilities all come from this Skill’s SKILL.md documentation, which the Agent will execute according to the documentation after installation.

  1. Trigger scenarios: Enabled when users mention FAQ extraction, common question extraction, customer service Q&A, knowledge base generation, or request FAQ extraction from chat logs; not involved in real-time conversation flows or system integration development.
  2. Question side: Identify user questions from unstructured conversations; merge questions with different wording but similar semantics; sort by occurrence frequency.
  3. Answer side: Extract corresponding content from customer service responses, synthesize multiple answers to generate standard answers; emphasize completeness and actionability, and suggest manual review by business parties (especially for policy-related content).
  4. Organization and output: Classify by topic/scenario; attach keywords to entries for easier retrieval; support list, table, Q&A pair formats, and adjust to more conversational phrasing based on user requests.
  5. Data and boundaries: Must be provided by users with chat records, tickets, or feedback text; cannot generate from nothing; recommends at least 50 conversations, with 200+ being more effective; anonymization of names, phone numbers, order numbers, etc. is required before processing; the Skill declares it does not store user-provided chat records.

The execution process is divided into four steps in the documentation: Obtain and clean data → Extract and merge questions, count frequency → Generate standard answers → Classify and output in preferred format. Output can include high-frequency question ranking tables, topic-based FAQ content, and supplementary suggestion lists of “high-frequency questions lacking standard answers”.

Installation and Activation

Before installation, ensure SkillHub CLI is available on your machine; if not, you can first check or install according to the official installation documentation:

command -v skillhub && skillhub --version

If not installed, you can use the installation script in the SkillHub documentation (full installation or CLI only), see https://skillhub.cn/install/skillhub.md Section 1 for details.

Method 1: Command line installation to the current Agent’s skills directory

When installing, you must use --dir to point to the skills path that the Agent actually reads; otherwise, it may fall into ./skills/ by default and not be recognized:

skillhub install faq-auto-extractor --namespace user_70c2f807 --dir <your skills directory>

Common paths (from SkillHub installation documentation):

  • Cursor: ~/.cursor/skills/
  • Codex: ~/.codex/skills/ or .agents/skills/ under the project
  • Claude Code: ~/.claude/skills/

Method 2: Let the Agent install according to prompts

The installation prompt provided by the SkillHub page is: Please install @user_70c2f807/faq-auto-extractor according to https://skillhub.cn/install/skillhub.md.

After installation, restart or refresh the Agent to load the new Skill.

Typical Usage

The interactive examples in the Skill documentation can be summarized into the following reproducible workflow.

  1. User initiates: “Help me extract FAQs” → Agent should ask the other party to paste customer service chat records or user feedback.
  2. User provides a batch of conversations (approximately 100 in the documentation example) → Agent analyzes high-frequency questions, sorts by frequency, and generates standard answers.
  3. User requests “The answers are too formal, make them conversational” → Agent adjusts answer tone.
  4. User requests “Help me categorize” → Agent divides by topic (e.g., logistics, returns/exchanges, product usage).
  5. User requests “Export as table format” → Agent outputs table content suitable for copying or importing into customer service systems.

For data formats, the Skill documentation states that plain text, CSV, and JSON are all acceptable; the more structured, the faster the processing; it also mentions that Excel and similar formats need to be organized by the user into a text format readable by the Agent (this Skill package does not contain independent conversion scripts, only SKILL.md and metadata).

The output skeleton provided in the documentation includes: number of data source records, number of extracted questions, number of categories; high-frequency question ranking table (rank, question, frequency, category); topic-based Q/A and keywords; and a list of high-frequency questions lacking answers that are suggested for supplementation.

Applicable Scenarios and Considerations

Suitable for

  • Customer service, operations, or knowledge base maintenance personnel who have anonymized historical conversations or ticket text and need to quickly obtain FAQ drafts and frequency priorities.
  • Teams that want to reduce duplicate Q&A and unify “one standard answer for the same question”.
  • Need to organize mixed Chinese-English records into FAQs (Skill documentation supports output classification by language).

Limitations and Considerations

  • Only produces FAQ text/tables, does not build bots or integrate with customer service system APIs; importing into Zendesk, ZhiChi, etc. requires using the system’s batch import capabilities (Skill mentions it can output CSV/JSON formats, specific fields are based on Agent generation according to documentation).
  • Answers are summarized from historical responses and must be manually reviewed before entering the knowledge base; activity and policy-related content needs to be confirmed for timeliness.
  • When data volume is too small, the documentation will prompt that results may be incomplete; if content is mainly casual chat/complaints with lack of clear Q&A, need to confirm with users whether to change to extracting “concerns”.
  • Real-time conversation analysis, user profiling, knowledge graphs, etc. are not within the scope of this Skill.

Not suitable for (Summarized from Skill documentation table): Building customer service bots, real-time stream analysis, complex knowledge graphs, marketing copy generation as the primary goal.

Conclusion

FAQ Auto-Extraction writes “from conversations to FAQ drafts” as steps and output specifications that Agents can follow, suitable as an extraction step in the knowledge management (knowledge-management) workflow; implementation still depends on anonymized data, sufficient sample size, and business review. For installation and details, see SkillHub: https://www.skillhub.cn/skills/user_70c2f807/faq-auto-extractor , coordinates page: https://api.skillhub.cn/user_70c2f807/faq-auto-extractor .