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

85%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 well-structured, actionable composition workflow that leans on a real, clearly-mapped bundle and includes explicit validation and feedback loops. The only room for improvement is mild tightening of the imagery rules and offering one inline completed-section example.

Suggestions

Trim the three dense imagery bullets in 'Hard rules' into tighter imperatives; the geometry-preservation guidance can be condensed without losing the key constraints.

Inline one short completed-section snippet (a filled hero, for instance) so the paste-and-fill step is fully concrete without leaving the SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence (no basic HTML/CSS explanations), and routes detail to bundled files, with only minor over-explanation in the dense imagery-handling rules that could be tightened slightly.	4 / 5
Actionability	Gives concrete, specific guidance (named files, the six :root variables, [REPLACE] tokens, paste targets in <main id="content">, P0/P1/P2 checklist gating) with a default-rhythm table covering common cases, but the actual paste-ready section blocks live in layouts.md rather than inline, leaving a minor gap.	4 / 5
Workflow Clarity	A clear Step 0 through Step 5 sequence includes an explicit validation checkpoint (Step 4 self-check where every P0 item must pass before proceeding), feedback loops (empty slot -> pick a different layout), and a referenced checklist for the complex process.	5 / 5
Progressive Disclosure	A resource-map tree signals the one-level-deep bundle clearly, all referenced paths (assets/template.html, references/layouts.md, references/checklist.md) are real files, and content is appropriately split between the overview SKILL.md, the seed, the layout library, and the checklist.	5 / 5
	Total	18 / 20 Passed

Description

78%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 conveys both purpose and trigger conditions with concrete file references and explicit deferral logic, making it highly complete and largely distinct. Its main weakness is specificity, describing one composite build action rather than a comprehensive list of distinct capabilities.

Suggestions

Broaden specificity by listing a few distinct concrete actions (e.g., 'compose sections, swap design tokens, self-review against the P0 checklist') rather than framing everything as one copy-and-paste build step.

Add one or two natural synonyms ('homepage', 'single-page site') to the description's page-type list to lift trigger-term coverage toward comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain ('General-purpose desktop web prototype') and two concrete actions ('copying the seed assets/template.html', 'pasting section layouts from references/layouts.md'), but these are sub-steps of one composite action rather than several distinct capabilities, so it is not comprehensive.	3 / 5
Completeness	Explicitly answers what ('Single self-contained HTML file built by copying the seed... and pasting section layouts') and when ('Default for any landing / marketing / docs / SaaS page when no more specific skill matches') with concrete trigger phrases, satisfying the 'Use when...' equivalent requirement.	5 / 5
Trigger Term Quality	Embeds natural page-type terms a user would say ('landing / marketing / docs / SaaS page'), giving good keyword coverage, though common synonyms like 'homepage' or 'single page' are absent from the description itself.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche as the fallback prototype skill and explicitly defers to more specific skills ('when no more specific skill matches'), but the broad span of four page types keeps minor overlap risk with specialized sibling skills.	4 / 5
	Total	16 / 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: 81044a0

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