Content creator for tessl.io — generates publish-ready blog articles with SEO metadata, Tessl house style, and technical authority.
90
79%
Does it follow best practices?
Impact
92%
1.26xAverage score across 10 eval scenarios
Passed
No known issues
{
"context": "The agent was asked to write a publish-ready skill showcase article for the tessl.io blog featuring three code-review-related skills. Evaluate the output file article.md for adherence to the skill showcase format and house style.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Showcase structure",
"description": "The article follows the correct sequence: Hook, Why skills help, Setup with tessl i commands, Skills walkthrough, Worked example, Choosing right skills, CTA to Registry. All major sections are present and in logical order.",
"max_score": 12
},
{
"name": "Eval scores included",
"description": "Each featured skill's eval score is mentioned in the skills walkthrough section (87/100, 79/100, 91/100 or equivalents as given in the task brief).",
"max_score": 8
},
{
"name": "Install commands shown",
"description": "Each skill's install command is shown as a code block or inline code (tessl i pr-context, tessl i lint-annotator, tessl i test-failure-explainer).",
"max_score": 8
},
{
"name": "Worked example with output",
"description": "The article includes a realistic before/after or actual-output example showing what the agent produces when one of the skills is active. The example must be concrete, not described in abstract terms.",
"max_score": 10
},
{
"name": "CTA to Registry",
"description": "The article ends with a clear call to action that directs the reader toward the Tessl Skills Registry. The CTA is specific and actionable, not generic.",
"max_score": 8
},
{
"name": "Internal links",
"description": "At least 2 internal links are placed within the article body with contextual anchor text. Anchor text is descriptive (not 'click here'). If target URLs are unknown, anchor text includes '[find matching tessl.io article]' notation.",
"max_score": 8
},
{
"name": "Meta description length",
"description": "The meta description in the metadata block is between 130 and 155 characters (inclusive), includes the primary keyword, and is written to be compelling to click.",
"max_score": 8
},
{
"name": "Skills terminology",
"description": "The article consistently uses 'skills' not 'tiles'. If 'tiles' appears, it is only for historical context with the explanation 'skills (previously called tiles)'.",
"max_score": 6
},
{
"name": "Features framed by problems",
"description": "Each skill is introduced by explaining the problem it solves, not just listing what it does. The writing avoids bullet-point feature dumps without problem framing.",
"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), primary keyword from priority clusters, URL slug (3-6 words, lowercase, hyphenated), and estimated read time. All fields are present.",
"max_score": 8
},
{
"name": "Word count",
"description": "The article body is between 1200 and 2000 words, appropriate for the skill showcase format.",
"max_score": 10
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
skills
article-creator