web-prototype

General-purpose desktop web prototype. Single self-contained HTML file built by copying the seed `assets/template.html` and pasting section layouts from `references/layouts.md`. Default for any landing / marketing / docs / SaaS page when no more specific skill matches.

Quality

81%

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

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.

The body is a tight, well-structured overview that points cleanly to three real bundle files and lays out a sequenced workflow with an explicit P0 self-check gate. Its only gap is the absence of inline code examples, since the executable material lives entirely in the referenced files.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive throughout — 'Produce a single, self-contained HTML prototype... not by writing CSS from scratch', a compact resource map, and terse numbered steps — with no padding or explanation of concepts Claude already knows, matching the 'every token earns its place' anchor.	5 / 5
Actionability	Guidance is concrete and specific — 'copy the <section> block from layouts.md into <main id="content">', 'Replace the six :root variables', named classes like .ph-img and data-od-id — but the body itself contains no inline copy-paste code (the executable skeletons live in the referenced layouts.md), so it sits just below the fully copy-paste-ready 5 anchor.	4 / 5
Workflow Clarity	A clear six-step sequence (Step 0 pre-flight through Step 5 write) with an explicit validation gate — 'Run through references/checklist.md top to bottom. Every P0 item must pass before you move on' — plus a cheap user redirect checkpoint in Step 2, matching the explicit-checklist/feedback-loop 5 anchor.	5 / 5
Progressive Disclosure	The body is a clear overview with a resource map and well-signaled, one-level-deep references — assets/template.html, references/layouts.md, references/checklist.md — all of which are real files, with content appropriately split across them, matching the 'easy navigation' 5 anchor.	5 / 5
	Total	19 / 20 Passed

Description

70%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 states what the skill produces and gives an explicit (if fallback-framed) when clause with concrete page-type triggers, all in third person. It is strong on trigger coverage and distinctiveness but lists only two concrete actions, limiting specificity.

Suggestions

Add one or two more concrete actions (e.g., 'swaps design tokens', 'self-checks against a P0/P1/P2 checklist') to lift specificity toward the 5 anchor.

Reframe the 'when' as an explicit 'Use when...' clause naming user-facing trigger phrases (e.g., 'Use when the user asks for a landing page, marketing site, or single-page mockup') to reach the completeness 5 anchor.

Fold a natural synonym or two currently only in the triggers field (e.g., 'mockup', 'homepage') into the description prose to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions — 'copying the seed assets/template.html' and 'pasting section layouts from references/layouts.md' — but the action list is not comprehensive, matching the '1-2 concrete actions' anchor rather than the multi-action 4/5 anchors.	3 / 5
Completeness	Both 'what' (a single self-contained HTML prototype built from the seed and layout library) and 'when' ('Default for any landing / marketing / docs / SaaS page when no more specific skill matches') are present; the 'when' is explicit but phrased as a fallback/default rule rather than crisp 'Use when the user mentions X' trigger phrases, so it sits just below the 5 anchor.	4 / 5
Trigger Term Quality	The description surfaces natural page-type terms users say — 'landing / marketing / docs / SaaS page' plus 'web prototype' and 'HTML' — giving good coverage, though common synonyms like 'homepage' or 'mockup' (present only in the separate triggers field) are absent from the description itself.	4 / 5
Distinctiveness Conflict Risk	The niche is clear — desktop, single self-contained HTML prototypes — and the 'when no more specific skill matches' clause explicitly defers to more specific skills, reducing conflict; minor overlap risk remains with other web/design skills due to the 'general-purpose' framing, keeping it just below 5.	4 / 5
	Total	15 / 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: design-templates/web-prototype/SKILL.md
Commit: 1a7a23d

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