CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tailwindcss-development

Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS.

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 tight, well-organized reference skill that concentrates on genuinely non-obvious knowledge (Tailwind v4 migration specifics, CSS-first configuration) with executable examples throughout. Its main weaknesses are minor: a few redundant labels and basic examples Claude already knows, and no separation of reference material into bundle files.

Suggestions

Remove the redundant HTML comments that restate section headings (e.g., '<!-- Flexbox Layout -->' under '### Flexbox Layout'), since they duplicate the visible structure and spend tokens without adding information.

Trim or cut the 'Common Patterns' flex/grid examples — Claude already knows basic flexbox and grid layout — and keep only project-specific conventions or non-obvious patterns.

Consider moving the full deprecated-utility replacement table and detailed v4 migration notes into a references/ file (e.g., v4-migration.md), keeping SKILL.md to the highest-frequency guidance and a one-level-deep pointer.

DimensionReasoningScore

Conciseness

The high-value non-obvious material (the deprecated-utility replacement table, @theme config, @import syntax) is delivered efficiently, but there is minor padding: redundant HTML comments restating each section heading ('<!-- Flexbox Layout -->' under '### Flexbox Layout') and basic flex/grid pattern examples Claude already knows. Not 5 because of these trimmable spots; not 3 because over-explanation is isolated and minor.

4 / 5

Actionability

Fully executable, copy-paste-ready snippets for @theme configuration, the v3→v4 import diff, gap utilities, dark mode variants, and flex/grid layouts, plus an exact deprecated→replacement utility mapping table that covers the common cases.

5 / 5

Workflow Clarity

This is a styling-reference skill with no multi-step process or destructive/batch operations (so no validation cap applies). 'Basic Usage' gives a coherent implicit order — check existing conventions before introducing patterns, offer component extraction, tidy class placement — but the sequencing stays implicit rather than an unambiguous single action. Not 5 for that implicitness; not 3 because nothing is missing or incoherent.

4 / 5

Progressive Disclosure

No bundle files exist, so everything lives in SKILL.md; sections are well-organized and the only external pointer ('Use search-docs for detailed Tailwind CSS v4 patterns') targets a tool, not a nested file reference. Not 5 because the body exceeds the under-50-line simple-skill threshold and some reference-style material (e.g., the full replacement table, common patterns) could sit in a separate file; not 3 because structure is good and nothing is buried.

4 / 5

Total

17

/

20

Passed

Description

100%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.

An exemplary description: explicit invocation trigger, concrete capability list, a clearly stated core use case, and a skip list that disambiguates it from adjacent skills. Every clause is functional trigger or scope information rather than fluff.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'building responsive grid layouts (multi-column card grids, product grids)', 'adding dark mode variants', 'fixing spacing or typography' — and states the core use case ('writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue)'), giving comprehensive coverage rather than the minor gaps of a 4.

5 / 5

Completeness

Explicitly answers both questions: 'when' via 'Always invoke when the user's message includes tailwind in any form. Also invoke for: ...' and 'what' via the core use case statement, going beyond the anchor with an explicit skip list.

5 / 5

Trigger Term Quality

Comprehensive natural terms users would actually say: 'tailwind' in any form, 'dark mode', 'spacing', 'typography', 'dashboard', 'pricing sections', plus framework names (Blade, JSX, Vue) and version markers (v3/v4).

5 / 5

Distinctiveness Conflict Risk

Clear niche anchored on the 'tailwind' trigger; the explicit skip list ('Skip for backend PHP logic, ... vanilla CSS') resolves the only plausible overlap (generic CSS or frontend styling skills), minimizing conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

yaojingang/GEOFlow

Path

.agents/skills/tailwindcss-development/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.