reference-design-contract

Turn vague taste, screenshots, URLs, product notes, or "make it feel like this" references into a grounded DESIGN.md plus an implementation handoff. Use it before prototypes, decks, redesigns, or image remix work when the user needs a reusable visual direction rather than a one-off prompt.

Quality

86%

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

Quality

Content

86%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 body is well-structured, concrete, and actionable with a clean overview-plus-reference split and a sequenced workflow that includes validation. The only weaknesses are minor: a lightly trimmable intro and a feedback loop that lives in the referenced checklist rather than inline.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, avoiding concept over-explanation, but the opening restates purpose with a slight rhetorical flourish ("The goal is not... The goal is...") that could be trimmed, keeping it just below the 5-anchor.	4 / 5
Actionability	For an instruction-only skill it is fully actionable: it specifies the exact three files, the exact nine DESIGN.md headings, required per-file elements, confidence labels (observed/provided/inferred), and the keep/change/do-not-copy framework, so Claude can execute without guessing.	5 / 5
Workflow Clarity	An 8-step sequence with an explicit validation checkpoint (step 8 referencing checklist.md P0 gates) is clear, but the validate→fix→retry feedback loop is delegated to the referenced checklist rather than spelled out inline, a minor validation gap versus the 5-anchor.	4 / 5
Progressive Disclosure	The body is a clear overview with a well-signaled one-level-deep reference (references/checklist.md, verified to exist) for the detailed P0 gates and quality bar, and content is appropriately split, matching the 5-anchor.	5 / 5
	Total	18 / 20 Passed

Description

87%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 clearly and concretely states what the skill produces and when to use it, with natural trigger phrases and a distinct niche. It is strong throughout, with only minor room for more action/synonym breadth in the specificity and trigger dimensions.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete deliverable artifacts ("a grounded DESIGN.md plus an implementation handoff") with comprehensive input types, but presents essentially one transformation rather than the multiple distinct actions of the 5-anchor.	4 / 5
Completeness	Explicitly answers both what ("Turn...references into a grounded DESIGN.md plus an implementation handoff") and when ("Use it before prototypes, decks, redesigns, or image remix work...") with concrete trigger contexts, matching the 5-anchor.	5 / 5
Trigger Term Quality	Includes natural user phrases like "make it feel like this", "redesigns", "image remix", "decks", and "prototypes"; good coverage but a few synonyms and explicit artifact-name variants are missing relative to the 5-anchor.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (reference→reusable design contract) with distinct framing ("reusable visual direction rather than a one-off prompt"), giving it minimal overlap risk with general design or image-generation skills.	5 / 5
	Total	18 / 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/reference-design-contract/SKILL.md
Commit: d4138ea

Reviewed: ~7 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.