waitlist-page

Minimal pre-launch landing with email capture, brand logo, and optional decorative layer. Reads DESIGN.md for colors, typography, and layout rules. Best for: product launches, beta signups, early access programs, indie projects.

Quality

84%

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

81%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 highly actionable, well-sequenced skill body with explicit validation feedback loops and correctly signaled one-level-deep references. Its main weakness is redundancy — the P0/P1 gate lists and the CSS variable table are restated across sections rather than kept in a single place.

Suggestions

Remove the duplicated P0/P1 gate lists from either the Workflow steps or the 'Quality gates' section, keeping them in references/checklist.md and citing that file once to eliminate the ~40 lines of repetition.

Drop or condense step 3 ('Verify token mapping rules'), since the full --variable = {{TOKEN}} mapping is already implied by the inputs and the step-2 replacement rules.

Move the decorative-restraint and typographic-discipline details into the checklist or template comments so the SKILL.md body stays a lean overview pointing to the bundle files.

Dimension	Reasoning	Score
Conciseness	Mostly operational and free of explaining concepts Claude already knows, but the P0/P1 gate lists are duplicated between the Workflow steps and the 'Quality gates' section, and step 3 restates every CSS variable already defined in the inputs — clear tightening opportunities.	3 / 5
Actionability	Provides fully executable guidance: exact token-mapping rules, an explicit color grammar with a precise unsafe-character reject list (';', '{}', '<', '>', '/*', '@', 'url('), specific viewport sizes (375x667, 390x844), and exact attributes (role="status", checkValidity()).	5 / 5
Workflow Clarity	Clear sequence (Preflight -> token replacement -> responsive check -> validation -> emit) with explicit validation checkpoints ('Pass P0 or do not emit'), a real referenced checklist (references/checklist.md), and a post-emission feedback loop to re-run P0 gates on iterations.	5 / 5
Progressive Disclosure	Structure is good: SKILL.md points one level deep to assets/template.html (the artifact) and references/checklist.md (the gates), both verified to exist. Held below 5 because the P0/P1 gate content is inlined in the body AND duplicated in checklist.md rather than being solely deferred to the reference.	4 / 5
	Total	17 / 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.

A strong, concrete description that clearly states what the skill builds and when to use it, with a distinct niche and natural trigger phrasing. The only gap is that a few common user synonyms (waitlist, coming soon) live in the triggers field rather than the description body itself.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities — 'email capture, brand logo, and optional decorative layer' and 'Reads DESIGN.md for colors, typography, and layout rules' — with only minor gaps in coverage; not a 5 because it omits the templated/hardened validation workflow.	4 / 5
Completeness	Explicitly answers both what ('Minimal pre-launch landing with email capture...') and when ('Best for: product launches, beta signups...') with concrete trigger phrases, satisfying the equivalent of a 'Use when' clause.	5 / 5
Trigger Term Quality	The 'Best for: product launches, beta signups, early access programs, indie projects' line plus 'pre-launch landing' gives good natural keyword coverage, but within the description field itself it omits common variations users say like 'waitlist' or 'coming soon page'.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (pre-launch waitlist/landing pages with DESIGN.md-driven theming) with distinct triggers, making conflict with unrelated skills minimal.	5 / 5
	Total	18 / 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/waitlist-page/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.