CtrlK
CommunityDocumentationLog inGet started
Tessl Logo

frontend-design

tessl i github:jdrhyne/agent-skills --skill frontend-design

Expert frontend design guidelines for creating beautiful, modern UIs. Use when building landing pages, dashboards, or any user interface.

77%

Overall

SKILL.md
Review
Evals

Validation

81%
CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

license_field

'license' field is missing

Warning

Total

13

/

16

Passed

Implementation

77%

This is a solid, actionable frontend design skill with excellent concrete examples (theme CSS, CDN imports, animation micro-syntax). The workflow is clear and the content is well-structured. Main weaknesses are some unnecessary explanation of concepts Claude knows (accessibility basics, responsive design fundamentals) and all content being monolithic rather than split across files for better progressive disclosure.

Suggestions

Remove or significantly trim sections 6-8 (Responsive Design, Accessibility, Component Design Tips) as these cover concepts Claude already knows well

Consider extracting the detailed theme patterns (Dark Mode, Neo-Brutalism, Glassmorphism) into a separate THEMES.md reference file

The font list and quick reference table are valuable - keep these but trim surrounding explanatory text

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some content Claude already knows (basic accessibility principles, semantic HTML concepts, responsive design basics). The quick reference table and theme patterns are valuable, but sections 6-8 could be significantly trimmed.

2 / 3

Actionability

Provides fully executable CSS code snippets, concrete CDN imports, specific font recommendations, and copy-paste ready theme patterns. The micro-syntax for animations and the theme CSS variables are immediately usable.

3 / 3

Workflow Clarity

Clear 4-step workflow (Layout → Theme → Animation → Implementation) with each step well-defined. The ASCII wireframe example and numbered sections make the sequence unambiguous. For a design skill, validation checkpoints are less critical than for destructive operations.

3 / 3

Progressive Disclosure

Content is well-organized with clear sections and a quick reference table, but everything is inline in one file. The 150+ lines of content could benefit from splitting detailed theme patterns or component tips into separate reference files.

2 / 3

Total

10

/

12

Passed

Activation

67%

The description has good structure with an explicit 'Use when...' clause, making the trigger conditions clear. However, it lacks specific concrete actions (what the skill actually does beyond 'guidelines') and uses somewhat vague qualifiers like 'beautiful, modern' without defining specific capabilities. The trigger terms could be expanded to capture more natural user language.

Suggestions

Add specific concrete actions like 'Provides color palette selection, typography guidelines, spacing systems, and component styling patterns'

Expand trigger terms to include variations users might say: 'UI design', 'web design', 'CSS styling', 'responsive layouts', 'frontend components'

DimensionReasoningScore

Specificity

Names the domain ('frontend design guidelines', 'UIs') and mentions some outputs ('landing pages, dashboards'), but lacks concrete actions like 'create layouts', 'apply color schemes', or 'implement responsive designs'.

2 / 3

Completeness

Explicitly answers both what ('Expert frontend design guidelines for creating beautiful, modern UIs') and when ('Use when building landing pages, dashboards, or any user interface') with a clear 'Use when...' clause.

3 / 3

Trigger Term Quality

Includes some natural terms users might say ('landing pages', 'dashboards', 'user interface'), but misses common variations like 'UI design', 'web design', 'frontend styling', 'CSS', 'components', or 'responsive'.

2 / 3

Distinctiveness Conflict Risk

'Any user interface' is quite broad and could overlap with component libraries, CSS frameworks, or general web development skills. The scope is somewhat specific to frontend/UI but not narrowly defined.

2 / 3

Total

9

/

12

Passed

Reviewed

Table of Contents

ValidationImplementationActivation

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.