{
  "context": "The agent was asked to write a publish-ready thought leadership article for the tessl.io blog on context engineering for AI agents. The article must introduce a named framework and be structured appropriately for the thought leadership format. Evaluate the output file article.md.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Problem-first structure",
      "description": "The article opens by surfacing a real tension or misconception engineers face, not by immediately presenting a solution. The hook acknowledges what already works before introducing the problem.",
      "max_score": 10
    },
    {
      "name": "Named framework",
      "description": "The article introduces at least one explicitly named mental model (e.g., a named 2x2, lifecycle, taxonomy, or spectrum) that a reader could repeat and use themselves. The framework must have a distinct name, not just be described in prose.",
      "max_score": 12
    },
    {
      "name": "Featured snippet definition",
      "description": "The article includes a 40-60 word definition of the core concept in the format '[Term] is [definition]. It [what it does]. [Why it matters].' This definition should appear early and be suitable for a Google featured snippet.",
      "max_score": 8
    },
    {
      "name": "Concrete example per section",
      "description": "Every major section contains at least one concrete example or specific data point. There are no two consecutive paragraphs of pure theory without an illustration. Specific numbers are preferred over qualitative claims.",
      "max_score": 10
    },
    {
      "name": "Counterargument pre-empted",
      "description": "The article explicitly anticipates the strongest skeptical objection to its central claim and addresses it directly, not dismissively.",
      "max_score": 8
    },
    {
      "name": "Closing with question",
      "description": "The article ends with a provocative question, a concrete next step, or a deliberate callback to the hook. The closing is not generic.",
      "max_score": 6
    },
    {
      "name": "No hype or sycophantic language",
      "description": "The article contains none of the prohibited terms: 'revolutionary', 'game-changing', 'cutting-edge', 'unlock', 'supercharge', 'exciting', 'incredible', 'amazing'. Tone is conversational and authoritative without hype.",
      "max_score": 8
    },
    {
      "name": "No em dashes",
      "description": "The article contains zero em dashes. Where a writer might use an em dash, the sentence is restructured using a comma, period, or new sentence.",
      "max_score": 6
    },
    {
      "name": "SEO metadata complete",
      "description": "The metadata block includes: title (<60 chars, keyword front-loaded), one primary keyword from the priority clusters, meta description (130-155 characters), a URL slug (3-6 words, lowercase, hyphenated), at least 2 internal links with contextual anchor text, and estimated read time.",
      "max_score": 12
    },
    {
      "name": "H2 structure",
      "description": "The article has 2-5 H2 headings. At least one H2 contains the primary keyword or a close variant. No H2 is generic ('Introduction', 'Conclusion'). H2s are problem-oriented or question-oriented.",
      "max_score": 8
    },
    {
      "name": "Word count and product mentions",
      "description": "The article is 1500-2500 words. There are 0 or 1 product mentions (tessl.io). The article is not a product pitch.",
      "max_score": 6
    },
    {
      "name": "Developer-first framing",
      "description": "The article frames concepts from the perspective of someone building systems (chef's kitchen), not consuming a product (plate of food). Analogies reference developer-native concepts where applicable.",
      "max_score": 6
    }
  ]
}