editorial

Magazine-inspired editorial layout with refined serif typography, structured grids, and elegant reading experiences.

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/editorial/SKILL.md

Quality

Content

85%

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

The content is a concise, well-structured design-system guideline with a clear sequenced authoring workflow and quality gates, assuming Claude's competence throughout. Its main gap is actionability: concrete defaults and structure are present, but no executable component examples (markup, token CSS, code snippets) are provided.

Suggestions

Add at least one concrete, copy-paste-ready example (e.g., a sample component anatomy with token usage in CSS/JSX) to push actionability to level 3.

Include a small concrete anti-pattern example pairing a do-rule with its don't-example, since the 'Example Constraint Language' section currently only describes the pattern abstractly.

Dimension	Reasoning	Score
Conciseness	The body is a lean, well-organized spec of tokens, rules, and workflow steps that assumes Claude's competence and avoids explaining basic design concepts; every section earns its place without padding.	3 / 3
Actionability	It provides concrete, specific guidance (token values, state lists, required output structure), but as an instruction-only design-system skill it stops short of fully executable/copy-paste-ready artifacts like component markup or token CSS; the guidance is actionable but not concrete enough for level 3.	2 / 3
Workflow Clarity	The 'Guideline Authoring Workflow' gives a clear, explicitly sequenced six-step process ending in a QA checklist, and the 'Expected Behavior' and 'Quality Gates' sections provide concrete checkpoints and prioritization rules for error/conflict resolution.	3 / 3
Progressive Disclosure	As a self-contained skill under ~80 lines with no bundle files, content is organized into clearly labeled sections (Foundations, Rules, Workflow, Output Structure, QA) with no nested references, satisfying the simple-skill allowance for a top score.	3 / 3
	Total	11 / 12 Passed

Description

37%

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 establishes a clear editorial/magazine design niche with concrete stylistic elements, but it lacks any 'Use when...' trigger guidance and relies on design jargon rather than natural user phrasing. Adding explicit trigger terms and concrete actions would lift it across most dimensions.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers such as 'Use when creating magazine-style layouts, long-form article designs, or blog templates with editorial typography.'

Replace design jargon with terms users actually say (e.g., 'magazine layout', 'article template', 'blog design system') to improve trigger term coverage.

Reframe the stylistic descriptors as concrete actions (e.g., 'Build magazine-style article layouts with serif typography and structured grids') to push specificity to level 3.

Dimension	Reasoning	Score
Specificity	It names the domain (editorial layout) and lists several concrete artifacts ('refined serif typography, structured grids, and elegant reading experiences'), but these are stylistic descriptors rather than distinct implementable actions, so it stops short of the 'multiple specific concrete actions' anchor at level 3.	2 / 3
Completeness	It answers 'what does this do' (magazine-inspired editorial layout with typography and grids) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	The terms used ('editorial layout', 'refined serif typography', 'structured grids') are design jargon a user is unlikely to naturally say when they need this skill, and there are no common natural variations like 'magazine layout', 'article template', or 'blog design'.	1 / 3
Distinctiveness Conflict Risk	It is anchored to a fairly specific niche (magazine editorial design), but the absence of explicit triggers means it could still overlap with other generic design/layout skills.	2 / 3
	Total	7 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: bergside/awesome-design-skills
Path: skills/editorial/SKILL.md
Commit: f631a09

Reviewed: 1 day 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.