CtrlK
BlogDocsLog inGet started
Tessl Logo

wireframe-greybox

A crisp greybox / blueprint lo-fi wireframe — neutral grey blocks on a pale page, image placeholders drawn as a rectangle with a diagonal X, text shown as solid "lorem bars" of varying widths, sharp 1.5–2px borders, and a single monospace redline accent for annotations. Reads like a structural blueprint before any visual design is applied. Use when the brief asks for "greybox", "blueprint wireframe", "lo-fi dashboard", "low fidelity", "线框图", or "灰盒原型".

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 a tight, well-structured instruction set for a single-purpose wireframing skill: concrete palette and component specs, a numbered workflow with a self-check, and a precise output contract. It loses only slightly on actionability and workflow_clarity for lacking an explicit code stub and a formal validate->retry loop.

Suggestions

Add a minimal inline HTML/CSS stub (e.g. a skeleton with the pale page, one grey block, and one X-crossed image placeholder) to lift actionability from concrete guidance to copy-paste-ready.

Reframe the 'Self-check' step as an explicit validate->fix->retry loop (list the specific failure conditions to check, then state 're-render until it passes') for stronger workflow_clarity.

DimensionReasoningScore

Conciseness

Lean and efficient — gives palette hex codes, a specific ordered component list, and an output contract without explaining HTML/CSS basics Claude already knows; every section earns its place.

5 / 5

Actionability

Highly concrete guidance (exact hex palette, named components, output contract with artifact tag), but provides no inline executable code stub — acceptable for an instruction-only skill, leaving minor gaps versus copy-paste-ready examples.

4 / 5

Workflow Clarity

Clear numbered 5-step sequence with a 'Self-check' validation step describing what to verify, but the feedback loop is described qualitatively ('fix it') rather than as an explicit validate->fix->retry cycle.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no external references needed — well-organized into Workflow / Output contract sections; per the simple-skill scoring note this merits full marks with no bundle files required.

5 / 5

Total

18

/

20

Passed

Description

100%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 exemplary: highly specific, concise, and explicitly pairs a vivid 'what' with a 'Use when...' trigger clause covering natural synonyms and multilingual variants. It is clearly distinguishable from other design skills.

DimensionReasoningScore

Specificity

Lists multiple concrete visual specifics — 'neutral grey blocks on a pale page', 'image placeholders drawn as a rectangle with a diagonal X', 'solid lorem bars of varying widths', 'sharp 1.5-2px borders', 'single monospace redline accent' — comprehensive coverage of the skill's output.

5 / 5

Completeness

Explicitly answers what ('a crisp greybox / blueprint lo-fi wireframe...') and when ('Use when the brief asks for...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms including synonyms ('greybox', 'blueprint wireframe', 'lo-fi dashboard', 'low fidelity') plus CJK variants ('线框图', '灰盒原型') a user would naturally say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (structural greybox wireframes pre-design) with distinct triggers; minimal overlap risk with other UI/design skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
Reviewed

Table of Contents

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.