CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tailwindcss

Use when designing/implementing UI with Tailwind CSS (layout, typography, responsive, theming, component patterns). Includes quick recipes and conventions for clean, consistent web design.

Quality

80%

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 ./agent-skills/web-design/tailwindcss/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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-organized, example-driven reference with executable recipes, real-world pitfalls, and a useful user-question checklist. Its main weakness is the Key concepts section restating Tailwind basics (variant and arbitrary-value syntax) that Claude already knows, which spends tokens without adding value; the rest of the body is tight and actionable.

Suggestions

Cut or compress the 'Key concepts & patterns' entries that restate Tailwind documentation Claude already knows (responsive variant prefixes sm:/md:/lg:, state variants hover:/focus:/active:, arbitrary value syntax) — keep only the skill's own conventions such as 'prefer components first, then @apply' and 'use arbitrary values sparingly'.

Replace generic variant listings with non-obvious guidance, e.g. when to reach for group-hover/peer-checked patterns vs. component state, or how the content-scanning build pipeline affects class emission decisions.

Anchor the pitfalls with a one-line fix each where missing (e.g. 'conflicting styles due to class order' could note that CSS specificity, not class-list order, wins and to use conflicting-pairs utilities or restructure).

DimensionReasoningScore

Conciseness

The body is list-based and compact, but 'Responsive variants: sm: md: lg: xl:', 'State variants: hover:, focus:, active:', and arbitrary-value syntax are Tailwind fundamentals Claude already knows — unnecessary re-explanation. Fits anchor 3 ('mostly efficient but includes some unnecessary explanation'); too much known-material restatement for anchor 4, but far from the padded verbosity of anchor 2.

3 / 5

Actionability

Three copy-paste-ready examples (CTA button, responsive hero grid, tone-class mapping) plus concrete pitfall fixes ('Avoid building class names dynamically... unless safelisted', 'use clsx/cva when needed'). Anchor 4 fits: mostly executable with minor gaps; not 5 because supporting details like content-glob configuration are alluded to but not shown.

4 / 5

Workflow Clarity

This is a conventions/reference skill rather than a sequential process, so no destructive-operation validation is required; the organization (concepts → pitfalls → recipes → 'What to ask the user') is coherent and the upfront question list acts as a practical checkpoint. Matches anchor 4 — clear guidance with only minor gaps, short of anchor 5's explicit multi-step sequence with feedback loops.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed: the ~74-line body is cleanly sectioned (When to use, Key concepts, Pitfalls, Recipes, Questions) with everything appropriately inline and scannable. Per the simple-skill guidance, well-organized sections with no need for external references warrant anchor 5.

5 / 5

Total

16

/

20

Passed

Description

78%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 with an explicit 'Use when...' trigger clause naming the Tailwind CSS niche and its sub-areas (layout, typography, responsive, theming, component patterns), plus a statement of what the skill contains. The 'what' half leans on describing bundle contents ('includes quick recipes and conventions') rather than concrete capability verbs, keeping it just below top marks.

DimensionReasoningScore

Specificity

Names the domain ('Tailwind CSS') and enumerates several specific capability areas ('layout, typography, responsive, theming, component patterns') plus what it provides ('quick recipes and conventions'). It falls short of anchor 5 because 'designing/implementing UI' is a generic action phrase rather than the concrete verbs of the top anchor, but exceeds anchor 3's 1-2 concrete actions.

4 / 5

Completeness

Both halves are present: an explicit 'Use when designing/implementing UI with Tailwind CSS...' clause with concrete trigger areas, and a 'what' ('Includes quick recipes and conventions for clean, consistent web design'). Not anchor 5 because the 'what' describes the bundle's contents rather than stating capabilities as directly as the anchor-5 example; well above anchor 3 since the 'when' is fully explicit.

4 / 5

Trigger Term Quality

Good coverage of natural terms a user would say — 'Tailwind CSS', 'UI', 'layout', 'typography', 'responsive', 'theming', 'web design'. Not anchor 5 because common variations like 'styling', 'CSS classes', or 'dark mode' are missing, but it clearly exceeds anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

'Tailwind CSS' is a clear, named niche with distinct triggers; it would not fire for other styling or general web-design skills. Matches anchor 5's clear-niche, minimal-conflict profile.

5 / 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

MengTo/Skills

Path

agent-skills/web-design/tailwindcss/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.