{
  "schema_version": 2,
  "kind": "shortening-method",
  "format": "agent-skill",
  "id": "faq-answer",
  "name": "FAQ answer",
  "category": "Writing",
  "summary": "Reduce an answer to the specific question, its conditions, and the next step.",
  "use_cases": [
    "Help-center answers",
    "Product FAQs",
    "Service questions"
  ],
  "word_count": 146,
  "url": "https://sho.rten.it/methods/faq-answer/",
  "instructions_url": "https://sho.rten.it/methods/faq-answer/SKILL.md",
  "skill_url": "https://sho.rten.it/methods/faq-answer/SKILL.md",
  "json_url": "https://sho.rten.it/methods/faq-answer/llms.txt",
  "plain_text_url": "https://sho.rten.it/methods/faq-answer/prompt.txt",
  "license": "MIT",
  "sources_url": "https://sho.rten.it/sources/#faq-answer",
  "skill_name": "faq-answer",
  "skill_description": "Reduce an answer to the specific question, its conditions, and the next step. Use for Help-center answers, Product FAQs, Service questions.",
  "agents_md_url": "https://sho.rten.it/methods/faq-answer/AGENTS.md",
  "sources": [],
  "instructions": "Shorten the supplied FAQ answer around its exact question. Start with a direct answer that is accurate on its own. Follow it with only the conditions, exceptions, explanation, or next step the reader needs for that question.\n\nPreserve eligibility, limits, deadlines, costs, required evidence, and the difference between a guarantee and a possibility. Keep a supplied link or UI label when it is needed to act. If the answer depends on missing information, name that dependency instead of writing an unconditional yes or no.\n\nRemove company background, repeated versions of the question, unrelated features, and instructions for other problems. Prefer a short paragraph; use a list for distinct conditions or steps. Do not invent policy, support commitments, refund rights, or product behavior. Do not broaden the question to make the answer sound more helpful. Return the question and revised answer, or only the answer if requested.",
  "example": {
    "context": "Workshop booking FAQ",
    "before": "Question: Can I transfer my workshop ticket to someone else? Answer: We understand that plans can change and that people sometimes cannot attend an event they have booked. Ticket transfers are possible for this workshop. The new attendee must be at least 18 years old. You need to email the booking reference and the new attendee's full name to the event team at least 48 hours before the workshop starts. There is no transfer fee. Once that deadline has passed, transfers are not available. This process transfers the ticket; it does not provide a refund.",
    "after": "Can I transfer my workshop ticket to someone else?\n\nYes, at no charge, if the new attendee is 18 or older. Email the event team your booking reference and their full name at least 48 hours before the workshop starts. Later transfers are unavailable. A transfer does not provide a refund.",
    "must_preserve": [
      "Transfer is free",
      "New attendee must be 18 or older",
      "Email booking reference and full name to the event team",
      "At least 48 hours before the workshop",
      "No late transfers or refund through this process"
    ],
    "omitted": [
      "Drops empathy framing and repeated explanations of changed plans."
    ],
    "kind": "illustrative"
  }
}