CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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.

The body is an exemplary lean, well-structured skill: it assumes competence, sequences the work with explicit validation checkpoints, and cleanly offloads detail to real one-level-deep bundle files. Its only minor gap is the absence of an inline HTML snippet, which it deliberately delegates to the bundled layouts.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — it assumes Claude knows HTML/CSS and avoids explaining concepts, with a tight resource map and terse hard rules where every token earns its place.

5 / 5

Actionability

Provides concrete executable guidance (specific files to read, :root variables to swap, default rhythm table, output contract), but defers the actual HTML to the bundled layouts rather than including a copy-paste snippet in the body.

4 / 5

Workflow Clarity

A clearly sequenced Step 0–5 process with explicit validation checkpoints — the P0/P1/P2 self-check, "Every P0 item must pass before you move on", and "Stop after </artifact>" — forming a feedback loop for error recovery.

5 / 5

Progressive Disclosure

A clear overview (resource map + workflow) points to well-signaled, one-level-deep references — assets/template.html, references/layouts.md, references/checklist.md — all of which exist in the bundle and are easy to navigate.

5 / 5

Total

19

/

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 is concise, concrete, and explicit about both what the skill produces and when to use it, with natural trigger terms and a clear niche. Its only minor weakness is slightly limited synonym coverage in the trigger list.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete actions — "copying the seed assets/template.html" and "pasting section layouts from references/layouts.md" — with only minor gaps in coverage; not as comprehensive as the 5-anchor's multi-action list.

4 / 5

Completeness

Explicitly answers both 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.

5 / 5

Trigger Term Quality

Good keyword coverage with natural user-facing terms ("prototype", "mockup", "landing", "single page", "marketing page", "homepage"), but a few common variations/synonyms like "web page" or "splash page" are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — general-purpose desktop web prototype — with distinct triggers and minimal overlap risk against more specific skills.

5 / 5

Total

18

/

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
compozy/compozy
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.