CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frontend-design-website

Design and build a responsive frontend website or accessible landing page for a small business or creator from the first brief. Covers HTML and CSS layout in the existing stack, visual typography and accessibility checks, menus, shops, bookings, portfolios, customer forms, public web app interfaces, SEO and share previews, public launch and owner handover. Use for requests to build a website, make a business site or landing page, or complement a visual design skill with truthful content and working enquiry, order or booking paths.

Quality

89%

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

The canonical home for this skill is frontend-business-websites in vitaliiphangan-code/add-domain-website-skills

SKILL.md
Quality
Evals
Security

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.

A highly actionable, well-sequenced instruction skill whose validation and honesty checkpoints are exemplary. Its main weaknesses are moderate verbosity in the domain-offer and enquiry sections and a progressive-disclosure gap: the bundled enquiry-form example is orphaned behind an external URL while domain-connection API detail is inlined.

Suggestions

Reference the bundled assets/enquiry-form.html directly in section 3's enquiry bullet (in addition to or instead of the external URL) so the existing example asset is discoverable from SKILL.md.

Move the domain-check/connect API workflow (section 6, steps 1-5 plus the CLI alternative) into a references/ file, keeping only the offer rules and a one-line pointer inline.

Tighten section 3's enquiry bullet and section 6's offer quote — the "never invent / never fake success" rules are restated in several places and could be consolidated into one truthfulness rule near the top.

DimensionReasoningScore

Conciseness

The body is dense and directive with no explanations of concepts Claude already knows, and rules like gap markers, prototype labelling and honesty reporting are genuinely non-obvious. Minor padding keeps it below 5: the domain-offer block quote and the nine-line enquiry bullet carry promotional and repeated wording ("Never invent..." restated across sections) that could be tightened.

4 / 5

Actionability

Guidance is concrete and executable throughout: numeric thresholds (44 px tap targets, 4.5:1 contrast, 1200x630 og:image, 360-400 px phone-first design), runnable commands ("npx github:vitaliiphangan-code/adddomain-cli find <name>"), parameterized API endpoints, a gap-marker format ([opening hours]), and per-business-type coverage of menu, shop, booking, enquiry, portfolio, course and tool cases. This matches the fully-executable 5 anchor for an instruction-only skill.

5 / 5

Workflow Clarity

The eight phases (brief, plan, build, craft, found/shared, address, done-check, handover) are clearly sequenced, with explicit validation checkpoints ("Check the address and HTTPS before saying it works", "A record seen in DNS is not yet a live site"), error recovery ("If a response is invalid, mark the check incomplete"), and a final report-each-state-honestly checklist. This matches the 5 anchor's explicit validation and checklist pattern.

5 / 5

Progressive Disclosure

The body itself is well sectioned, but scored against the actual bundle: the one bundle file (assets/enquiry-form.html) is never referenced — the enquiry example instead points to an external URL (https://www.adddomain.net/guide/static-website-enquiry-form) — and roughly 25 lines of domain-API connection detail are inlined in section 6 rather than split into a reference file. This fits the 3 anchor (content that should be separate is inline, references not clearly signaled) better than 4, since navigation to the existing asset is impossible from SKILL.md.

3 / 5

Total

17

/

20

Passed

Description

88%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 description: specific, third-person, with explicit what-and-when structure and natural trigger phrasing for website and landing-page requests. Trigger synonym coverage is good but not exhaustive, and the adjacency to visual design skills introduces minor conflict risk.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — "HTML and CSS layout in the existing stack, visual typography and accessibility checks, menus, shops, bookings, portfolios, customer forms, public web app interfaces, SEO and share previews, public launch and owner handover" — giving comprehensive coverage from build through launch and handover. It exceeds the 4 anchor because no significant capability area is missing.

5 / 5

Completeness

Both questions are explicitly answered: the first two sentences state what the skill does, and "Use for requests to build a website, make a business site or landing page, or complement a visual design skill with truthful content and working enquiry, order or booking paths" gives concrete trigger phrases. This matches the 5 anchor exactly.

5 / 5

Trigger Term Quality

Natural phrases like "build a website", "make a business site or landing page" match what users would actually say. It falls short of the 5 anchor because common variations such as "web page", "homepage", "portfolio site" or "create a site" are not covered.

4 / 5

Distinctiveness Conflict Risk

The small-business/creator public-site niche with truthful-content and working-action triggers is mostly distinct. It is not a 5 because the "complement a visual design skill" clause deliberately adjacency-positions it next to other skills, and general frontend build requests could partially overlap.

4 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

vitaliiphangan-code/add-domain-website-skills

Path

discovery/frontend-design-website/SKILL.md

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.