CtrlK
BlogDocsLog inGet started
Tessl Logo

blog-post

A long-form article / blog post — masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts. Use when the brief asks for "blog", "article", "post", "essay", or "case study".

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, actionable spec for a single HTML article page: a sequenced workflow, concrete numeric and structural constraints, a copy-ready artifact contract, and a self-check validation step. It assumes Claude's intelligence and avoids teaching basics.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what a blog post is, and every line (e.g. 'long-form is 70% type, 20% image, 10% chrome', '60–75 chars for body prose') earns its place; it is not the level-2 case that includes unnecessary explanation.

3 / 3

Actionability

For an instruction-only generation skill the guidance is concrete and specific — fixed section order, '600 words across 4–6 H2 sections', 'accent rule on the inline-start edge', 'max-width 680–720px', 'data-od-id on the headline, hero, body, pull quote, related grid', plus a copy-ready artifact template; per scoring notes, absent code is not penalized when guidance is this actionable.

3 / 3

Workflow Clarity

A clear numbered sequence (Read DESIGN.md → Pick topic → Sections → Write → Self-check) with an explicit self-check validation checkpoint covering hierarchy, line length, and accent usage; it is not the level-2 case with implicit or missing checkpoints.

3 / 3

Progressive Disclosure

A single-purpose, well-organized skill under 50 lines with no external references needed; per the simple-skills note, well-organized sections (Workflow, Output contract) warrant a top score without bundle files.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, specific, and complete: it names concrete output components and pairs them with an explicit 'Use when' trigger clause covering natural user terms. It uses third-person voice and avoids fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete structural components — 'masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts' — matching the anchor for listing several specific concrete actions; it is not the level below which only names a domain and some actions.

3 / 3

Completeness

Explicitly answers both what ('A long-form article / blog post — masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts') and when ('Use when the brief asks for "blog", "article", "post", "essay", or "case study"'), matching the top anchor.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'blog', 'article', 'post', 'essay', 'case study' — giving good coverage of common variations rather than only some relevant keywords.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (long-form editorial article page) with distinct trigger terms, making it unlikely to fire for unrelated skills; it is not merely 'somewhat specific' as in the level-2 anchor.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.