CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-design

Frontend UI: pages, apps, components, polished non-generic design.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/frontend-design/SKILL.md

The canonical home for this skill is frontend-design in anthropics/skills

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 content delivers concrete, well-organized aesthetic guidance with a clear think-then-build workflow and appropriate structure for a self-contained skill, held back only by minor motivational padding and the absence of executable code templates.

DimensionReasoningScore

Conciseness

The body is mostly lean, skill-specific aesthetic guidance (typography, color, motion, spatial, backgrounds) with only minor motivational padding at the opening and closing that could be trimmed.

4 / 5

Actionability

Provides concrete directives — named fonts to avoid (Arial, Inter), CSS variables, Motion library for React, and specific techniques (gradient meshes, noise textures) — which is actionable for an instruction-only skill, though no copy-paste code templates are included.

4 / 5

Workflow Clarity

A clear think-then-implement sequence is present with a design-thinking pre-checklist (Purpose, Tone, Constraints, Differentiation); output validation is absent but appropriate for non-destructive creative work.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into well-signaled sections (Design Thinking, Frontend Aesthetics Guidelines), meeting the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

61%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 clearly declares its domain and a distinguishing quality, but omits any 'when to use' trigger guidance and lacks action verbs, leaving it moderately specific rather than fully complete.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when building web pages, apps, or UI components that need a polished, non-generic aesthetic').

Replace noun-only categories with action verbs (e.g., 'Builds frontend UI: pages, apps, and components with polished, non-generic design').

Include common synonyms users say (website, interface, dashboard, landing page) to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain and concrete artifact categories ('pages, apps, components') plus a quality descriptor ('polished non-generic design'), but uses no action verbs, so coverage of concrete actions is limited rather than comprehensive.

3 / 5

Completeness

The 'what' is clear, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('Frontend UI', 'pages', 'apps', 'components', 'design'), though common synonyms like 'website', 'interface', or 'dashboard' are missing.

4 / 5

Distinctiveness Conflict Risk

The 'polished non-generic design' qualifier carves a distinct niche away from generic web-development skills, leaving only minor overlap risk with closely related UI skills.

4 / 5

Total

14

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
steipete/agent-scripts
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.