CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-design

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

49

Quality

53%

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
SKILL.md
Quality
Evals
Security

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-organized and offers concrete aesthetic guidance, but it leans on inspirational padding, lacks executable code examples, and presents only a loose workflow without validation checkpoints. Progressive disclosure is appropriate for a single-file skill.

Suggestions

Trim motivational filler (e.g. the closing "Remember: Claude is capable of extraordinary creative work..." and "There are so many flavors to choose from.") to improve token efficiency.

Add at least one copy-paste-ready example, such as a CSS-variables palette block or a staggered animation-delay snippet, to lift actionability.

Make the workflow explicit with numbered steps and a lightweight verification checkpoint (e.g. review the result against the chosen aesthetic direction before finalizing).

DimensionReasoningScore

Conciseness

The body gives useful concrete directives but includes motivational padding ("Remember: Claude is capable of extraordinary creative work. Don't hold back...") and some repeated guidance, so it is mostly efficient but could be tightened.

2 / 3

Actionability

It lists specific, actionable techniques (CSS variables, animation-delay, Motion library, gradient meshes, grain overlays) but provides no executable code example and mixes in abstract directives like "Create atmosphere and depth", fitting level 2.

2 / 3

Workflow Clarity

A two-phase sequence (Design Thinking: Purpose/Tone/Constraints/Differentiation, then implement) is present, but there are no explicit checkpoints or feedback loops, so it stays at level 2.

2 / 3

Progressive Disclosure

The skill is a single self-contained SKILL.md with no bundle files and is organized into clear sections (Design Thinking, Frontend Aesthetics Guidelines), which per the simple-skills note merits a 3.

3 / 3

Total

9

/

12

Passed

Description

50%

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 is terse and on-domain but stops at naming artifacts rather than actions and omits any explicit use-when trigger guidance. It is adequate but not comprehensive or trigger-rich.

Suggestions

Add concrete actions, e.g. "Build and design frontend UI: pages, apps, and components with polished, non-generic aesthetics."

Append a Use-when clause naming natural triggers, e.g. "Use when building web pages, landing pages, dashboards, UI components, or mockups that need distinctive design."

Include more natural keyword variations users actually say (landing page, dashboard, web app, mockup, prototype) to improve trigger coverage.

DimensionReasoningScore

Specificity

"Frontend UI: pages, apps, components, polished non-generic design" names the domain and concrete artifact types but lists no concrete actions (build, design, scaffold), matching the level-2 anchor rather than the multi-action level-3.

2 / 3

Completeness

It states what the skill produces but has no "Use when..." trigger clause, so per the guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Natural terms like "Frontend", "UI", "pages", "apps", "components" are present, but common variations users say (landing page, dashboard, mockup, web app) are missing, fitting level 2.

2 / 3

Distinctiveness Conflict Risk

"Frontend UI" is a recognizable niche sharpened by "polished non-generic design", but it could still overlap with a general web-development skill, so it is not a clear level-3 niche.

2 / 3

Total

8

/

12

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.