spacious

Generous whitespace, consistent padding, and grid-based layouts for clean, readable, and breathing interfaces.

Quality

51%

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

Quality

Content

62%

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 well-structured, token-dense guideline-authoring framework with concrete design tokens, a clear sequenced workflow, and explicit quality gates. Its main gaps are conceptual redundancy across rule sections and the absence of a worked example showing the required output structure applied.

Suggestions

Consolidate the overlapping guidance in "Rules: Do/Don't", "Quality Gates", and "Example Constraint Language" into a single rules-and-gates section to reduce redundancy.

Add one fully worked example (e.g. a sample Button guideline) that demonstrates the Required Output Structure with anatomy, states, tokens, accessibility criteria, and QA checklist.

Consider moving the token tables (color palette, typography scale) to a short reference section or file so the overview stays scannable and supports progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean and does not over-explain known concepts, but principles are restated across "Rules: Do/Don't", "Quality Gates", and "Example Constraint Language", so it could be consolidated to tighten token use.	2 / 3
Actionability	It supplies concrete tokens (hex colors, type scale, 8pt spacing) and a required output structure, but provides no worked example of actual generated guidance, leaving the instruction set concrete yet incomplete.	2 / 3
Workflow Clarity	The 6-step "Guideline Authoring Workflow" is clearly sequenced and backed by explicit "Quality Gates" and a terminal QA-checklist step, providing clear validation checkpoints for the authoring process.	3 / 3
Progressive Disclosure	Content is well-organized into headed sections with no nested references, but everything is inline with no external references; at ~80 lines it slightly exceeds the under-50-line simple-skill exemption that would allow a 3 on organization alone.	2 / 3
	Total	9 / 12 Passed

Description

40%

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 conveys a clear design aesthetic but fails to state what the skill actually does or when to invoke it, omitting any action verbs and any "Use when..." trigger. It is distinct enough within a design niche yet risks overlapping with broader design skills.

Suggestions

Lead with a concrete action verb and the skill's purpose, e.g. 'Authors implementation-ready design-system guidelines for spacious, grid-based interfaces.'

Add an explicit 'Use when...' trigger clause naming natural terms users would say (e.g. 'Use when creating or reviewing design-system guidance for whitespace, spacing, padding, or grid layouts').

Include common trigger variations such as 'spacing', 'layout', 'design system', and 'UI' to improve discoverability and reduce conflict with general design skills.

Dimension	Reasoning	Score
Specificity	The description lists design elements ("Generous whitespace, consistent padding, and grid-based layouts") but contains no verbs or concrete actions; it describes an aesthetic rather than what the skill does, so it does not meet the anchor requiring 'some actions'.	1 / 3
Completeness	It offers a weak "what" (aesthetic attributes rather than the guideline-authoring action) and provides no "Use when..." clause, so per the judging guidelines completeness is capped at 2 with "when" only implied by the closing purpose phrase.	2 / 3
Trigger Term Quality	Terms like "whitespace", "padding", "grid-based layouts", and "clean, readable" are relevant design vocabulary a user might say, but common variations such as "spacing", "layout", "design system", and "UI" are missing.	2 / 3
Distinctiveness Conflict Risk	It carves a somewhat specific niche (spacious/minimal design) but lacks explicit triggers, so it could still overlap with general UI or design-system 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/spacious/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.