article-magazine

Huashu / huashu-md-html-inspired magazine article layout for turning Markdown or notes into a polished long-form HTML essay.

Quality

61%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/article-magazine/SKILL.md

Quality

Content

72%

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, well-organized spec sheet for a single-purpose template skill, earning top marks for conciseness and structure, but it lacks a complete executable HTML skeleton and an explicit assembly/verification sequence, capping actionability and workflow clarity at the mid level.

Suggestions

Add a minimal complete HTML skeleton (hero, article container, sample heading/quote/code/list/hr/footer) so the guidance is copy-paste ready rather than a per-component spec list.

Turn the bullet list into an explicit ordered build sequence (e.g. '1. Render hero ... 2. Wrap body in max-w-[700px] ... 3. Add footer CTA') to make the workflow unambiguous.

Include a brief verification step (e.g. open index.html and confirm hero/quote/code/list render with the signature styling) to close the loop.

Dimension	Reasoning	Score
Conciseness	The body is a lean bullet list of concrete styling specs with no padding or explanation of concepts Claude already knows; every line (hero, body width, Tailwind classes, quote/code/list styling) earns its place.	3 / 3
Actionability	It gives several concrete details (Tailwind classes like `text-lg leading-relaxed text-neutral-700 dark:text-neutral-300`, ~700px max width, serif headings), but it stops at per-component specs and never provides a complete, copy-paste-ready HTML skeleton, leaving key structural details missing.	2 / 3
Workflow Clarity	The bullets imply a top-to-bottom layout order (hero, body, headings, quotes, code, lists, separators, footer), but this reads as a parts spec rather than an explicitly sequenced workflow with assembly or verification steps, so it lands at the 'sequence present but checkpoints implicit' level.	2 / 3
Progressive Disclosure	The skill is under 50 lines, single-purpose, needs no external references (none exist in references/scripts/assets), and the body is well-organized as a tight bulleted spec, which meets the rubric's allowance for simple skills to score 3 on progressive disclosure.	3 / 3
	Total	10 / 12 Passed

Description

50%

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 and names a concrete niche, but it relies on obscure jargon ('Huashu / huashu-md-html') and omits any explicit 'Use when...' trigger guidance, leaving it at the mid-level across all dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when turning Markdown or notes into a polished long-form HTML essay, blog post, or newsletter.'

Replace or downplay the 'Huashu / huashu-md-html-inspired' jargon with natural user terms (blog, essay, newsletter) so the description matches what users actually say.

List a couple more concrete actions (e.g. 'add hero headers, styled quotes, and a call-to-action card') to raise specificity.

Dimension	Reasoning	Score
Specificity	The description names a concrete domain ('magazine article layout') and one transformation action ('turning Markdown or notes into a polished long-form HTML essay'), but does not list multiple distinct concrete actions, so it sits at the 'names domain and some actions' level rather than the comprehensive list of anchor 3.	2 / 3
Completeness	It clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	It includes some natural terms users might say ('Markdown', 'notes', 'HTML essay', 'magazine article'), but the obscure 'Huashu / huashu-md-html-inspired' jargon is not something a user would naturally utter and common variations like 'blog' or 'newsletter' (present in tags) are absent.	2 / 3
Distinctiveness Conflict Risk	The 'magazine article / long-form HTML essay' niche is fairly specific and unlikely to fire for unrelated skills, but it could still overlap with other article, essay, or HTML-formatting skills, so it does not reach the clearly-distinct anchor 3.	2 / 3
	Total	8 / 12 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: skills/article-magazine/SKILL.md
Commit: f2760fd

Reviewed: about 16 hours 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.