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

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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.

A highly actionable, well-structured skill body with concrete templates and exact token tables. Its main weakness is conciseness — provenance and background prose inflate the body without aiding execution, and a final verification checkpoint is missing.

Suggestions

Trim the Background and Section 3 provenance prose (e.g., '71 is the research sample, not the current bundled-system count' and 'inherited from OpenDesign's original upstream baseline') — Claude does not need the catalog history to execute; keep only the 8-dimension list and the closed-vocabulary rule.

Add an explicit verification checkpoint before writing DESIGN.md (e.g., 'Confirm all 8 dimensions are resolved and every value appears in the Section 2.1 token table before generating output') to close the workflow_clarity gap.

Consider moving the large Section 2.1 token-resolution table and the DESIGN.md template into a reference file (e.g., references/tokens.md) referenced from SKILL.md, to improve progressive_disclosure and reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	The Background and Section 3 provenance paragraphs explain derivation history ("71 is the research sample, not the current bundled-system count"; "inherited from OpenDesign's original upstream baseline") that Claude does not need to execute, placing it at anchor 3 — mostly efficient with some unnecessary explanation.	3 / 5
Actionability	The body provides copy-paste-ready resources — a full I-Lang example, closed-vocabulary tables, exact concrete token mappings (hex/font/spacing), and a complete DESIGN.md template — matching anchor 5's fully executable, copy-paste-ready guidance.	5 / 5
Workflow Clarity	Five numbered steps are clearly sequenced with checkpoints (a clarification loop for unrecognized values, an overwrite confirmation), but it lacks an explicit final output-verification step, fitting anchor 4 rather than 5.	4 / 5
Progressive Disclosure	The skill is self-contained with well-organized sections and no external file references; the large inline token-resolution table and DESIGN.md template are a minor organization gap rather than a structure failure, fitting anchor 4 (the under-50-line simple-skill exception does not apply).	4 / 5
	Total	16 / 20 Passed

Description

78%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.

A strong, specific description that pairs a clear "what" with explicit trigger keywords and a well-scoped niche. It is slightly limited in action breadth (essentially one main verb) and could overlap with adjacent design skills.

Dimension	Reasoning	Score
Specificity	Names the domain ("structured design brief written in I-Lang protocol format") and 1-2 concrete actions ("Parse ... into a concrete design spec", "requiring explicit dimensions"), matching anchor 3; it does not list several distinct actions, so it stops short of 4.	3 / 5
Completeness	It explicitly answers what (parse an I-Lang brief into a design spec with named dimensions) and when (concrete trigger keywords), matching anchor 5's "both what and when with concrete trigger phrases"; the "Trigger keywords:" line is equivalent explicit trigger guidance, so it is not capped at 3.	5 / 5
Trigger Term Quality	Trigger keywords "design brief", "create a design brief", "ilang brief", "structured brief" give good natural-phrase coverage, but "ilang"/"structured" lean technical and a few synonyms are missing, fitting anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The I-Lang / design-brief niche with dedicated triggers is mostly distinct from sibling skills, with only minor overlap risk against other design-system skills, fitting anchor 4.	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: d4138ea

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