CtrlK
BlogDocsLog inGet started
Tessl Logo

wireframe-annotated

An annotated / redline lo-fi wireframe — a desktop landing/marketing page drawn as flat greyboxes inside a browser chrome frame, overlaid with numbered annotation pins (①②③④⑤) in a single accent color, paired with a right-hand SPEC PANEL that lists each numbered pin with a short engineering / UX note. This is the "wireframe + redline spec" style — clean, flat, low-fidelity, NOT hand-drawn. Use when the brief asks for "annotated wireframe", "redline wireframe", "wireframe with spec", "lo-fi landing wireframe", "low fidelity", "线框图", "标注线框", or "redline".

75

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

92%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 tight, highly actionable body that gives concrete fonts, colors, layout, and pin/spec structure plus a validation self-check and a clear output contract. Its only weakness is mild redundancy between the intro and the frontmatter description.

Suggestions

Trim the intro's restatement of the description ("greyboxes carry the layout, numbered pins call out regions, and a right-hand spec panel turns each pin into a short engineering / UX note") since it duplicates the frontmatter; lead directly with the workflow constraints instead.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence (no explaining of what a wireframe or HTML is), but the intro paragraph restates material already in the description ("greyboxes carry the layout, numbered pins call out regions, and a right-hand spec panel turns each pin into a short engineering / UX note"), a minor instance that could be trimmed — hence 4 rather than 5.

4 / 5

Actionability

Fully concrete guidance: specific fonts (Inter/system-ui, IBM Plex Mono), one accent color (coral or blue), a two-column shell, per-pin block specs, worked spec-row examples ("① Sticky nav, 64px, condenses on scroll"), `data-od-id` attributes, and a copy-ready artifact output template.

5 / 5

Workflow Clarity

A clear 5-step sequence capped by an explicit self-check validation step with concrete pass/fail criteria (every pin has one matching spec row; accent color only on pins + spec numbers; thumbnail legibility), providing the feedback loop the top anchor calls for.

5 / 5

Progressive Disclosure

A self-contained, single-purpose skill with well-organized sections (Workflow, Output contract) and no need for external references; per the rubric's simple-skill guidance, that is sufficient for the top anchor.

5 / 5

Total

19

/

20

Passed

Description

95%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, concrete description that crisply defines a niche deliverable and backs it with comprehensive, multilingual trigger terms and an explicit 'Use when' clause. The only mild gap is that it frames a single output rather than enumerating several distinct actions.

DimensionReasoningScore

Specificity

Names the domain and several concrete specifics ("flat greyboxes inside a browser chrome frame", "numbered annotation pins (①②③④⑤) in a single accent color", "right-hand SPEC PANEL"), but it describes one deliverable rather than multiple distinct actions, so it sits at 4 rather than 5.

4 / 5

Completeness

Explicitly answers both what (an annotated/redline lo-fi wireframe with a spec panel) and when ("Use when the brief asks for…") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural terms including synonyms and a second language — "annotated wireframe", "redline wireframe", "wireframe with spec", "lo-fi landing wireframe", "low fidelity", "线框图", "标注线框", "redline" — matching the top anchor's coverage expectation.

5 / 5

Distinctiveness Conflict Risk

A clear niche — numbered-pin redline wireframes paired with a spec panel — with distinct, specific triggers and minimal realistic overlap with other skills.

5 / 5

Total

19

/

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.