{"id":"ce513fed-dba3-41b8-8cb9-fb09d03d857c","entityType":"agent","slug":"clawhub-leooooooow-faq-builder","name":"FAQ Builder","canonicalUrl":"https://www.xpersona.co/agent/clawhub-leooooooow-faq-builder","canonicalPath":"/agent/clawhub-leooooooow-faq-builder","generatedAt":"2026-10-12T19:57:22.194Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T21:12:07.849Z","emptyReason":null},"description":"Generate comprehensive, conversion-focused FAQ sections for ecommerce product pages by systematically analyzing real customer questions, return data, and pur... Skill: FAQ Builder Owner: leooooooow Summary: Generate comprehensive, conversion-focused FAQ sections for ecommerce product pages by systematically analyzing real customer questions, return data, and pur... Tags: latest:1.1.0 Version history: v1.1.0 | 2026-06-05T14:40:44.220Z | user Version 1.0.2 of faq-builder - No file changes detected in this release. - Content, functionality, and documentation remain unchanged fr","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 992 downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17974h9acjg4h7h5djv1hg51d83hcca:faq-builder","sourceUrl":"https://clawhub.ai/leooooooow/faq-builder","homepage":"https://clawhub.ai/leooooooow/skills/faq-builder","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/leooooooow/faq-builder","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/leooooooow/skills/faq-builder","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Generate comprehensive, conversion-focused FAQ sections for ecommerce product pages by systematically analyzing real customer questions, return data, and pur..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T21:12:07.849Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T21:12:07.849Z","emptyReason":null},"stars":null,"forks":null,"downloads":992,"likes":null,"task":null,"library":null,"packageName":null,"latestVersion":"1.1.0","tractionLabel":"992 downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T21:12:07.836Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T21:12:07.849Z","lastCrawledAt":"2026-10-11T21:12:07.836Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T21:12:07.836Z","lastVerifiedAt":null,"highlights":[{"version":"1.1.0","createdAt":"2026-06-05T14:40:44.220Z","changelog":"Version 1.0.2 of faq-builder - No file changes detected in this release. - Content, functionality, and documentation remain unchanged from the previous version. - Release may address metadata or platform-level updates not affecting user-facing features.","fileCount":7,"zipByteSize":12927},{"version":"1.0.1","createdAt":"2026-06-05T14:37:51.519Z","changelog":"Version 1.0.1 introduces supporting resources and updates documentation: - Added key documentation: output-template.md, platform-formatting-guide.md, quality-checklist.md, and question-bank.md for enhanced usability. - Expanded SKILL.md with a Quick Reference table, step-by-step workflow, and platform-specific formatting advice. - Removed skill-card.md (redundant or replaced by new documentation). - Refined scope and guidance to improve FAQ quality, platform integration, and maintenance best practices.","fileCount":7,"zipByteSize":12862},{"version":"1.0.0","createdAt":"2026-04-20T01:30:31.740Z","changelog":"Initial release.","fileCount":3,"zipByteSize":3827}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17974h9acjg4h7h5djv1hg51d83hcca:faq-builder","setupComplexity":"low","setupSteps":["Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-faq-builder/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-faq-builder/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-faq-builder/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-faq-builder/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-faq-builder/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-faq-builder/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-12T19:57:22.193Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-faq-builder/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-faq-builder/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-faq-builder/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-faq-builder/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T21:12:07.849Z","emptyReason":null},"readme":"Skill: FAQ Builder\n\nOwner: leooooooow\n\nSummary: Generate comprehensive, conversion-focused FAQ sections for ecommerce product pages by systematically analyzing real customer questions, return data, and pur...\n\nTags: latest:1.1.0\n\nVersion history:\n\nv1.1.0 | 2026-06-05T14:40:44.220Z | user\n\nVersion 1.0.2 of faq-builder\n\n- No file changes detected in this release.\n- Content, functionality, and documentation remain unchanged from the previous version.\n- Release may address metadata or platform-level updates not affecting user-facing features.\n\nv1.0.1 | 2026-06-05T14:37:51.519Z | user\n\nVersion 1.0.1 introduces supporting resources and updates documentation:\n\n- Added key documentation: output-template.md, platform-formatting-guide.md, quality-checklist.md, and question-bank.md for enhanced usability.\n- Expanded SKILL.md with a Quick Reference table, step-by-step workflow, and platform-specific formatting advice.\n- Removed skill-card.md (redundant or replaced by new documentation).\n- Refined scope and guidance to improve FAQ quality, platform integration, and maintenance best practices.\n\nv1.0.0 | 2026-04-20T01:30:31.740Z | user\n\nInitial release.\n\nArchive index:\n\nArchive v1.1.0: 7 files, 12927 bytes\n\nFiles: output-template.md (904b), platform-formatting-guide.md (4216b), quality-checklist.md (2094b), question-bank.md (3035b), skill-card.md (2429b), SKILL.md (12495b), _meta.json (130b)\n\nFile v1.1.0:SKILL.md\n\n---\nname: FAQ Builder\ndescription: Generate comprehensive, conversion-focused FAQ sections for ecommerce product pages by systematically analyzing real customer questions, return data, and purchase objections.\n---\n\n# FAQ Builder\n\nGenerate comprehensive, conversion-focused FAQ sections for your product pages by systematically analyzing the questions real customers ask, the reasons they return products, and the objections that stall purchases. Instead of guessing what buyers want to know, this skill builds FAQ content grounded in actual customer pain points, structured to resolve hesitation at the moment it arises and reduce the support ticket volume that drains your team's bandwidth.\n\n## Quick Reference\n\n| Decision | Strong | Acceptable | Weak |\n|---|---|---|---|\n| FAQ source data | Support tickets + return reasons + review Q&A + competitor listings | Support tickets only | Writing from memory what you think customers ask |\n| Number of FAQs | 8–15 per product, grouped by topic | 5–7 ungrouped FAQs | 2–3 FAQs or 20+ with no grouping |\n| Answer length | 2–5 sentences with specifics (dimensions, materials, compatibility) | 1 sentence answer without detail | One-word answers or answers that raise new questions |\n| Objection handling | Explicitly names the concern before resolving it | Answers question without acknowledging doubt | Defensive or dismissive tone |\n| Platform formatting | Matches platform specs (Amazon character limits, Shopify accordion, TikTok Shop) | Generic HTML list format | Plain text wall, no formatting |\n| SEO integration | Target keywords woven naturally into answers | Keywords in questions only | No keyword consideration |\n| Update cadence | Reviewed and updated after new support ticket spikes | Reviewed quarterly | Never updated after initial publish |\n\n## Solves\n\n- Product pages that generate high support ticket volume for the same repeated questions\n- Return rates driven by \"not as described\" or \"wrong size/compatibility\" — both addressable with FAQs\n- Conversion drop-off at the product page because buyers can't find answers before checkout\n- Listings that lose to competitors whose pages are more complete and trust-building\n- Support team spending hours answering questions that should be self-serve\n- New product launches with no existing review base to signal trustworthiness\n- Marketplaces penalizing listings with high \"buyer question\" rates (Amazon A9 signals)\n\n## Workflow\n\n### Step 1 — Gather Source Data\n\nThe quality of your FAQ is entirely determined by the quality of your input data. Collect:\n\n**Tier 1 sources (highest signal):**\n- Support ticket exports filtered by product — look for question patterns appearing 3+ times\n- Return reason data — \"not as described,\" \"wrong size,\" \"missing feature\" all translate to FAQ entries\n- Amazon Buyer Questions on your listing and competitor listings in the same category\n- 1-star and 2-star review text — complaints reveal unmet expectations you can preemptively address\n\n**Tier 2 sources (supplemental):**\n- Your own product team's anticipated questions (useful for technical specs)\n- Competitor listing Q&A sections (reveals what buyers in your category commonly wonder)\n- Reddit and forum threads where buyers discuss products in your category\n- Google autocomplete for \"[product type] does it...\" / \"[product type] is it compatible with...\"\n\nMinimum viable input: product description, 3 top support ticket categories, and 5 real customer questions.\n\n### Step 2 — Categorize Questions by Intent\n\nGroup raw questions into intent buckets before writing answers:\n\n| Category | Examples | FAQ priority |\n|---|---|---|\n| Compatibility / fit | \"Does this work with X?\" \"What size should I get?\" | High — prevents returns |\n| Shipping / fulfillment | \"How long does delivery take?\" \"Do you ship to X?\" | High — pre-purchase anxiety |\n| Product specs | \"What material is it made of?\" \"How many units included?\" | Medium — listing gap filler |\n| Usage / instructions | \"How do I set this up?\" \"Can it be used for X?\" | Medium — reduces support tickets |\n| Returns / warranty | \"What's the return policy?\" \"Is there a warranty?\" | High — purchase risk reducer |\n| Authenticity / quality | \"Is this the real brand?\" \"Is the quality good?\" | High — trust signal for new listings |\n| Comparison | \"How is this different from [competitor]?\" | Medium — consideration stage |\n\n### Step 3 — Write Answers Using the ACES Framework\n\nEach FAQ answer should follow: **Acknowledge → Clarify → Expand → Seal**\n\n- **Acknowledge**: Name the concern or question directly\n- **Clarify**: Give the direct, specific answer (number, yes/no, dimension)\n- **Expand**: Add the detail that turns the answer into confidence (\"the [material] ensures...\")\n- **Seal**: End with a trust signal or action if applicable\n\n**Example:**\n- Q: \"Is this water-resistant?\"\n- Weak answer: \"Yes it is.\"\n- ACES answer: \"Yes, the [product] is IPX6-rated water-resistant, meaning it handles heavy rain, splashing, and sweat without damage. It is not designed for submersion — don't use it underwater. This makes it ideal for outdoor workouts, hiking, and daily commutes in wet weather.\"\n\n### Step 4 — Format for Platform\n\n**Amazon:**\n- Use the Seller Central Q&A feature and A+ Content FAQ module\n- Character limit: ~1,000 characters per answer in A+\n- Questions should contain relevant search keywords\n- Lead with the most important information (Amazon may truncate)\n\n**Shopify:**\n- Use accordion-style FAQ apps (Acecart, HelpCenter, or custom sections)\n- No character limit — prioritize readability over compression\n- Include internal links to size guides, shipping pages, return policy\n- Place FAQ section above the fold on product pages for high-anxiety categories\n\n**TikTok Shop:**\n- Shorter answers (2–3 sentences maximum)\n- Mirror the casual, direct tone of TikTok content\n- Prioritize shipping speed and return policy (top buyer concerns on the platform)\n\n**WooCommerce / generic:**\n- Use schema markup (FAQPage schema) for Google rich result eligibility\n- Structured data can generate FAQ accordion directly in SERPs\n\n### Step 5 — Prioritize and Sequence\n\nOrder your FAQs to map the buyer's journey — put purchase blockers first:\n\n1. Compatibility / fit (prevent the \"wrong item\" return)\n2. Shipping and delivery timeline\n3. Return and refund policy\n4. Quality and material details\n5. Usage and setup questions\n6. Comparison and differentiation\n\nNever lead with company background or brand story FAQs — buyers at the product page want answers about the product, not your origin story.\n\n### Step 6 — Optimize for SEO\n\n- Include primary and secondary keywords in 30–40% of answers\n- Use long-tail question formats Google shows in \"People Also Ask\": \"Can you use [product] for [use case]?\"\n- Avoid keyword stuffing — one natural mention per answer is enough\n- For Shopify: create a dedicated /faq page with schema markup to capture SERP FAQ real estate\n\n### Step 7 — Set Up Maintenance Triggers\n\nFAQs decay. Set up:\n- Support ticket spike alerts: if a question type spikes 30%+ in a week, add or update the FAQ\n- Quarterly review: pull fresh support data and compare against published FAQs\n- Post-return analysis: after each return batch, check if reasons are addressable with FAQ updates\n- Review mining: flag new 1- and 2-star reviews monthly for new FAQ candidates\n\n## Examples\n\n### Example 1 — Kitchen Gadget (Shopify + Amazon)\n\n**Product:** Adjustable mandoline slicer, 3 SKUs (different blade sets)  \n**Source data:** 47 support tickets in 90 days; top issues: blade compatibility between SKUs, cleaning instructions, safety concerns with the guard  \n**Return reasons:** \"cut myself using it\" (22%), \"blades don't fit my model\" (18%)\n\n**FAQ output (top 5 by priority):**\n\n**Q: Will the extra blades from the 5-blade set fit my 3-blade model?**  \nA: No — the blade sets are model-specific and not cross-compatible. The 3-blade model uses a narrower frame than the 5-blade model. If you're unsure which model you have, the model number is printed on the underside of the frame. Contact us with your order number and we'll confirm compatibility before you purchase additional blades.\n\n**Q: Is the hand guard required to use the slicer?**  \nA: Yes — we strongly recommend always using the included cut-resistant hand guard. The mandoline blade is razor-sharp and 68% of customer injuries we've seen occurred without the guard in use. The guard fits all slice thicknesses and is dishwasher safe.\n\n**Q: How do I clean the blades safely?**  \nA: Use the included brush (not a sponge or cloth) to clean blades under running water. Always push the brush away from the blade edge, never toward it. Blades are not dishwasher safe — the heat warps the edge over time.\n\n**Result:** Return rate fell from 14% to 8% in 60 days after FAQ publish. Support tickets for the top 3 questions dropped 61%.\n\n---\n\n### Example 2 — Apparel (TikTok Shop, new listing)\n\n**Product:** Oversized fleece hoodie, women's, 5 colors  \n**Source data:** No prior tickets (new listing); competitor listing Q&A mined; top 3 competitor concerns: sizing runs large, material pills quickly, hood too small  \n**Return reasons from category:** \"too big\" (41%), \"color different than pictured\" (27%)\n\n**FAQ output (pre-emptive, no support history):**\n\n**Q: How does the sizing run?**  \nA: This hoodie is intentionally oversized — it runs 1–2 sizes large for a relaxed fit. If you prefer a closer fit, size down. Example: our size M fits a typical S–M body (bust 34–38\"). Check the size chart in photos for exact measurements. Still unsure? DM us with your bust/waist measurements and we'll recommend a size.\n\n**Q: Will the fleece pill after washing?**  \nA: We've had zero pilling reports in 200+ orders since launch. The fleece is 320 GSM brushed polyester — denser than the typical 280 GSM hoodies in this price range. Wash inside-out on cold, and it'll hold up for years.\n\n**Q: Does the color match the photos?**  \nA: We photograph under natural light with no filter adjustments. Screens vary slightly, but the colors are true-to-life. All five colorways are shown in the video with natural light + indoor light comparison.\n\n## Common Mistakes\n\n1. **Writing FAQs based on what you think buyers ask** — without checking support tickets, return data, or review mining, you're guessing. Guesses produce FAQs that answer the wrong questions.\n\n2. **One-word or one-line answers** — \"Yes\" and \"No\" answers create new questions instead of resolving them. Every answer needs enough detail to be actionable.\n\n3. **Vague specs** — \"It's pretty big\" or \"durable material\" tells buyers nothing. Replace with: dimensions in inches/cm, material composition percentages, weight in grams.\n\n4. **Burying the FAQ** — An FAQ section below the fold on a product page doesn't get read. High-anxiety categories (electronics, apparel, supplements) need FAQs visible without scrolling.\n\n5. **Ignoring return-driven questions** — Your return reason report is a direct FAQ brief. Every top return reason is an FAQ entry waiting to be written.\n\n6. **Defensive tone** — \"We don't offer refunds because...\" sounds adversarial. Rewrite as policy + benefit: \"We offer 30-day returns because we're confident you'll love it — and if not, the process takes less than 5 minutes.\"\n\n7. **Not formatting for the platform** — A 500-character answer that gets truncated to 150 on Amazon is worse than no answer.\n\n8. **Writing for you, not the buyer** — FAQs about your company history, founder story, or certifications nobody can verify belong on your About page, not the product FAQ.\n\n9. **No maintenance schedule** — FAQs that are accurate at launch become misleading after a policy change, reformulation, or new SKU launch. Set a calendar reminder to review every 90 days.\n\n10. **Skipping schema markup** — For Shopify and WooCommerce stores, FAQPage schema is free and can generate FAQ accordions in Google SERPs, effectively expanding your listing real estate.\n\n## Resources\n\n- [Output Template](references/output-template.md) — FAQ section brief and output format\n- [Question Bank by Category](references/question-bank.md) — Pre-researched common questions by product type\n- [Platform Formatting Guide](references/platform-formatting-guide.md) — Character limits and formatting specs by marketplace\n- [Quality Checklist](assets/quality-checklist.md) — Pre-publish FAQ review checklist\n\nFile v1.1.0:_meta.json\n\n{\n  \"ownerId\": \"kn70fv0ehp50emedet9tx3fekd82pw3b\",\n  \"slug\": \"faq-builder\",\n  \"version\": \"1.1.0\",\n  \"publishedAt\": 1780670444220\n}\n\nFile v1.1.0:output-template.md\n\n# FAQ Section Output Template\n\n## Product Brief\n- **Product name:** \n- **Platform(s):** Amazon / Shopify / TikTok Shop / WooCommerce / Other\n- **SKU count:** \n- **Category:** \n\n## Source Data Summary\n- **Support ticket themes (top 3):**\n  1. \n  2. \n  3. \n- **Top return reasons:**\n  1. \n  2. \n- **Competitor Q&A patterns noted:**\n\n## FAQ Section: [Product Name]\n\n### Compatibility & Fit\n**Q:**  \n**A:** \n\n**Q:**  \n**A:** \n\n### Shipping & Delivery\n**Q:**  \n**A:** \n\n**Q:**  \n**A:** \n\n### Product Specs & Materials\n**Q:**  \n**A:** \n\n**Q:**  \n**A:** \n\n### Usage & Instructions\n**Q:**  \n**A:** \n\n### Returns & Warranty\n**Q:**  \n**A:** \n\n**Q:**  \n**A:** \n\n### Other Questions\n**Q:**  \n**A:** \n\n## SEO Notes\n- Primary keyword used in: Q___, Q___\n- Secondary keywords used in: Q___, Q___\n- Schema markup added: Yes / No / Pending\n\n## Maintenance Log\n| Date | Trigger | Questions updated |\n|---|---|---|\n| | | |\n\nFile v1.1.0:platform-formatting-guide.md\n\n# Platform Formatting Guide for FAQ Sections\n\n## Amazon\n\n### A+ Content FAQ Module\n- Maximum answers per FAQ module: 6–8 (recommended)\n- Character limit per answer: ~1,000 characters\n- Questions should include high-search keywords naturally\n- Images can accompany answers in premium A+ Content\n- FAQs display in an accordion format — question first, answer on expand\n\n### Amazon Customer Q&A (Separate from A+ Content)\n- Sellers can answer any customer question in the Q&A section\n- Responses show as \"Seller\" answer — respond to all questions within 24 hours\n- High-volume Q&As surface to top of listing (Amazon ranks by helpfulness votes)\n- Best practice: answer competitor questions in your category to build authority\n\n### Keyword Strategy for Amazon FAQ\n- Include your primary ASIN keyword in 2–3 answers\n- Include backend search terms that don't fit naturally in bullet points\n- Avoid keyword stuffing — Amazon's algorithm reads FAQs for relevance signals\n\n---\n\n## Shopify\n\n### FAQ Placement Options\n1. **Product page FAQ section** — highest-converting placement for pre-purchase questions\n2. **Dedicated /faq page** — for brand-level questions (returns, shipping, company info)\n3. **Modal / popup** — triggered on exit intent or add-to-cart click (advanced)\n\n### Recommended Apps\n- **HelpCenter** — Native Shopify FAQ with accordion UI, no coding required\n- **Acecart FAQ** — Lightweight, fast-loading\n- **Yotpo** — Integrates FAQ with reviews for social proof combination\n- **Custom Liquid section** — Full control; use `<details>` HTML for native accordion\n\n### Schema Markup for Shopify (FAQPage)\nAdd to your product page or FAQ page template:\n\n```json\n{\n  \"@context\": \"https://schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Does this product come with a warranty?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Yes, all products include a 1-year manufacturer warranty covering defects in materials and workmanship.\"\n      }\n    }\n  ]\n}\n```\n\nSchema markup enables Google to show FAQ accordion directly in search results (rich results), expanding your SERP presence without additional ranking effort.\n\n### Character Guidance\n- No hard limit, but answers longer than 200 words lose readability\n- Aim for 50–150 words per answer on product pages\n- Break long answers into bullet points rather than paragraphs\n\n---\n\n## TikTok Shop\n\n### FAQ Behavior on TikTok Shop\n- Product page FAQs appear in the \"Details\" tab below the listing\n- Buyers on TikTok skim — prioritize short, direct answers\n- Return policy and shipping time are the top 2 buyer concerns on TikTok Shop\n\n### Style Guide for TikTok Shop\n- Maximum 3 sentences per answer\n- Use casual, direct language matching TikTok's tone\n- Lead with the direct answer, then add brief context\n- Avoid corporate-speak or legal language\n\n### Priority FAQ Order for TikTok Shop\n1. Shipping time and carrier\n2. Return / refund policy\n3. Size / fit (if apparel)\n4. Authenticity / brand verification\n5. Bundle contents / what's in the package\n\n---\n\n## WooCommerce\n\n### FAQ Implementation Options\n- **WPForms FAQ Block** — Gutenberg block, schema enabled\n- **Accordion FAQ plugin** — Multiple free options; ensure FAQPage schema output\n- **Custom post type** — For stores with large FAQ libraries needing search\n\n### WooCommerce SEO Notes\n- Install RankMath or Yoast and use their FAQ block — both output FAQPage schema automatically\n- Check Google Search Console after adding schema to confirm rich result eligibility\n- FAQ rich results appear within 1–4 weeks of Google recrawling the page\n\n---\n\n## General Formatting Best Practices\n\n| Principle | Do | Don't |\n|---|---|---|\n| Lead with the answer | \"Yes, it is compatible with iOS 16+\" | \"That's a great question. This product is designed with...\" |\n| Use specific numbers | \"Ships in 3–5 business days\" | \"Ships quickly\" |\n| Name the concern | \"If you're worried about sizing...\" | Ignore the underlying anxiety |\n| Action when needed | \"Contact us at [email] for custom orders\" | Leave the buyer stuck |\n| Consistent tone | Match brand voice across all answers | Mix formal and casual randomly |\n\nFile v1.1.0:quality-checklist.md\n\n# FAQ Builder Quality Checklist\n\n## Source Data Quality\n- [ ] Support ticket data reviewed (minimum 30 tickets or 90 days of data)\n- [ ] Return reason report pulled and top 3 reasons noted\n- [ ] Competitor Q&A sections reviewed for category patterns\n- [ ] Review mining completed (1-star and 2-star reviews scanned for questions)\n- [ ] At least one tier-1 source used (not just assumptions)\n\n## Question Coverage\n- [ ] Compatibility / fit questions addressed\n- [ ] Shipping and delivery addressed\n- [ ] Return and refund policy clearly stated\n- [ ] Product specs and materials answered with specific details\n- [ ] Top 3 support ticket themes have dedicated FAQ entries\n- [ ] Top 2 return reasons have preemptive FAQ entries\n- [ ] 8–15 total questions (not fewer, not overwhelmingly more)\n\n## Answer Quality\n- [ ] Every answer contains a specific, direct response (no vague or non-answers)\n- [ ] Answers include numbers, dimensions, or material names where relevant\n- [ ] No answer is shorter than 2 sentences\n- [ ] Tone matches brand voice\n- [ ] No defensive or corporate-speak language\n- [ ] ACES framework applied: Acknowledge → Clarify → Expand → Seal\n- [ ] Answers don't create new unanswered questions\n\n## Platform Compliance\n- [ ] Answer length matches platform character limits\n- [ ] Format matches platform (accordion, plain text, A+ module)\n- [ ] Keywords included naturally in 30–40% of answers\n- [ ] FAQPage schema markup added (Shopify/WooCommerce)\n- [ ] FAQ placement is above the fold or in a prominent section\n\n## Sequence and Organization\n- [ ] Purchase-blocker questions appear first (compatibility, returns, shipping)\n- [ ] Questions grouped by topic or follow buyer journey order\n- [ ] No company background / brand story questions in product FAQ\n- [ ] Most important information leads each answer\n\n## Maintenance Setup\n- [ ] Support ticket spike alert configured (>30% increase = review trigger)\n- [ ] Quarterly review date set in calendar\n- [ ] Return analysis trigger: new batch → check if FAQ-addressable\n- [ ] Version/update log started for future reference\n\nFile v1.1.0:question-bank.md\n\n# Question Bank by Product Category\n\n## Apparel & Footwear\n- Does it run true to size, small, or large?\n- What are the exact measurements for size [X]?\n- What material is it made from? Is it breathable?\n- How should I wash and care for this item?\n- Will the color fade after washing?\n- Is it stretchy? How much stretch does it have?\n- Is it see-through/sheer?\n- Can it be worn in rain / is it water-resistant?\n- Are the pockets functional?\n\n## Electronics & Tech Accessories\n- Is it compatible with [iPhone/Android/MacBook/Windows]?\n- Does it require batteries or is it rechargeable?\n- What is the battery life?\n- Is it Bluetooth or does it require a cable?\n- What's in the box — does it come with [charging cable/accessories]?\n- Does it work with [Alexa/Google Assistant/Siri]?\n- What's the warranty? What does it cover?\n- Can I use it in multiple countries (voltage compatibility)?\n\n## Kitchen & Home\n- What are the dimensions (length × width × height)?\n- Is it dishwasher safe?\n- Is it BPA-free / food-safe?\n- What materials is it made from?\n- Is it compatible with induction / gas / electric stovetops?\n- Does it come with a lid / accessories?\n- Is it oven-safe? Up to what temperature?\n- Will it scratch non-stick surfaces?\n\n## Beauty & Personal Care\n- Is it suitable for sensitive skin?\n- Is it cruelty-free / vegan?\n- Does it contain fragrance / parabens / sulfates?\n- How long does one unit last with daily use?\n- Is it dermatologist tested?\n- Can it be used on [hair type / skin tone / specific concern]?\n- Is there a return policy if it causes a reaction?\n\n## Supplements & Health\n- Are there any allergens? (gluten, soy, dairy, nuts)\n- Is it third-party tested?\n- What is the recommended dosage?\n- Can it be taken with [medication X]? (answer: consult your doctor)\n- Is it safe for pregnant / breastfeeding women?\n- What's the expiry date / shelf life?\n- What certifications does it have? (GMP, NSF, Informed Sport)\n\n## Pet Products\n- What size / breed is this designed for?\n- Is it safe if my pet chews on it?\n- What materials are used? Are they non-toxic?\n- Is it machine washable?\n- Can it be used for both cats and dogs?\n- Is the size adjustable?\n\n## Baby & Kids\n- What age range is it appropriate for?\n- Is it BPA-free / phthalate-free?\n- Does it meet safety certifications? (CPSC, ASTM, EN71)\n- Is it machine washable?\n- Can small parts be swallowed? (choking hazard)\n- What are the exact dimensions?\n\n## Sports & Fitness Equipment\n- What weight capacity does it support?\n- What is the assembled size vs. storage/folded size?\n- Does it require assembly? How long does it take?\n- What are the warranty terms?\n- Can it be used on carpet / hardwood / outdoors?\n- Is it compatible with [fitness tracker / app]?\n\n## Universal High-Priority Questions (Any Category)\n- What is the return policy?\n- How long does shipping take?\n- Do you ship internationally?\n- Is this the official/authentic product? (important for Amazon)\n- What does the warranty cover and how long is it?\n- How do I contact support if I have an issue?\n\nFile v1.1.0:skill-card.md\n\n## Description:\n\nGenerate comprehensive, conversion-focused FAQ sections for ecommerce product pages by systematically analyzing real customer questions, return data, and purchase objections.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[leooooooow](https://clawhub.ai/user/leooooooow)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal ecommerce operators, marketers, and support teams use this skill to turn product details, customer questions, support tickets, return reasons, reviews, and competitor Q&A into structured product-page FAQ sections.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can involve customer support tickets, return reasons, reviews, and competitor Q&A that may contain personal or sensitive business data.\n\nMitigation: Share only the data needed for the FAQ task and redact unnecessary personal details before use.\n\nRisk: FAQ content based on incomplete or outdated source data can mislead buyers about product fit, shipping, returns, materials, or compatibility.\n\nMitigation: Review generated FAQs against current product, policy, and support data before publishing and update them when support or return patterns change.\n\n## Reference(s):\n\n- [Output Template](references/output-template.md)\n- [Question Bank by Category](references/question-bank.md)\n- [Platform Formatting Guide](references/platform-formatting-guide.md)\n- [Quality Checklist](assets/quality-checklist.md)\n- [FAQPage schema](https://schema.org)\n- [ClawHub skill page](https://clawhub.ai/leooooooow/skills/faq-builder)\n- [Publisher profile](https://clawhub.ai/user/leooooooow)\n\n## Skill Output:\n\n**Output Type(s):** [Markdown, Configuration instructions, Guidance]\n\n**Output Format:** [Markdown FAQ brief with grouped question-and-answer sections, SEO notes, platform formatting guidance, and a maintenance log]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Uses customer and business input such as product descriptions, support ticket themes, return reasons, reviews, and competitor Q&A.]\n\n## Skill Version(s):\n\n1.1.0 (source: server-resolved release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.1: 7 files, 12862 bytes\n\nFiles: output-template.md (904b), platform-formatting-guide.md (4216b), quality-checklist.md (2094b), question-bank.md (3035b), skill-card.md (2248b), SKILL.md (12495b), _meta.json (130b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: FAQ Builder\ndescription: Generate comprehensive, conversion-focused FAQ sections for ecommerce product pages by systematically analyzing real customer questions, return data, and purchase objections.\n---\n\n# FAQ Builder\n\nGenerate comprehensive, conversion-focused FAQ sections for your product pages by systematically analyzing the questions real customers ask, the reasons they return products, and the objections that stall purchases. Instead of guessing what buyers want to know, this skill builds FAQ content grounded in actual customer pain points, structured to resolve hesitation at the moment it arises and reduce the support ticket volume that drains your team's bandwidth.\n\n## Quick Reference\n\n| Decision | Strong | Acceptable | Weak |\n|---|---|---|---|\n| FAQ source data | Support tickets + return reasons + review Q&A + competitor listings | Support tickets only | Writing from memory what you think customers ask |\n| Number of FAQs | 8–15 per product, grouped by topic | 5–7 ungrouped FAQs | 2–3 FAQs or 20+ with no grouping |\n| Answer length | 2–5 sentences with specifics (dimensions, materials, compatibility) | 1 sentence answer without detail | One-word answers or answers that raise new questions |\n| Objection handling | Explicitly names the concern before resolving it | Answers question without acknowledging doubt | Defensive or dismissive tone |\n| Platform formatting | Matches platform specs (Amazon character limits, Shopify accordion, TikTok Shop) | Generic HTML list format | Plain text wall, no formatting |\n| SEO integration | Target keywords woven naturally into answers | Keywords in questions only | No keyword consideration |\n| Update cadence | Reviewed and updated after new support ticket spikes | Reviewed quarterly | Never updated after initial publish |\n\n## Solves\n\n- Product pages that generate high support ticket volume for the same repeated questions\n- Return rates driven by \"not as described\" or \"wrong size/compatibility\" — both addressable with FAQs\n- Conversion drop-off at the product page because buyers can't find answers before checkout\n- Listings that lose to competitors whose pages are more complete and trust-building\n- Support team spending hours answering questions that should be self-serve\n- New product launches with no existing review base to signal trustworthiness\n- Marketplaces penalizing listings with high \"buyer question\" rates (Amazon A9 signals)\n\n## Workflow\n\n### Step 1 — Gather Source Data\n\nThe quality of your FAQ is entirely determined by the quality of your input data. Collect:\n\n**Tier 1 sources (highest signal):**\n- Support ticket exports filtered by product — look for question patterns appearing 3+ times\n- Return reason data — \"not as described,\" \"wrong size,\" \"missing feature\" all translate to FAQ entries\n- Amazon Buyer Questions on your listing and competitor listings in the same category\n- 1-star and 2-star review text — complaints reveal unmet expectations you can preemptively address\n\n**Tier 2 sources (supplemental):**\n- Your own product team's anticipated questions (useful for technical specs)\n- Competitor listing Q&A sections (reveals what buyers in your category commonly wonder)\n- Reddit and forum threads where buyers discuss products in your category\n- Google autocomplete for \"[product type] does it...\" / \"[product type] is it compatible with...\"\n\nMinimum viable input: product description, 3 top support ticket categories, and 5 real customer questions.\n\n### Step 2 — Categorize Questions by Intent\n\nGroup raw questions into intent buckets before writing answers:\n\n| Category | Examples | FAQ priority |\n|---|---|---|\n| Compatibility / fit | \"Does this work with X?\" \"What size should I get?\" | High — prevents returns |\n| Shipping / fulfillment | \"How long does delivery take?\" \"Do you ship to X?\" | High — pre-purchase anxiety |\n| Product specs | \"What material is it made of?\" \"How many units included?\" | Medium — listing gap filler |\n| Usage / instructions | \"How do I set this up?\" \"Can it be used for X?\" | Medium — reduces support tickets |\n| Returns / warranty | \"What's the return policy?\" \"Is there a warranty?\" | High — purchase risk reducer |\n| Authenticity / quality | \"Is this the real brand?\" \"Is the quality good?\" | High — trust signal for new listings |\n| Comparison | \"How is this different from [competitor]?\" | Medium — consideration stage |\n\n### Step 3 — Write Answers Using the ACES Framework\n\nEach FAQ answer should follow: **Acknowledge → Clarify → Expand → Seal**\n\n- **Acknowledge**: Name the concern or question directly\n- **Clarify**: Give the direct, specific answer (number, yes/no, dimension)\n- **Expand**: Add the detail that turns the answer into confidence (\"the [material] ensures...\")\n- **Seal**: End with a trust signal or action if applicable\n\n**Example:**\n- Q: \"Is this water-resistant?\"\n- Weak answer: \"Yes it is.\"\n- ACES answer: \"Yes, the [product] is IPX6-rated water-resistant, meaning it handles heavy rain, splashing, and sweat without damage. It is not designed for submersion — don't use it underwater. This makes it ideal for outdoor workouts, hiking, and daily commutes in wet weather.\"\n\n### Step 4 — Format for Platform\n\n**Amazon:**\n- Use the Seller Central Q&A feature and A+ Content FAQ module\n- Character limit: ~1,000 characters per answer in A+\n- Questions should contain relevant search keywords\n- Lead with the most important information (Amazon may truncate)\n\n**Shopify:**\n- Use accordion-style FAQ apps (Acecart, HelpCenter, or custom sections)\n- No character limit — prioritize readability over compression\n- Include internal links to size guides, shipping pages, return policy\n- Place FAQ section above the fold on product pages for high-anxiety categories\n\n**TikTok Shop:**\n- Shorter answers (2–3 sentences maximum)\n- Mirror the casual, direct tone of TikTok content\n- Prioritize shipping speed and return policy (top buyer concerns on the platform)\n\n**WooCommerce / generic:**\n- Use schema markup (FAQPage schema) for Google rich result eligibility\n- Structured data can generate FAQ accordion directly in SERPs\n\n### Step 5 — Prioritize and Sequence\n\nOrder your FAQs to map the buyer's journey — put purchase blockers first:\n\n1. Compatibility / fit (prevent the \"wrong item\" return)\n2. Shipping and delivery timeline\n3. Return and refund policy\n4. Quality and material details\n5. Usage and setup questions\n6. Comparison and differentiation\n\nNever lead with company background or brand story FAQs — buyers at the product page want answers about the product, not your origin story.\n\n### Step 6 — Optimize for SEO\n\n- Include primary and secondary keywords in 30–40% of answers\n- Use long-tail question formats Google shows in \"People Also Ask\": \"Can you use [product] for [use case]?\"\n- Avoid keyword stuffing — one natural mention per answer is enough\n- For Shopify: create a dedicated /faq page with schema markup to capture SERP FAQ real estate\n\n### Step 7 — Set Up Maintenance Triggers\n\nFAQs decay. Set up:\n- Support ticket spike alerts: if a question type spikes 30%+ in a week, add or update the FAQ\n- Quarterly review: pull fresh support data and compare against published FAQs\n- Post-return analysis: after each return batch, check if reasons are addressable with FAQ updates\n- Review mining: flag new 1- and 2-star reviews monthly for new FAQ candidates\n\n## Examples\n\n### Example 1 — Kitchen Gadget (Shopify + Amazon)\n\n**Product:** Adjustable mandoline slicer, 3 SKUs (different blade sets)  \n**Source data:** 47 support tickets in 90 days; top issues: blade compatibility between SKUs, cleaning instructions, safety concerns with the guard  \n**Return reasons:** \"cut myself using it\" (22%), \"blades don't fit my model\" (18%)\n\n**FAQ output (top 5 by priority):**\n\n**Q: Will the extra blades from the 5-blade set fit my 3-blade model?**  \nA: No — the blade sets are model-specific and not cross-compatible. The 3-blade model uses a narrower frame than the 5-blade model. If you're unsure which model you have, the model number is printed on the underside of the frame. Contact us with your order number and we'll confirm compatibility before you purchase additional blades.\n\n**Q: Is the hand guard required to use the slicer?**  \nA: Yes — we strongly recommend always using the included cut-resistant hand guard. The mandoline blade is razor-sharp and 68% of customer injuries we've seen occurred without the guard in use. The guard fits all slice thicknesses and is dishwasher safe.\n\n**Q: How do I clean the blades safely?**  \nA: Use the included brush (not a sponge or cloth) to clean blades under running water. Always push the brush away from the blade edge, never toward it. Blades are not dishwasher safe — the heat warps the edge over time.\n\n**Result:** Return rate fell from 14% to 8% in 60 days after FAQ publish. Support tickets for the top 3 questions dropped 61%.\n\n---\n\n### Example 2 — Apparel (TikTok Shop, new listing)\n\n**Product:** Oversized fleece hoodie, women's, 5 colors  \n**Source data:** No prior tickets (new listing); competitor listing Q&A mined; top 3 competitor concerns: sizing runs large, material pills quickly, hood too small  \n**Return reasons from category:** \"too big\" (41%), \"color different than pictured\" (27%)\n\n**FAQ output (pre-emptive, no support history):**\n\n**Q: How does the sizing run?**  \nA: This hoodie is intentionally oversized — it runs 1–2 sizes large for a relaxed fit. If you prefer a closer fit, size down. Example: our size M fits a typical S–M body (bust 34–38\"). Check the size chart in photos for exact measurements. Still unsure? DM us with your bust/waist measurements and we'll recommend a size.\n\n**Q: Will the fleece pill after washing?**  \nA: We've had zero pilling reports in 200+ orders since launch. The fleece is 320 GSM brushed polyester — denser than the typical 280 GSM hoodies in this price range. Wash inside-out on cold, and it'll hold up for years.\n\n**Q: Does the color match the photos?**  \nA: We photograph under natural light with no filter adjustments. Screens vary slightly, but the colors are true-to-life. All five colorways are shown in the video with natural light + indoor light comparison.\n\n## Common Mistakes\n\n1. **Writing FAQs based on what you think buyers ask** — without checking support tickets, return data, or review mining, you're guessing. Guesses produce FAQs that answer the wrong questions.\n\n2. **One-word or one-line answers** — \"Yes\" and \"No\" answers create new questions instead of resolving them. Every answer needs enough detail to be actionable.\n\n3. **Vague specs** — \"It's pretty big\" or \"durable material\" tells buyers nothing. Replace with: dimensions in inches/cm, material composition percentages, weight in grams.\n\n4. **Burying the FAQ** — An FAQ section below the fold on a product page doesn't get read. High-anxiety categories (electronics, apparel, supplements) need FAQs visible without scrolling.\n\n5. **Ignoring return-driven questions** — Your return reason report is a direct FAQ brief. Every top return reason is an FAQ entry waiting to be written.\n\n6. **Defensive tone** — \"We don't offer refunds because...\" sounds adversarial. Rewrite as policy + benefit: \"We offer 30-day returns because we're confident you'll love it — and if not, the process takes less than 5 minutes.\"\n\n7. **Not formatting for the platform** — A 500-character answer that gets truncated to 150 on Amazon is worse than no answer.\n\n8. **Writing for you, not the buyer** — FAQs about your company history, founder story, or certifications nobody can verify belong on your About page, not the product FAQ.\n\n9. **No maintenance schedule** — FAQs that are accurate at launch become misleading after a policy change, reformulation, or new SKU launch. Set a calendar reminder to review every 90 days.\n\n10. **Skipping schema markup** — For Shopify and WooCommerce stores, FAQPage schema is free and can generate FAQ accordions in Google SERPs, effectively expanding your listing real estate.\n\n## Resources\n\n- [Output Template](references/output-template.md) — FAQ section brief and output format\n- [Question Bank by Category](references/question-bank.md) — Pre-researched common questions by product type\n- [Platform Formatting Guide](references/platform-formatting-guide.md) — Character limits and formatting specs by marketplace\n- [Quality Checklist](assets/quality-checklist.md) — Pre-publish FAQ review checklist\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn70fv0ehp50emedet9tx3fekd82pw3b\",\n  \"slug\": \"faq-builder\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1780670271519\n}\n\nFile v1.0.1:output-template.md\n\n# FAQ Section Output Template\n\n## Product Brief\n- **Product name:** \n- **Platform(s):** Amazon / Shopify / TikTok Shop / WooCommerce / Other\n- **SKU count:** \n- **Category:** \n\n## Source Data Summary\n- **Support ticket themes (top 3):**\n  1. \n  2. \n  3. \n- **Top return reasons:**\n  1. \n  2. \n- **Competitor Q&A patterns noted:**\n\n## FAQ Section: [Product Name]\n\n### Compatibility & Fit\n**Q:**  \n**A:** \n\n**Q:**  \n**A:** \n\n### Shipping & Delivery\n**Q:**  \n**A:** \n\n**Q:**  \n**A:** \n\n### Product Specs & Materials\n**Q:**  \n**A:** \n\n**Q:**  \n**A:** \n\n### Usage & Instructions\n**Q:**  \n**A:** \n\n### Returns & Warranty\n**Q:**  \n**A:** \n\n**Q:**  \n**A:** \n\n### Other Questions\n**Q:**  \n**A:** \n\n## SEO Notes\n- Primary keyword used in: Q___, Q___\n- Secondary keywords used in: Q___, Q___\n- Schema markup added: Yes / No / Pending\n\n## Maintenance Log\n| Date | Trigger | Questions updated |\n|---|---|---|\n| | | |\n\nFile v1.0.1:platform-formatting-guide.md\n\n# Platform Formatting Guide for FAQ Sections\n\n## Amazon\n\n### A+ Content FAQ Module\n- Maximum answers per FAQ module: 6–8 (recommended)\n- Character limit per answer: ~1,000 characters\n- Questions should include high-search keywords naturally\n- Images can accompany answers in premium A+ Content\n- FAQs display in an accordion format — question first, answer on expand\n\n### Amazon Customer Q&A (Separate from A+ Content)\n- Sellers can answer any customer question in the Q&A section\n- Responses show as \"Seller\" answer — respond to all questions within 24 hours\n- High-volume Q&As surface to top of listing (Amazon ranks by helpfulness votes)\n- Best practice: answer competitor questions in your category to build authority\n\n### Keyword Strategy for Amazon FAQ\n- Include your primary ASIN keyword in 2–3 answers\n- Include backend search terms that don't fit naturally in bullet points\n- Avoid keyword stuffing — Amazon's algorithm reads FAQs for relevance signals\n\n---\n\n## Shopify\n\n### FAQ Placement Options\n1. **Product page FAQ section** — highest-converting placement for pre-purchase questions\n2. **Dedicated /faq page** — for brand-level questions (returns, shipping, company info)\n3. **Modal / popup** — triggered on exit intent or add-to-cart click (advanced)\n\n### Recommended Apps\n- **HelpCenter** — Native Shopify FAQ with accordion UI, no coding required\n- **Acecart FAQ** — Lightweight, fast-loading\n- **Yotpo** — Integrates FAQ with reviews for social proof combination\n- **Custom Liquid section** — Full control; use `<details>` HTML for native accordion\n\n### Schema Markup for Shopify (FAQPage)\nAdd to your product page or FAQ page template:\n\n```json\n{\n  \"@context\": \"https://schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Does this product come with a warranty?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Yes, all products include a 1-year manufacturer warranty covering defects in materials and workmanship.\"\n      }\n    }\n  ]\n}\n```\n\nSchema markup enables Google to show FAQ accordion directly in search results (rich results), expanding your SERP presence without additional ranking effort.\n\n### Character Guidance\n- No hard limit, but answers longer than 200 words lose readability\n- Aim for 50–150 words per answer on product pages\n- Break long answers into bullet points rather than paragraphs\n\n---\n\n## TikTok Shop\n\n### FAQ Behavior on TikTok Shop\n- Product page FAQs appear in the \"Details\" tab below the listing\n- Buyers on TikTok skim — prioritize short, direct answers\n- Return policy and shipping time are the top 2 buyer concerns on TikTok Shop\n\n### Style Guide for TikTok Shop\n- Maximum 3 sentences per answer\n- Use casual, direct language matching TikTok's tone\n- Lead with the direct answer, then add brief context\n- Avoid corporate-speak or legal language\n\n### Priority FAQ Order for TikTok Shop\n1. Shipping time and carrier\n2. Return / refund policy\n3. Size / fit (if apparel)\n4. Authenticity / brand verification\n5. Bundle contents / what's in the package\n\n---\n\n## WooCommerce\n\n### FAQ Implementation Options\n- **WPForms FAQ Block** — Gutenberg block, schema enabled\n- **Accordion FAQ plugin** — Multiple free options; ensure FAQPage schema output\n- **Custom post type** — For stores with large FAQ libraries needing search\n\n### WooCommerce SEO Notes\n- Install RankMath or Yoast and use their FAQ block — both output FAQPage schema automatically\n- Check Google Search Console after adding schema to confirm rich result eligibility\n- FAQ rich results appear within 1–4 weeks of Google recrawling the page\n\n---\n\n## General Formatting Best Practices\n\n| Principle | Do | Don't |\n|---|---|---|\n| Lead with the answer | \"Yes, it is compatible with iOS 16+\" | \"That's a great question. This product is designed with...\" |\n| Use specific numbers | \"Ships in 3–5 business days\" | \"Ships quickly\" |\n| Name the concern | \"If you're worried about sizing...\" | Ignore the underlying anxiety |\n| Action when needed | \"Contact us at [email] for custom orders\" | Leave the buyer stuck |\n| Consistent tone | Match brand voice across all answers | Mix formal and casual randomly |\n\nFile v1.0.1:quality-checklist.md\n\n# FAQ Builder Quality Checklist\n\n## Source Data Quality\n- [ ] Support ticket data reviewed (minimum 30 tickets or 90 days of data)\n- [ ] Return reason report pulled and top 3 reasons noted\n- [ ] Competitor Q&A sections reviewed for category patterns\n- [ ] Review mining completed (1-star and 2-star reviews scanned for questions)\n- [ ] At least one tier-1 source used (not just assumptions)\n\n## Question Coverage\n- [ ] Compatibility / fit questions addressed\n- [ ] Shipping and delivery addressed\n- [ ] Return and refund policy clearly stated\n- [ ] Product specs and materials answered with specific details\n- [ ] Top 3 support ticket themes have dedicated FAQ entries\n- [ ] Top 2 return reasons have preemptive FAQ entries\n- [ ] 8–15 total questions (not fewer, not overwhelmingly more)\n\n## Answer Quality\n- [ ] Every answer contains a specific, direct response (no vague or non-answers)\n- [ ] Answers include numbers, dimensions, or material names where relevant\n- [ ] No answer is shorter than 2 sentences\n- [ ] Tone matches brand voice\n- [ ] No defensive or corporate-speak language\n- [ ] ACES framework applied: Acknowledge → Clarify → Expand → Seal\n- [ ] Answers don't create new unanswered questions\n\n## Platform Compliance\n- [ ] Answer length matches platform character limits\n- [ ] Format matches platform (accordion, plain text, A+ module)\n- [ ] Keywords included naturally in 30–40% of answers\n- [ ] FAQPage schema markup added (Shopify/WooCommerce)\n- [ ] FAQ placement is above the fold or in a prominent section\n\n## Sequence and Organization\n- [ ] Purchase-blocker questions appear first (compatibility, returns, shipping)\n- [ ] Questions grouped by topic or follow buyer journey order\n- [ ] No company background / brand story questions in product FAQ\n- [ ] Most important information leads each answer\n\n## Maintenance Setup\n- [ ] Support ticket spike alert configured (>30% increase = review trigger)\n- [ ] Quarterly review date set in calendar\n- [ ] Return analysis trigger: new batch → check if FAQ-addressable\n- [ ] Version/update log started for future reference\n\nFile v1.0.1:question-bank.md\n\n# Question Bank by Product Category\n\n## Apparel & Footwear\n- Does it run true to size, small, or large?\n- What are the exact measurements for size [X]?\n- What material is it made from? Is it breathable?\n- How should I wash and care for this item?\n- Will the color fade after washing?\n- Is it stretchy? How much stretch does it have?\n- Is it see-through/sheer?\n- Can it be worn in rain / is it water-resistant?\n- Are the pockets functional?\n\n## Electronics & Tech Accessories\n- Is it compatible with [iPhone/Android/MacBook/Windows]?\n- Does it require batteries or is it rechargeable?\n- What is the battery life?\n- Is it Bluetooth or does it require a cable?\n- What's in the box — does it come with [charging cable/accessories]?\n- Does it work with [Alexa/Google Assistant/Siri]?\n- What's the warranty? What does it cover?\n- Can I use it in multiple countries (voltage compatibility)?\n\n## Kitchen & Home\n- What are the dimensions (length × width × height)?\n- Is it dishwasher safe?\n- Is it BPA-free / food-safe?\n- What materials is it made from?\n- Is it compatible with induction / gas / electric stovetops?\n- Does it come with a lid / accessories?\n- Is it oven-safe? Up to what temperature?\n- Will it scratch non-stick surfaces?\n\n## Beauty & Personal Care\n- Is it suitable for sensitive skin?\n- Is it cruelty-free / vegan?\n- Does it contain fragrance / parabens / sulfates?\n- How long does one unit last with daily use?\n- Is it dermatologist tested?\n- Can it be used on [hair type / skin tone / specific concern]?\n- Is there a return policy if it causes a reaction?\n\n## Supplements & Health\n- Are there any allergens? (gluten, soy, dairy, nuts)\n- Is it third-party tested?\n- What is the recommended dosage?\n- Can it be taken with [medication X]? (answer: consult your doctor)\n- Is it safe for pregnant / breastfeeding women?\n- What's the expiry date / shelf life?\n- What certifications does it have? (GMP, NSF, Informed Sport)\n\n## Pet Products\n- What size / breed is this designed for?\n- Is it safe if my pet chews on it?\n- What materials are used? Are they non-toxic?\n- Is it machine washable?\n- Can it be used for both cats and dogs?\n- Is the size adjustable?\n\n## Baby & Kids\n- What age range is it appropriate for?\n- Is it BPA-free / phthalate-free?\n- Does it meet safety certifications? (CPSC, ASTM, EN71)\n- Is it machine washable?\n- Can small parts be swallowed? (choking hazard)\n- What are the exact dimensions?\n\n## Sports & Fitness Equipment\n- What weight capacity does it support?\n- What is the assembled size vs. storage/folded size?\n- Does it require assembly? How long does it take?\n- What are the warranty terms?\n- Can it be used on carpet / hardwood / outdoors?\n- Is it compatible with [fitness tracker / app]?\n\n## Universal High-Priority Questions (Any Category)\n- What is the return policy?\n- How long does shipping take?\n- Do you ship internationally?\n- Is this the official/authentic product? (important for Amazon)\n- What does the warranty cover and how long is it?\n- How do I contact support if I have an issue?\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nGenerate comprehensive, conversion-focused FAQ sections for ecommerce product pages by systematically analyzing real customer questions, return data, and purchase objections. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[leooooooow](https://clawhub.ai/user/leooooooow) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEcommerce operators, marketers, and support teams use this skill to draft product-page FAQ sections from customer questions, return reasons, reviews, and competitor Q&A patterns. The skill helps organize purchase objections into clear markdown FAQ content for platforms such as Amazon, Shopify, TikTok Shop, and WooCommerce. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: FAQ source material can include customer names, emails, order numbers, addresses, or other personal details. <br>\nMitigation: Provide only the support-ticket or return-data excerpts needed for the FAQ and remove unnecessary personal details before using the skill. <br>\n\n\n## Reference(s): <br>\n- [FAQ Builder on ClawHub](https://clawhub.ai/leooooooow/faq-builder) <br>\n- [Output Template](artifact/output-template.md) <br>\n- [Question Bank by Product Category](artifact/question-bank.md) <br>\n- [Platform Formatting Guide](artifact/platform-formatting-guide.md) <br>\n- [FAQ Builder Quality Checklist](artifact/quality-checklist.md) <br>\n- [Schema.org FAQPage](https://schema.org) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown FAQ sections, briefs, checklists, and platform-specific writing guidance] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May include ecommerce FAQ questions, answers, source-data summaries, SEO notes, schema-markup guidance, and maintenance logs.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.0: 3 files, 3827 bytes\n\nFiles: skill-card.md (2172b), SKILL.md (5293b), _meta.json (130b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: faq-builder\ndescription: Generate comprehensive product FAQ sections by analyzing common customer questions, return reasons, and support tickets to preemptively answer objections and reduce pre-purchase hesitation on product pages.\n---\n\n# FAQ Builder\n\nGenerate comprehensive, conversion-focused FAQ sections for your product pages by systematically analyzing the questions real customers ask, the reasons they return products, and the objections that stall purchases. Instead of guessing what buyers want to know, this skill builds FAQ content grounded in actual customer pain points, structured to resolve hesitation at the moment it arises and reduce the support ticket volume that drains your team's bandwidth.\n\n## Use when\n\n- You are launching a new product on Shopify, Amazon, or TikTok Shop and need a thorough FAQ section before the first customer lands on the page\n- Your support inbox is flooded with the same questions — \"is this compatible with X?\", \"what's the return policy?\", \"how long does shipping take?\" — and you want to deflect those tickets with preemptive answers on the product page\n- You have return and refund data showing common reasons like \"not as described\" or \"wrong size\" and want FAQ entries that address those exact issues before purchase\n- A product manager or listing specialist says \"write me 10-15 FAQs for this product\" and you need content that is specific, helpful, and strategically ordered to overcome buying objections rather than generic placeholder questions\n\n## What this skill does\n\nThis skill takes your product details, known customer questions, return reason data, and support ticket themes, then generates a prioritized FAQ section designed to reduce pre-purchase hesitation and post-purchase support load. It categorizes questions into logical groups — product specifications, compatibility and sizing, shipping and delivery, returns and warranty, usage instructions, and safety or compliance — then writes clear, concise answers that address the underlying concern rather than just the surface question. For example, if customers frequently ask \"is this true to size?\", the FAQ answer does not just say \"yes\" — it provides specific measurement guidance, comparison to popular brands, and links to a size chart. The skill also identifies gaps where common objections are not yet covered and suggests additional FAQ entries to fill those blind spots. Questions are ordered strategically so the highest-impact objection-busters appear first.\n\n## Inputs required\n\n- **Product name and description** (required): What you are selling with enough detail to write accurate answers — e.g., \"Wireless Bluetooth earbuds, ANC, 30hr battery, IPX5 waterproof, USB-C charging\"\n- **Known customer questions** (required): List of real questions from support tickets, reviews, chat logs, or Q&A sections — paste them in raw, the skill will clean and categorize them\n- **Return reason data** (optional): Top reasons customers return this product or similar products — e.g., \"25% say not comfortable for long wear, 15% say pairing issues with Android\" — so the FAQ can preemptively address these\n- **Target platform** (optional): Where the FAQ will be published (Amazon A+ Content, Shopify product page, TikTok Shop listing) so formatting and length suit platform constraints\n- **Brand voice** (optional): Tone description so FAQ answers match your brand — e.g., \"technical and precise\" or \"friendly and approachable\"\n\n## Output format\n\nThe output is a structured FAQ document organized into five to seven thematic sections. Each section has a clear heading such as Product Specifications, Sizing and Fit, Shipping and Delivery, Returns and Warranty, Usage and Care, and Compatibility. Under each heading, individual FAQ entries follow a consistent Q&A format with the question bolded and the answer written in two to four sentences that directly address the concern with specific, verifiable details rather than vague reassurances. After the FAQ entries, the output includes an Objection Gap Analysis — a short list of two to four additional questions the skill recommends adding based on patterns it detected in the inputs, such as frequently returned categories or unanswered concerns implied by the product type. Finally, a Platform Notes section provides formatting recommendations if a target platform was specified, including character limit guidance for Amazon Q&A versus Shopify accordion blocks and tips on keyword placement within answers for SEO benefit.\n\n## Scope\n\n- Designed for: ecommerce operators, listing specialists, product managers, customer support leads\n- Platform context: Amazon, Shopify, TikTok Shop, Shopee, WooCommerce, platform-agnostic\n- Language: English\n\n## Limitations\n\n- Does not pull live customer questions or reviews from any platform — you provide the input data and the skill structures and expands it into FAQ format\n- Answers are based on the product information you supply; if critical specs are missing from your input, the FAQ may contain gaps or require manual editing\n- Not a substitute for legal or regulatory compliance statements — if your product requires specific safety disclosures or certifications, those should be reviewed by a compliance professional before publishing\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn70fv0ehp50emedet9tx3fekd82pw3b\",\n  \"slug\": \"faq-builder\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1776648631740\n}\n\nFile v1.0.0:skill-card.md\n\n## Description: <br>\nGenerate comprehensive product FAQ sections by analyzing common customer questions, return reasons, and support tickets to preemptively answer objections and reduce pre-purchase hesitation on product pages. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[leooooooow](https://clawhub.ai/user/leooooooow) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEcommerce operators, listing specialists, product managers, and support leads use this skill to turn product details, customer questions, return reasons, and support themes into publish-ready FAQ sections that reduce purchase hesitation and repetitive support tickets. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Customer support tickets, reviews, or chat logs can contain personal data. <br>\nMitigation: Redact customer personal data before providing inputs to the skill. <br>\nRisk: FAQ answers can include inaccurate product specifications, warranty terms, shipping promises, safety statements, or compliance language when source data is incomplete or unverified. <br>\nMitigation: Manually verify product specifications, warranty terms, shipping claims, safety statements, and compliance language before publishing. <br>\n\n\n## Reference(s): <br>\n- [FAQ Builder on ClawHub](https://clawhub.ai/leooooooow/faq-builder) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Markdown, Guidance] <br>\n**Output Format:** [Structured Markdown FAQ with Q&A sections, objection gap analysis, and platform notes] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Uses user-provided product details, customer questions, return reasons, and support-ticket themes; product claims should be verified before publishing.] <br>\n\n## Skill Version(s): <br>\n1.0.0 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: FAQ Builder Owner: leooooooow Summary: Generate comprehensive, conversion-focused FAQ sections for ecommerce product pages by systematically analyzing real customer questions, return data, and pur... Tags: latest:1.1.0 Version history: v1.1.0 | 2026-06-05T14:40:44.220Z | user Version 1.0.2 of faq-builder - No file changes detected in this release. - Content, functionality, and documentation remain unchanged fr","codeSnippets":[],"executableExamples":[{"language":"json","snippet":"{\n  \"@context\": \"https://schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Does this product come with a warranty?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Yes, all products include a 1-year manufacturer warranty covering defects in materials and workmanship.\"\n      }\n    }\n  ]\n}"},{"language":"json","snippet":"{\n  \"@context\": \"https://schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Does this product come with a warranty?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Yes, all products include a 1-year manufacturer warranty covering defects in materials and workmanship.\"\n      }\n    }\n  ]\n}"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: FAQ Builder\ndescription: Generate comprehensive, conversion-focused FAQ sections for ecommerce product pages by systematically analyzing real customer questions, return data, and purchase objections.\n---\n\n# FAQ Builder\n\nGenerate comprehensive, conversion-focused FAQ sections for your product pages by systematically analyzing the questions real customers ask, the reasons they return products, and the objections that stall purchases. Instead of guessing what buyers want to know, this skill builds FAQ content grounded in actual customer pain points, structured to resolve hesitation at the moment it arises and reduce the support ticket volume that drains your team's bandwidth.\n\n## Quick Reference\n\n| Decision | Strong | Acceptable | Weak |\n|---|---|---|---|\n| FAQ source data | Support tickets + return reasons + review Q&A + competitor listings | Support tickets only | Writing from memory what you think customers ask |\n| Number of FAQs | 8–15 per product, grouped by topic | 5–7 ungrouped FAQs | 2–3 FAQs or 20+ with no grouping |\n| Answer length | 2–5 sentences with specifics (dimensions, materials, compatibility) | 1 sentence answer without detail | One-word answers or answers that raise new questions |\n| Objection handling | Explicitly names the concern before resolving it | Answers question without acknowledging doubt | Defensive or dismissive tone |\n| Platform formatting | Matches platform specs (Amazon character limits, Shopify accordion, TikTok Shop) | Generic HTML list format | Plain text wall, no formatting |\n| SEO integration | Target keywords woven naturally into answers | Keywords in questions only | No keyword consideration |\n| Update cadence | Reviewed and updated after new support ticket spikes | Reviewed quarterly | Never updated after initial publish |\n\n## Solves\n\n- Product pages that generate high support ticket volume for the same repeated questions\n- Return rates driven by \"not as described\" or \"wrong size/compatibility\" — both addressable with FAQs\n- Conversion drop-off at the product page because buyers can't find answers before checkout\n- Listings that lose to competitors whose pages are more complete and trust-building\n- Support team spending hours answering questions that should be self-serve\n- New product launches with no existing review base to signal trustworthiness\n- Marketplaces penalizing listings with high \"buyer question\" rates (Amazon A9 signals)\n\n## Workflow\n\n### Step 1 — Gather Source Data\n\nThe quality of your FAQ is entirely determined by the quality of your input data. Collect:\n\n**Tier 1 sources (highest signal):**\n- Support ticket exports filtered by product — look for question patterns appearing 3+ times\n- Return reason data — \"not as described,\" \"wrong size,\" \"missing feature\" all translate to FAQ entries\n- Amazon Buyer Questions on your listing and competitor listings in the same category\n- 1-star and 2-star review text — complaints reveal unmet expectations you can preemptively address\n\n**Tier 2 source"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn70fv0ehp50emedet9tx3fekd82pw3b\",\n  \"slug\": \"faq-builder\",\n  \"version\": \"1.1.0\",\n  \"publishedAt\": 1780670444220\n}"},{"path":"output-template.md","content":"# FAQ Section Output Template\n\n## Product Brief\n- **Product name:** \n- **Platform(s):** Amazon / Shopify / TikTok Shop / WooCommerce / Other\n- **SKU count:** \n- **Category:** \n\n## Source Data Summary\n- **Support ticket themes (top 3):**\n  1. \n  2. \n  3. \n- **Top return reasons:**\n  1. \n  2. \n- **Competitor Q&A patterns noted:**\n\n## FAQ Section: [Product Name]\n\n### Compatibility & Fit\n**Q:**  \n**A:** \n\n**Q:**  \n**A:** \n\n### Shipping & Delivery\n**Q:**  \n**A:** \n\n**Q:**  \n**A:** \n\n### Product Specs & Materials\n**Q:**  \n**A:** \n\n**Q:**  \n**A:** \n\n### Usage & Instructions\n**Q:**  \n**A:** \n\n### Returns & Warranty\n**Q:**  \n**A:** \n\n**Q:**  \n**A:** \n\n### Other Questions\n**Q:**  \n**A:** \n\n## SEO Notes\n- Primary keyword used in: Q___, Q___\n- Secondary keywords used in: Q___, Q___\n- Schema markup added: Yes / No / Pending\n\n## Maintenance Log\n| Date | Trigger | Questions updated |\n|---|---|---|\n| | | |"},{"path":"platform-formatting-guide.md","content":"# Platform Formatting Guide for FAQ Sections\n\n## Amazon\n\n### A+ Content FAQ Module\n- Maximum answers per FAQ module: 6–8 (recommended)\n- Character limit per answer: ~1,000 characters\n- Questions should include high-search keywords naturally\n- Images can accompany answers in premium A+ Content\n- FAQs display in an accordion format — question first, answer on expand\n\n### Amazon Customer Q&A (Separate from A+ Content)\n- Sellers can answer any customer question in the Q&A section\n- Responses show as \"Seller\" answer — respond to all questions within 24 hours\n- High-volume Q&As surface to top of listing (Amazon ranks by helpfulness votes)\n- Best practice: answer competitor questions in your category to build authority\n\n### Keyword Strategy for Amazon FAQ\n- Include your primary ASIN keyword in 2–3 answers\n- Include backend search terms that don't fit naturally in bullet points\n- Avoid keyword stuffing — Amazon's algorithm reads FAQs for relevance signals\n\n---\n\n## Shopify\n\n### FAQ Placement Options\n1. **Product page FAQ section** — highest-converting placement for pre-purchase questions\n2. **Dedicated /faq page** — for brand-level questions (returns, shipping, company info)\n3. **Modal / popup** — triggered on exit intent or add-to-cart click (advanced)\n\n### Recommended Apps\n- **HelpCenter** — Native Shopify FAQ with accordion UI, no coding required\n- **Acecart FAQ** — Lightweight, fast-loading\n- **Yotpo** — Integrates FAQ with reviews for social proof combination\n- **Custom Liquid section** — Full control; use `<details>` HTML for native accordion\n\n### Schema Markup for Shopify (FAQPage)\nAdd to your product page or FAQ page template:\n\n```json\n{\n  \"@context\": \"https://schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Does this product come with a warranty?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Yes, all products include a 1-year manufacturer warranty covering defects in materials and workmanship.\"\n      }\n    }\n  ]\n}\n```\n\nSchema markup enables Google to show FAQ accordion directly in search results (rich results), expanding your SERP presence without additional ranking effort.\n\n### Character Guidance\n- No hard limit, but answers longer than 200 words lose readability\n- Aim for 50–150 words per answer on product pages\n- Break long answers into bullet points rather than paragraphs\n\n---\n\n## TikTok Shop\n\n### FAQ Behavior on TikTok Shop\n- Product page FAQs appear in the \"Details\" tab below the listing\n- Buyers on TikTok skim — prioritize short, direct answers\n- Return policy and shipping time are the top 2 buyer concerns on TikTok Shop\n\n### Style Guide for TikTok Shop\n- Maximum 3 sentences per answer\n- Use casual, direct language matching TikTok's tone\n- Lead with the direct answer, then add brief context\n- Avoid corporate-speak or legal language\n\n### Priority FAQ Order for TikTok Shop\n1. Shipping time and carrier\n2. Return / refund policy\n3. Size / fit (if apparel)\n4. Authenti"},{"path":"quality-checklist.md","content":"# FAQ Builder Quality Checklist\n\n## Source Data Quality\n- [ ] Support ticket data reviewed (minimum 30 tickets or 90 days of data)\n- [ ] Return reason report pulled and top 3 reasons noted\n- [ ] Competitor Q&A sections reviewed for category patterns\n- [ ] Review mining completed (1-star and 2-star reviews scanned for questions)\n- [ ] At least one tier-1 source used (not just assumptions)\n\n## Question Coverage\n- [ ] Compatibility / fit questions addressed\n- [ ] Shipping and delivery addressed\n- [ ] Return and refund policy clearly stated\n- [ ] Product specs and materials answered with specific details\n- [ ] Top 3 support ticket themes have dedicated FAQ entries\n- [ ] Top 2 return reasons have preemptive FAQ entries\n- [ ] 8–15 total questions (not fewer, not overwhelmingly more)\n\n## Answer Quality\n- [ ] Every answer contains a specific, direct response (no vague or non-answers)\n- [ ] Answers include numbers, dimensions, or material names where relevant\n- [ ] No answer is shorter than 2 sentences\n- [ ] Tone matches brand voice\n- [ ] No defensive or corporate-speak language\n- [ ] ACES framework applied: Acknowledge → Clarify → Expand → Seal\n- [ ] Answers don't create new unanswered questions\n\n## Platform Compliance\n- [ ] Answer length matches platform character limits\n- [ ] Format matches platform (accordion, plain text, A+ module)\n- [ ] Keywords included naturally in 30–40% of answers\n- [ ] FAQPage schema markup added (Shopify/WooCommerce)\n- [ ] FAQ placement is above the fold or in a prominent section\n\n## Sequence and Organization\n- [ ] Purchase-blocker questions appear first (compatibility, returns, shipping)\n- [ ] Questions grouped by topic or follow buyer journey order\n- [ ] No company background / brand story questions in product FAQ\n- [ ] Most important information leads each answer\n\n## Maintenance Setup\n- [ ] Support ticket spike alert configured (>30% increase = review trigger)\n- [ ] Quarterly review date set in calendar\n- [ ] Return analysis trigger: new batch → check if FAQ-addressable\n- [ ] Version/update log started for future reference"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Generate comprehensive, conversion-focused FAQ sections for ecommerce product pages by systematically analyzing real customer questions, return data, and pur... Skill: FAQ Builder Owner: leooooooow Summary: Generate comprehensive, conversion-focused FAQ sections for ecommerce product pages by systematically analyzing real customer questions, return data, and pur... Tags: latest:1.1.0 Version history: v1.1.0 | 2026-06-05T14:40:44.220Z | user Version 1.0.2 of faq-builder - No file changes detected in this release. - Content, functionality, and documentation remain unchanged fr","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1579,"uniquenessScore":50,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T21:12:07.849Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T21:12:07.849Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-12T19:57:22.194Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}