{
  "context": "Tests whether the skill prevents unsupported topic-only article drafting. For a generated answer, score the produced brief. For a usage specification, score whether the tile clearly requires or exemplifies the same brief behavior; it need not include a final article or enumerate every possible source inside the inline example when the template or references require it. Strong answers infer brief mode, create a useful editorial brief and source plan, label assumptions, offer safe angle options, and refuse to invent facts, quotes, citations, examples, or current claims.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Brief mode selected",
      "description": "The response treats the topic-only request as a brief/source-plan task rather than writing a finished factual article from generic knowledge.",
      "max_score": 12
    },
    {
      "name": "Reader and promise defined",
      "description": "The brief names a specific provisional reader, the reader's job or confusion, and a concrete promise beyond the broad topic of AI in healthcare.",
      "max_score": 10
    },
    {
      "name": "Angle options are distinct",
      "description": "The output gives multiple article angle options with different editorial functions such as diagnostic, decision guide, case-led, or synthesis, not minor headline variations.",
      "max_score": 10
    },
    {
      "name": "Evidence standard stated",
      "description": "The response defines what source types are required before publication, including current primary or expert sources for factual healthcare and AI claims. A usage specification earns full credit when it requires source type, support status, and action fields plus stronger evidence or human review for high-stakes claims.",
      "max_score": 12
    },
    {
      "name": "Source packet needed",
      "description": "The output lists concrete missing source-packet items such as interviews, official guidance, product artifacts, customer examples, data, or source excerpts. A usage specification earns full credit when templates or references require those source-packet gap types, even if the inline example shows only one row.",
      "max_score": 10
    },
    {
      "name": "No fabricated support",
      "description": "The response does not invent citations, statistics, quotes, source titles, URLs, case studies, company facts, or unsupported healthcare claims. A usage specification earns full credit when it explicitly forbids fabricated support and directs missing support into a source plan or verification queue.",
      "max_score": 14
    },
    {
      "name": "Structure and voice specified",
      "description": "The brief names a suitable article structure and gives observable voice rules rather than vague instructions such as 'make it engaging'. A usage specification earns full credit when it requires structure fields, section jobs, observable diction/claims-posture rules, hype limits, and uncertainty handling.",
      "max_score": 10
    },
    {
      "name": "Acceptance criteria included",
      "description": "The response lists observable conditions for publishability, including source support, reader value, risk handling, and anti-generic standards.",
      "max_score": 10
    },
    {
      "name": "Focused collaboration",
      "description": "The answer keeps momentum by providing a usable provisional brief and only asks a small number of blocking questions, if any.",
      "max_score": 6
    },
    {
      "name": "High-stakes risk handled",
      "description": "The response recognizes healthcare as a high-stakes domain and calls for stronger verification or human review before final factual publication.",
      "max_score": 6
    }
  ]
}