{
  "context": "The agent was asked to write a publish-ready tutorial for the tessl.io blog that walks developers through running agent evals locally. Evaluate the output file article.md for adherence to the tutorial format and house style.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Outcome-first hook",
      "description": "The opening paragraph states what the developer will have accomplished by the end of the tutorial before explaining background or context. The hook is specific about the outcome, not generic.",
      "max_score": 10
    },
    {
      "name": "Tutorial structure complete",
      "description": "The article follows the correct sequence: Hook (outcome-first), Why this matters, Prerequisites, Numbered steps with headings, Advanced usage, Troubleshooting, Closing. All sections are present.",
      "max_score": 12
    },
    {
      "name": "Numbered steps with code blocks",
      "description": "Each step in the main walkthrough has a numbered heading, an explanation of what is happening and why, and a code block showing the exact command or file content. No step is explanation-only or code-only.",
      "max_score": 12
    },
    {
      "name": "Prerequisites section",
      "description": "The article includes a dedicated prerequisites section that lists what the developer needs before starting (software, accounts, etc.) without burying these requirements inside the steps.",
      "max_score": 6
    },
    {
      "name": "Advanced usage section",
      "description": "The article includes at least one advanced usage tip or variation that goes beyond the basic walkthrough, clearly marked as advanced.",
      "max_score": 6
    },
    {
      "name": "Troubleshooting section",
      "description": "The article includes a troubleshooting section covering at least two distinct common errors or failure modes, with concrete resolution steps for each.",
      "max_score": 8
    },
    {
      "name": "H2 with keyword",
      "description": "At least one H2 heading contains the primary keyword or a close variant. All H2s are specific and problem- or action-oriented, not generic labels like 'Introduction' or 'Conclusion'.",
      "max_score": 8
    },
    {
      "name": "URL slug format",
      "description": "The URL slug in the metadata block is 3-6 words, all lowercase, hyphenated, and includes the primary keyword.",
      "max_score": 6
    },
    {
      "name": "Developer-first framing",
      "description": "The article explains concepts from the perspective of someone building and operating systems, not consuming a product. The framing assumes a competent developer audience throughout.",
      "max_score": 8
    },
    {
      "name": "Concrete and internally consistent",
      "description": "Commands, file names, and output examples are specific and internally consistent throughout the tutorial. If a file is created in step 2, it is referenced by the same name in later steps.",
      "max_score": 8
    },
    {
      "name": "No hype or em dashes",
      "description": "The article contains no em dashes and none of the prohibited hype words ('revolutionary', 'game-changing', 'cutting-edge', 'unlock', 'supercharge', 'exciting', 'incredible', 'amazing').",
      "max_score": 6
    },
    {
      "name": "SEO metadata complete",
      "description": "Metadata block includes: title (<60 chars, keyword front-loaded when possible), primary keyword from priority clusters, meta description (130-155 characters), URL slug, at least 2 internal links with contextual anchor text, and estimated read time.",
      "max_score": 10
    }
  ]
}