CtrlK
BlogDocsLog inGet started
Tessl Logo

tailwind-patterns

Quick reference for Tailwind CSS utility patterns, responsive design, and configuration. Triggers on: tailwind, utility classes, responsive design, tailwind config, dark mode css, tw classes.

92

1.56x
Quality

Does it follow best practices?

Impact

89%

1.56x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

The body is an efficient, actionable Tailwind cheat sheet with strong conciseness and copy-paste examples. Its single gap is a broken reference to a missing ./references/component-patterns.md file.

Suggestions

Create ./references/component-patterns.md (Navbar, cards, forms, alerts, loading states) so the referenced 'Additional Resources' file actually exists, or remove the dead reference.

Close or annotate the snippet divs in 'Common Layout Patterns' so each example is complete and unambiguous.

DimensionReasoningScore

Conciseness

The body is lean tables and code snippets with almost no prose, assuming Claude already knows what Tailwind is and not padding with explanation.

3 / 3

Actionability

It provides concrete, copy-paste-ready HTML class combinations and config snippets (card, button, form input, dark mode) rather than abstract direction.

3 / 3

Workflow Clarity

This is a simple single-purpose reference skill whose content is organized into clear, unambiguous sections, which the rubric allows to score 3 without a multi-step workflow.

3 / 3

Progressive Disclosure

Sections are well organized and a reference is clearly signaled ('For detailed patterns, load: ./references/component-patterns.md'), but that referenced file does not exist, so the one-level-deep reference is a dead link.

2 / 3

Total

11

/

12

Passed

Description

90%

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 concise, in third person, and clearly communicates both purpose and trigger conditions with strong natural keywords. Its only weakness is that it describes a reference scope rather than enumerating concrete actions.

DimensionReasoningScore

Specificity

It names the domain and some actions ('Quick reference for Tailwind CSS utility patterns, responsive design, and configuration'), but as a reference skill it does not list multiple concrete actions like the score-3 anchor.

2 / 3

Completeness

It states what it does (quick reference for patterns/responsive/config) and provides equivalent explicit trigger guidance via 'Triggers on:', answering both what and when.

3 / 3

Trigger Term Quality

'Triggers on: tailwind, utility classes, responsive design, tailwind config, dark mode css, tw classes' gives good coverage of natural terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Tailwind-specific triggers and a clear CSS-utility niche make it unlikely to fire for the wrong skill.

3 / 3

Total

11

/

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
NeverSight/skills_feed
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.