design-brief

Parse a structured design brief written in I-Lang protocol format into a concrete design spec. Eliminates ambiguity from vague requests like "make it professional" by requiring explicit dimensions: palette, typography, layout, mood, density, and constraints. Trigger keywords: "design brief", "create a design brief", "ilang brief", "structured brief".

Quality

75%

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

Quality

Content

75%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 highly actionable with concrete tokens, templates, and a clear five-step workflow including input validation and an overwrite checkpoint. Its main weakness is the Background section's historical rationale, which is padding that could be trimmed for token efficiency.

Suggestions

Trim or remove the Background section (the 71-system catalog derivation and mood/density rationale) since Claude does not need this history to execute the workflow.

Add an explicit output-validation step after generating DESIGN.md and brief-preview.html (e.g., verify all hex values and font stacks come from Section 2.1) to close the feedback-loop gap.

Consider extracting the large symbolic→concrete token table (Section 2.1) into a reference file to reduce SKILL.md length while keeping the core workflow inline.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense, actionable reference material (token, mapping, and default tables), but the Background section explaining the '71-system catalog' derivation and the rationale for adding mood/density is unnecessary explanatory padding Claude does not need.	3 / 5
Actionability	Provides fully concrete, copy-paste-ready guidance: exact hex color tokens, font stacks with weights and sizes, spacing values, a complete DESIGN.md template, and a concrete four-section preview spec covering the common cases.	5 / 5
Workflow Clarity	Five clearly numbered sections (accept input, validate, generate DESIGN.md, generate preview, report) with explicit input validation in Section 2 and an overwrite checkpoint for the destructive DESIGN.md write; a minor gap is the lack of an output-validation feedback loop.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is self-contained with well-organized numbered sections and subsections; the large inlined tables are core executable reference rather than misplaced detail, yielding good structure with minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

75%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 specific and well-triggered, clearly stating its purpose and listing concrete trigger keywords with low conflict risk. It could improve by converting the mechanical 'Trigger keywords' list into a natural 'Use when...' sentence and broadening natural-language trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('structured design brief written in I-Lang protocol format') and several concrete actions—parsing into a design spec and requiring explicit dimensions (palette, typography, layout, mood, density, constraints)—with only minor coverage gaps.	4 / 5
Completeness	Clearly states what it does (parse a brief into a concrete design spec) and provides explicit trigger guidance via the 'Trigger keywords' line, which is equivalent to a 'Use when' clause; the 'when' could be phrased more naturally as a sentence.	4 / 5
Trigger Term Quality	Lists natural trigger phrases a user would say ('design brief', 'create a design brief') alongside more technical variants ('ilang brief', 'structured brief'), giving good but not fully comprehensive keyword coverage.	4 / 5
Distinctiveness Conflict Risk	The I-Lang protocol framing and 'design brief' niche are mostly distinct with minimal conflict risk, though 'design brief' could overlap slightly with general design-generation skills.	4 / 5
	Total	16 / 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: skills/design-brief/SKILL.md
Commit: 1a7a23d

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