CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

80

0.98x
Quality

84%

Does it follow best practices?

Impact

66%

0.98x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 efficient, well-structured instructional skill that gives concrete, opinionated design guidance with named techniques and explicit anti-patterns rather than generic advice. Its think-then-implement flow is clear, and its length and organization are appropriate for a self-contained skill with no external references. Remaining gains are minor: trimming motivational filler and adding one or two worked examples.

DimensionReasoningScore

Conciseness

The body is a tight, well-budgeted set of bullets that adds design guidance Claude would not reliably produce on its own (specific aesthetic directions, named anti-patterns like "Inter, Roboto, Arial" and "purple gradients on white backgrounds", and named techniques like "animation-delay", "gradient meshes, noise textures... grain overlays"). A few trimmable instances remain — filler such as "There are so many flavors to choose from" and the motivational closing "Remember: Claude is capable of extraordinary creative work. Don't hold back..." — placing it at score 4 rather than the every-token-earns-its-place level of 5.

4 / 5

Actionability

For an instruction-only skill, the guidance is concrete and specific: named aesthetic categories to choose from, concrete techniques ("Pair a distinctive display font with a refined body font", "CSS variables", "staggered reveals (animation-delay)", "Use Motion library for React when available"), and explicit prohibitions. It stops short of score 5 because there are no worked examples (e.g., a sample font pairing or CSS snippet) demonstrating the guidance in practice, but it is far above the high-level-hints level of score 2 or pseudocode-level score 3.

4 / 5

Workflow Clarity

A clear two-phase sequence is present: a "Design Thinking" step (purpose, tone, constraints, differentiation) followed by "Then implement working code" with a checklist of outcome qualities. The skill is simple and involves no destructive or batch operations, so no validation checkpoints are required; it falls short of 5 only because the sequence is implicit (section order) rather than explicitly enumerated steps.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (no references/, scripts/, or assets/ exist) and no content that warrants external files. Per the rubric's simple-skill guidance, well-organized sections alone justify a 5: the body is cleanly split into "Design Thinking" and "Frontend Aesthetics Guidelines" with coherent subsections by concern (Typography, Color & Theme, Motion, Spatial Composition, Backgrounds & Visual Details).

5 / 5

Total

17

/

20

Passed

Description

83%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 that explicitly covers what the skill does and when to use it, with natural, varied trigger terms and a clearly differentiated niche. The only weakness is that the action vocabulary is slightly repetitive (create/generate/style) and a few common user phrasings are absent, leaving trigger coverage just short of comprehensive.

DimensionReasoningScore

Specificity

The description states concrete actions in third person ("Create distinctive, production-grade frontend interfaces", "Generates creative, polished code and UI design", "styling/beautifying any web UI") and enumerates a broad range of concrete objects ("websites, landing pages, dashboards, React components, HTML/CSS layouts, posters"). It falls just short of the score-5 anchor because the distinct verbs are few (create/generate/style) and some coverage relies on examples rather than enumerated actions, but it is well above the 1-2 concrete-actions level of score 3.

4 / 5

Completeness

It explicitly answers both questions: what ("Create distinctive, production-grade frontend interfaces... Generates creative, polished code and UI design that avoids generic AI aesthetics") and when ("Use this skill when the user asks to build web components, pages, artifacts, posters, or applications... or when styling/beautifying any web UI"). This mirrors the score-5 anchor example's structure of a concrete capability statement followed by an explicit 'Use when...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases are well covered: "build web components, pages, artifacts, posters, or applications", "websites, landing pages, dashboards, React components", and "styling/beautifying any web UI" — phrasing a user would genuinely say. A few natural synonyms are missing (e.g., "redesign", "make it look better", "frontend"), keeping it below the comprehensive score-5 anchor but comfortably above score 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

The niche (high-design-quality frontend/UI creation) is clearly staked out with distinct triggers tied to building and styling web interfaces, and its anti-generic positioning further differentiates it. Minor overlap risk remains with closely related skills (e.g., dashboard-building could also match a data-visualization skill; "styling/beautifying any web UI" is broad), so it sits at score 4 rather than the minimal-conflict score 5.

4 / 5

Total

17

/

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

databricks/devhub

Path

.agents/skills/frontend-design/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.