CtrlK
BlogDocsLog inGet started
Tessl Logo

tailwind-design-system

Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.

88

1.13x
Quality

82%

Does it follow best practices?

Impact

100%

1.13x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is tailwind-design-system in wshobson/agents

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

Highly actionable with excellent executable code, but the body is a monolithic ~860-line file with no progressive disclosure, and the migration workflow lacks validation checkpoints. Tightening length and splitting reference material would lift the weaker dimensions.

Suggestions

Move the full component implementations (Card, Dialog, ThemeProvider, etc.) and 'Advanced v4 Patterns' into a separate references file referenced one level deep from SKILL.md to improve progressive disclosure.

Add explicit validation steps to the v3→v4 migration checklist (e.g., 'run the build and verify no @tailwind/forwardRef errors remain before proceeding') to introduce feedback loops.

Trim the inline theme token blocks by showing a representative subset plus a pointer to a complete token reference, reducing the token footprint while keeping the core pattern clear.

DimensionReasoningScore

Conciseness

The body is mostly executable code with little prose padding, but at ~860 lines it inlines full implementations of many components (Button, Card with 6 sub-components, Input, Grid, ThemeProvider, etc.) that could be tightened or moved to references.

2 / 3

Actionability

Provides complete, copy-paste-ready TypeScript/CSS examples with imports, variant definitions, and usage snippets — fully executable rather than pseudocode.

3 / 3

Workflow Clarity

The v3→v4 migration checklist sequences steps, but it lacks validation checkpoints or feedback loops for a potentially destructive migration; the rest is parallel patterns rather than a validated workflow.

2 / 3

Progressive Disclosure

No bundle files exist and everything lives in one monolithic SKILL.md; sections are well-organized, but the advanced patterns and full component reference could be split into clearly signaled one-level-deep reference files.

2 / 3

Total

9

/

12

Passed

Description

100%

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: third-person voice, concrete capabilities, explicit 'Use when' trigger guidance, and a clear niche. It earns full marks across all four dimensions with no over-claims or fluff.

DimensionReasoningScore

Specificity

Names multiple concrete capabilities — "design tokens, component libraries, and responsive patterns" — rather than vague abstractions, matching the top anchor.

3 / 3

Completeness

Explicitly answers both what ("Build scalable design systems with...") and when ("Use when creating component libraries, implementing design systems, or standardizing UI patterns").

3 / 3

Trigger Term Quality

Includes natural terms users would say — "component libraries", "design systems", "design tokens", "UI patterns" — with good coverage and no jargon-only phrasing.

3 / 3

Distinctiveness Conflict Risk

Scoped to "Tailwind CSS v4" design systems with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (867 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
calesthio/OpenMontage
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.