tailwind-class-optimizer
Tailwind Class Optimizer - Auto-activating skill for Frontend Development. Triggers on: tailwind class optimizer, tailwind class optimizer Part of the Frontend Development skill category.
35
3%
Does it follow best practices?
Impact
93%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/05-frontend-dev/tailwind-class-optimizer/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a title and category label with no substantive content. It fails to describe what the skill actually does, provides no natural trigger terms beyond the skill name repeated, and lacks any 'Use when...' guidance. It would be nearly impossible for Claude to reliably select this skill from a pool of similar frontend development skills.
Suggestions
Add concrete actions the skill performs, e.g., 'Deduplicates, sorts, and merges Tailwind CSS utility classes; resolves conflicting utilities; converts long class lists into cleaner equivalents.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about cleaning up Tailwind classes, removing duplicate utilities, sorting className strings, or optimizing utility-first CSS.'
Include common file/term variations users might mention, such as 'className', 'class attribute', 'tw-merge', 'clsx', 'tailwind.config', or '.tsx/.jsx files with utility classes'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Tailwind Class Optimizer') and its category ('Frontend Development') but does not describe any concrete actions like merging classes, removing duplicates, sorting utilities, or resolving conflicts. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explanation of capabilities and no explicit 'Use when...' clause with trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('tailwind class optimizer, tailwind class optimizer'). It lacks natural user terms like 'tailwind classes', 'CSS utilities', 'class cleanup', 'duplicate classes', 'utility-first CSS', or 'className optimization'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Tailwind' provides some domain specificity that distinguishes it from generic CSS or frontend skills, but without describing what optimization actions it performs, it could still overlap with other Tailwind-related or CSS cleanup skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual content. It repeatedly references 'tailwind class optimizer' without ever explaining what Tailwind class optimization entails, providing any code examples, listing specific techniques (e.g., class merging, purging, sorting), or offering any actionable guidance. It would provide zero value to Claude in performing any real task.
Suggestions
Add concrete, executable code examples showing Tailwind class optimization techniques (e.g., using tailwind-merge to deduplicate conflicting classes, clsx/cn utility patterns, PurgeCSS configuration).
Define a clear workflow: e.g., 1) Identify redundant/conflicting classes, 2) Apply merge utility, 3) Validate output renders correctly.
Replace the generic 'Capabilities' and 'When to Use' boilerplate with actual optimization rules and patterns (e.g., prefer `space-y-4` over individual margin classes, use `@apply` sparingly, class ordering conventions).
Add specific before/after examples showing unoptimized vs. optimized Tailwind class strings to make the skill immediately actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It repeats 'tailwind class optimizer' numerous times without providing any actual guidance, techniques, or code. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no specific commands, no actual optimization techniques for Tailwind classes. The content only describes what the skill theoretically does without showing how. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The 'Capabilities' section mentions 'step-by-step guidance' but provides none. There are no validation checkpoints or sequences of any kind. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. There are no references to detailed files, no layered information architecture, and the sections are all superficial boilerplate with no real content to organize. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3e83543
- 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.