modern

Contemporary editorial style with serif typography, minimal palettes, and clean layouts for polished digital products.

Quality

57%

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

Quality

Content

65%

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

The content is concise, well-structured, and offers specific foundational guidance for an instruction-only skill. Its main gaps are the absence of a concrete worked example and the lack of validation checkpoints and progressive file structure.

Suggestions

Add a short worked example showing one complete generated guideline (anatomy, states, tokens, a11y criteria) so the expected output is unambiguous.

Insert explicit validation checkpoints into the authoring workflow (e.g. "verify every rule is anchored to a token before proceeding to component rules").

Consider splitting the detailed component-rule expectations and quality gates into a referenced file to deepen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is a lean set of short bullet sections with no concept padding (no "what is a design system" filler), assuming Claude's competence throughout.	3 / 3
Actionability	It gives concrete directives (required states, token hex values, a required output structure) but provides no worked example of a finished guideline, leaving the expected output format underspecified.	2 / 3
Workflow Clarity	A clear 6-step authoring sequence is present and ends with a QA checklist, but there are no intermediate validation checkpoints or feedback loops between steps.	2 / 3
Progressive Disclosure	Sections are well organized, but the skill is a single monolithic file over 50 lines with no external references or file split, so progressive disclosure is minimal.	2 / 3
	Total	9 / 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 paints a clear aesthetic picture in third person but is adjective-heavy and action-light, with no explicit trigger guidance. It reads as a style tagline rather than a capability and usage statement.

Suggestions

Lead with concrete verbs, e.g. "Author modern editorial design-system guidelines with serif typography and minimal palettes."

Add an explicit trigger clause: "Use when creating or refining design-system guidance for polished digital products, or when the user mentions editorial style, serif typography, or minimal palettes."

Include natural keyword variations users would say (e.g. "design system", "editorial design", "serif fonts") to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	Names a concrete domain ("serif typography, minimal palettes, and clean layouts") but contains no verbs or concrete actions, so it describes an aesthetic rather than capabilities.	2 / 3
Completeness	It conveys what the skill produces (an editorial style) but provides no "Use when..." trigger clause, so the "when" guidance is missing and completeness is capped at 2.	2 / 3
Trigger Term Quality	Terms like "editorial style" and "serif typography" are partially natural, but there is no coverage of common variations a user would actually say when requesting this skill.	2 / 3
Distinctiveness Conflict Risk	The modern-editorial serif niche is somewhat specific, but without explicit triggers it could still overlap with other design-system skills.	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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: bergside/awesome-design-skills
Path: skills/modern/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.