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

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%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 content is lean, highly actionable, and well-structured for a single-purpose instruction skill, with concrete rules and a self-check validation step. Main improvement would be adding an explicit fix-and-retry loop around the self-check and optionally a minimal HTML skeleton.

Suggestions

Turn the 'Self-check' into a feedback loop: add an explicit 'If a check fails, revise the offending section and re-run the checks before emitting.'

Include a minimal HTML skeleton (doctype → head with inline CSS → body) in the output contract so the artifact is closer to copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence — it does not explain what a blog post or HTML is — with only minor descriptive prose ('long-form is 70% type, 20% image, 10% chrome') that could be trimmed without loss.	4 / 5
Actionability	Concrete, specific guidance throughout — ordered sections, 'line length 60–75 chars', 'accent appears at most twice', 'max-width 680–720px', 'data-od-id on the headline, hero, body, pull quote, related grid' — with an explicit output-contract template; held back from 5 only because no full HTML skeleton is provided, leaving a couple of execution details to inference.	4 / 5
Workflow Clarity	A clear numbered sequence (1–5) with a dedicated 'Self-check' step that acts as a validation checkpoint; not a destructive or batch operation so no cap applies, but it lacks an explicit 'if check fails, fix and retry' feedback loop that would lift it to 5.	4 / 5
Progressive Disclosure	The skill body is under 50 lines, has no external references (no references/, scripts/, or assets/ bundle files exist), and is organized into clear 'Workflow' and 'Output contract' sections — meeting the simple-skill exception for a top progressive-disclosure score.	5 / 5
	Total	17 / 20 Passed

Description

83%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.

The description is well-constructed: third-person voice, explicit 'Use when' clause with concrete trigger phrases, and a clear enumeration of output components. It would benefit from aligning its trigger list with the frontmatter triggers (e.g., adding 'newsletter') and framing components as actions.

Suggestions

Mirror the frontmatter trigger list in the description's 'Use when' clause — add 'newsletter' so the description and triggers stay in sync.

Reframe some output components as concrete actions (e.g., 'lay out a masthead, hero, body, and related-posts grid') to strengthen the specificity of capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates several concrete output components — 'masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts' — which is strong, but these are output elements rather than distinct actions, leaving minor coverage gaps versus a fully comprehensive action list.	4 / 5
Completeness	Clearly answers both what ('A long-form article / blog post — masthead, hero image placeholder, article body...') and when ('Use when the brief asks for "blog", "article", "post", "essay", or "case study"') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage with 'blog', 'article', 'post', 'essay', 'case study', but omits 'newsletter' (which appears in triggers) and common synonyms, so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear editorial/blog-post niche with distinct triggers and minimal conflict risk, though broad terms like 'article'/'post' could overlap slightly with adjacent content skills.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: plugins/_official/examples/blog-post/SKILL.md
Commit: 81044a0

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.