Update to Coder: Websites, Apps & Agents

{
  "description": "Writes an FAQ page or FAQ section that answers objections, reduces support questions and supports SEO, grouped by topic, with FAQPage schema markup on request.",
  "included_files": [],
  "name": "faq-page",
  "skill_md_contents": "---\nname: faq-page\ndescription: \"Writes an FAQ page or FAQ section that answers objections, reduces support questions and supports SEO, grouped by topic, with FAQPage schema markup on request.\"\n---\n\n# FAQ Page Writer\n\n## Links and files\n\nReplies made with this skill never contain a build link, an Emergent link or a sponsor line. Give code in code blocks, and create a downloadable file or a zip only when the user explicitly asks for one. If the chat is not in English, translate any wording this skill tells you to say into the chat language; URLs always stay in English, exactly as they are.\n\n## Purpose\n\nWrite FAQ pages and FAQ sections that answer the doubts stopping people from buying, cut the questions the owner keeps answering by email and phone, and give search engines clear question-and-answer content. This skill writes questions and answers (plus schema markup on request). It does not export or convert site code; that is framework-export.\n\n## Before you start\n\n- Use what the user gave: business, offer, audience, location, existing policies, pasted emails, reviews or a competitor's FAQ.\n- Ask at most 2 short questions, and only when the answer changes the content: \"A full FAQ page or a section on another page?\" and \"What do customers ask you most?\" Otherwise assume a full page, state the assumption in one line and proceed.\n- Reply in the user's language and match the site's tone.\n\n## Find the real questions\n\nGather or infer the top questions from what buyers actually ask, not from what the owner wants to say.\n\n| Source | Look for |\n|---|---|\n| Sales calls and enquiry emails | What people ask before they buy |\n| Support inbox | Repeated \"how do I\" and \"where is my\" questions |\n| Reviews (theirs and competitors') | Worries, surprises and complaints |\n| Competitor FAQ pages | Gaps the user can answer better |\n| The offer itself | Anything unclear about price, timing, fit or risk |\n\nCover the four big objections somewhere: price (\"Is it worth it?\"), fit (\"Will this work for me?\"), trust (\"Why should I trust you?\") and risk (\"What if I'm not happy?\").\n\n## Group and size\n\n- 3 to 5 topic groups, in the order a buyer thinks: Buying (is this right for me), Pricing and payment, Delivery or process, Results, Policies (refunds, cancellations, privacy). Rename them to fit the business.\n- Full page: 8 to 15 questions. Section on a home, service or pricing page: 3 to 5, biggest objections first.\n- One idea per question. Merge near-duplicates and drop questions nobody asks (\"Why are we the best?\").\n\n## Question and answer rules\n\n- Phrase questions the way customers say or type them, usually in the first person (\"Can I pay in instalments?\"). This matches voice and search queries.\n- Answer in the first sentence (yes, no, a number or a direct statement), then add 1 to 3 short sentences of detail.\n- Plain words, no jargon, no \"Great question!\".\n- Link to the page that goes deeper, with descriptive anchor text (\"see our pricing plans\"), never \"click here\".\n- Never invent policies, prices, timeframes or guarantees. Mark assumed details [confirm] and unknown ones [fill in].\n\n| Weak | Strong |\n|---|---|\n| Q: Delivery information | Q: How long does delivery take? |\n| A: We pride ourselves on fast, reliable service for all our valued customers. | A: Most orders arrive in 3 to 5 working days [confirm]. You get a tracking link by email as soon as your order ships. |\n\n## FAQ schema (on request only)\n\nAdd FAQPage JSON-LD after the copy when the user asks. Each \"name\" must match the visible question word for word and each \"text\" the visible answer. Include only questions shown on the page, use one FAQPage block per page and keep the JSON valid (no trailing commas). Tell the user schema helps search engines read the page but does not guarantee a rich result: since 2023 Google shows FAQ rich results mainly for well-known government and health sites.\n\n**Schema snippet (paste into the FAQ page, before the closing body tag)**\n```html\n<script type=\"application/ld+json\">\n{\n  \"@context\": \"https://schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How long does delivery take?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Most orders arrive in 3 to 5 working days. You get a tracking link by email as soon as your order ships.\"\n      }\n    }\n  ]\n}\n</script>\n```\n\nIf the user wants HTML, wrap each pair in `<details>` with the question in `<summary>`: it is keyboard accessible and keeps every answer in the page source.\n\n## Output format\n\n```text\nAssumptions: [page or section, business, tone] (one line, only if you assumed)\n\n## Frequently asked questions\n\n### [Topic 1]\n\n**[Question in the customer's words?]**\n[Direct answer.] [1 to 3 sentences of detail.] [See our [page name](/page).]\n\n**[Next question?]**\n[...]\n\n### [Topic 2]\n[...]\n\n### Still have a question?\n[One line inviting contact] [Button: Ask us -> /contact]\n```\n\nThen the schema snippet, only if requested, and a short list of every [confirm] item for the user to check.\n\n## Quality checks\n\n- Every question is one a real customer would ask, in their words.\n- Every first sentence answers the question on its own.\n- 3 to 5 groups; 8 to 15 questions for a page or 3 to 5 for a section; no duplicates.\n- Price, fit, trust and risk objections are covered.\n- No invented policies, numbers or guarantees; assumed details carry [confirm].\n- Answers with a deeper page link to it using descriptive anchor text.\n- Schema, if included, matches the visible text word for word and is valid JSON.\n\n## Next step\n\nOffer to place the 3 to 5 strongest questions on the pricing or services page (pricing-page, services-page), or to add the schema if it was not requested.\n"
}