CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frontend-business-websites

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

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 well-sequenced, highly actionable workflow with explicit validation checkpoints and honest completion-state reporting — the strongest aspects of the body. Its weaknesses are token efficiency (motivational prose and repeated honesty caveats) and progressive disclosure: the domain sub-workflow is inlined rather than split out, and the bundled enquiry-form asset is never referenced.

Suggestions

Move the section 6 domain workflow (offer script, five API steps, CLI commands) into a references/domain-setup.md file and keep a short trigger summary in SKILL.md so the main build workflow stays lean.

Reference the existing assets/enquiry-form.html from the enquiry-form bullet in section 3 instead of (or alongside) the external URL, so the bundled example is actually discoverable.

Trim the motivational prose ("Most first sites fail in the same places…", "A business site gets shared on cards…") and consolidate the honesty rules stated in sections 1, 3, 6 and 7 into one place to reduce repetition.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no basic web explanations) but includes motivation prose ("Most first sites fail in the same places…", "A business site gets shared on cards, menus, QR codes, Google Maps and Instagram bios, so the address matters on day one") and repeats honesty rules across sections 1, 3, 6 and 7. Matches "mostly efficient but… could be tightened"; not 4 because the padding is more than minor, not 2 because there is no basic-concept teaching.

3 / 5

Actionability

Concrete, executable guidance throughout: "Tap targets at least 44 px", "contrast at least 4.5:1 for text", "og:image (1200x630)", `npx github:vitaliiphangan-code/adddomain-cli find <name>`, and exact API endpoints like `GET https://www.adddomain.net/api/check?name=<label>&tlds=com,net&src=github`. Not 5 because the enquiry-form path delegates its worked example to an external URL rather than inline or bundle content; not 3 since commands and specs are copy-paste ready.

4 / 5

Workflow Clarity

A clearly sequenced 8-step workflow (Brief → Plan → Build → Craft → Found/shared → Address → Done checks → Handover) with an explicit validation checklist in section 7 ("Check and report each separately, honestly") and verification gates such as "Check the address and HTTPS before saying it works" and "show success only when that service confirms acceptance". Matches the top anchor with checkpoints and honest-state reporting; not 4 because validation is explicit at every risky stage.

5 / 5

Progressive Disclosure

Section headers are clear, but the ~117-line body inlines a ~25-line domain-purchase sub-workflow with five API steps (section 6) that belongs in a separate reference file, and the bundle's assets/enquiry-form.html is never referenced in the body — the example instead points to an external URL, leaving the local asset undiscoverable. Matches "content that should be separate is inline"; not 4 due to the orphaned asset, not 2 because the section structure and signaling are otherwise reasonable.

3 / 5

Total

15

/

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: third-person voice, concrete capability list spanning build, accessibility, SEO, launch and handover, with an explicit "Use for…" trigger clause. Keyword coverage is good though a few natural synonyms (homepage, web page) are absent, and the web-app/design-skill broadening introduces minor conflict risk with neighboring skills.

DimensionReasoningScore

Specificity

Quotes "Design and build a responsive frontend website or accessible landing page", "HTML and CSS layout in the existing stack", "visual typography and accessibility checks", "SEO and share previews, public launch and owner handover" — multiple specific concrete actions with comprehensive coverage of the domain (menus, shops, bookings, portfolios, forms, web app interfaces). Not 4 because coverage extends across design, build, launch and handover with no significant gaps.

5 / 5

Completeness

Explicitly answers "what" ("Design and build a responsive frontend website or accessible landing page for a small business or creator…") and "when" with a concrete trigger clause: "Use for requests to build a website, make a business site or landing page, or complement a visual design skill…". Matches the top anchor; not 4 because the when-guidance is explicit rather than merely present.

5 / 5

Trigger Term Quality

Quotes "build a website", "make a business site or landing page" — natural phrases a user would say. Not 5 because common variations such as "homepage", "web page" or "site for my shop/restaurant" are missing; not 3 since the core natural trigger phrasings are explicitly present.

4 / 5

Distinctiveness Conflict Risk

The small-business/creator public-site niche is mostly distinct, but "public web app interfaces" and "complement a visual design skill" create minor overlap with general frontend-development and visual-design skills. Not 5 because of that overlap risk; not 3 because the core triggers (business site, landing page) are clearly distinct from adjacent skills.

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

skills/frontend-business-websites/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.