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

88%

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

Quality

Content

77%

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

The body is highly actionable with concrete tables, token mappings, and templates organized into a clear sequenced workflow with validation checkpoints. It is somewhat long and monolithic with no reference files, leaving room to tighten prose and split detailed references out via progressive disclosure.

Suggestions

Trim the Background rationale (71-system catalog derivation, excluded-dimension explanation) to the minimum needed for the agent, since it is contextual rather than operational.

Move the large token-resolution table (Section 2.1) and the DESIGN.md template (Section 3) into separate reference files under references/ and link to them one level deep, keeping SKILL.md as a lean overview.

Reduce redundancy between the Section 2 dimension vocabulary table and the Section 2.1 token-resolution table so each value is authoritatively stated once.

Dimension	Reasoning	Score
Conciseness	Mostly efficient high-signal tables (mapping, dimensions, token resolution, defaults), but the Background prose about the 71-system catalog and some restatement of values across the dimension table, token table, and DESIGN.md template could be tightened, fitting the level-2 'mostly efficient but could be tightened' anchor rather than the lean level-3 case.	2 / 3
Actionability	Fully concrete and executable: a complete I-Lang example, a natural-language mapping table, closed-vocabulary dimension tables, concrete hex/font/spacing token mappings, default-resolution rules, a full DESIGN.md template, and a 4-section HTML preview spec — copy-paste ready guidance matching the level-3 anchor.	3 / 3
Workflow Clarity	A clearly sequenced 5-step workflow (Accept input → Validate dimensions → Generate DESIGN.md → Generate preview → Report defaults) with explicit validation checkpoints: closed-vocabulary enforcement, prompting for clarification on unrecognized values, overwrite confirmation, and a final transparency report of applied defaults.	3 / 3
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ absent) and the skill is a single ~250-line monolithic SKILL.md; well-organized into sections, but the token-resolution table, default rules, and DESIGN.md template are inline content that could be split into one-level-deep reference files, matching the level-2 'content that should be separate is inline' anchor.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 concise, third-person, and concrete, clearly stating what the skill does and when to trigger it. It enumerates the specific dimensions handled and provides natural trigger keywords, making it both specific and distinctive.

Dimension	Reasoning	Score
Specificity	Quotes multiple concrete actions — "Parse a structured design brief written in I-Lang protocol format into a concrete design spec" and "Eliminates ambiguity ... by requiring explicit dimensions: palette, typography, layout, mood, density, and constraints" — naming the domain, the output, and the concrete dimensions handled.	3 / 3
Completeness	It answers both "what" (parse a structured brief into a concrete design spec) and "when" via an explicit trigger-keywords clause, which qualifies as equivalent explicit trigger guidance and avoids the level-2 cap for a missing 'Use when' clause.	3 / 3
Trigger Term Quality	Explicit "Trigger keywords: \"design brief\", \"create a design brief\", \"ilang brief\", \"structured brief\"" gives good coverage of natural phrases a user would say, matching the level-3 anchor rather than the level-2 single-keyword case.	3 / 3
Distinctiveness Conflict Risk	The I-Lang design-brief niche with distinct triggers ("design brief", "ilang brief") is unlikely to overlap with other skills, matching the clear-niche level-3 anchor rather than the level-2 'Works with document files' overlap case.	3 / 3
	Total	12 / 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
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: f2760fd

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