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".

72

Quality

88%

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

86%Weight 40%Scale 1-5

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 tightly-scoped, highly actionable instruction skill with concrete numeric specs and a self-check, well-organized into clear sections. The sole gap is the absence of an explicit validation fix→retry loop in the workflow.

Suggestions

Add an explicit feedback loop after Self-check, e.g. 'If any check fails, revise the offending section and re-verify before emitting the artifact.'

Tighten a few minor phrasings (e.g. 'a real article — at least 600 words' could drop the dash clause) to push conciseness toward a 5.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (e.g., "long-form is 70% type, 20% image, 10% chrome", "Drop caps only if the DS mood is editorial / serif"), with only minor phrases that could be trimmed.

4 / 5

Actionability

Concrete, executable specs throughout — line length "60–75 chars", "Accent appears at most twice", max-width "680–720px", named `data-od-id` targets, and a copy-paste `<artifact>` output contract covering the common cases.

5 / 5

Workflow Clarity

A clear 5-step sequence ends with an explicit Self-check checklist (hierarchy, line length, accent count, magazine feel), but it lacks an explicit fix→retry feedback loop, so it sits just below the anchor with error-recovery loops.

4 / 5

Progressive Disclosure

A ~50-line skill with well-organized sections (Workflow, Output contract) and no bundle files to disclose; the only external reference (DESIGN.md) is injected rather than nested, satisfying the simple-skill exception for a 5.

5 / 5

Total

18

/

20

Passed

Description

91%Weight 40%Scale 1-5

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

A strong description that clearly states both the deliverable and its trigger conditions with concrete, natural-language keywords and multilingual synonyms. The only weakness is mild overlap risk from broad terms like "post" and "article".

DimensionReasoningScore

Specificity

Names concrete output components ("masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts") rather than vague language, though it lists structural parts rather than verb-driven actions, leaving a minor gap versus a fully comprehensive action list.

4 / 5

Completeness

Explicitly answers both what ("A long-form article / blog post" with enumerated components) and when ("Use when the brief asks for 'blog', 'article', 'post', 'essay', or 'case study'") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural user terms comprehensively — "blog", "article", "post", "essay", "case study" plus synonyms in the triggers list (newsletter, 博客, 文章), matching the anchor for comprehensive coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

The editorial long-form niche is distinct and well-scoped, but generic triggers like "post" and "article" carry minor overlap risk with other writing/content skills.

4 / 5

Total

18

/

20

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.