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 repeated as a trigger term with no substantive content. It fails to describe what the skill actually does (e.g., deduplicates, sorts, removes unused Tailwind classes), provides no natural trigger terms users would say, and lacks any explicit 'Use when...' guidance. The only slight positive is that mentioning 'Tailwind' gives it minimal domain specificity.
Suggestions
Add concrete actions describing what the optimizer does, e.g., 'Deduplicates redundant Tailwind utility classes, sorts class lists, removes unused classes, and consolidates conflicting utilities.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to clean up Tailwind classes, optimize utility class usage, sort className attributes, or reduce CSS bloat in Tailwind projects.'
Remove the duplicate trigger term and expand with varied natural phrases users might say, such as 'tailwind cleanup', 'sort classes', 'deduplicate utilities', 'className optimization'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names 'Tailwind Class Optimizer' but provides no concrete actions—it doesn't explain what optimization means (e.g., deduplicating classes, sorting, removing unused classes). 'Auto-activating skill for Frontend Development' is vague filler. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'Use when...' clause explaining when Claude should select this skill. Both dimensions are essentially missing. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'tailwind class optimizer' repeated twice. It misses natural user phrases like 'clean up tailwind classes', 'optimize CSS utilities', 'deduplicate classes', 'sort tailwind', or 'unused classes'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Tailwind' provides some domain specificity that distinguishes it from generic CSS or code skills, but without concrete actions described, it could still overlap with other Tailwind or CSS-related 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 a hollow template with no actual content about Tailwind class optimization. It contains only generic boilerplate that repeats the skill name without providing any actionable techniques, code examples, or workflows. It would provide zero value to Claude when attempting to help users optimize Tailwind CSS classes.
Suggestions
Add concrete code examples showing Tailwind class optimization techniques (e.g., using tailwind-merge to resolve conflicting classes, removing duplicate utilities, ordering classes consistently).
Provide a clear workflow for analyzing and optimizing Tailwind classes in a component, such as: identify duplicates → resolve conflicts → apply utility grouping → validate output.
Include specific tool recommendations with executable examples (e.g., `clsx`, `tailwind-merge`, `prettier-plugin-tailwindcss`) and show before/after code snippets.
Replace all boilerplate sections (When to Use, Example Triggers, Capabilities) with actual technical content that teaches optimization patterns Claude doesn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance, techniques, or code for optimizing Tailwind classes. Every section restates the skill name without adding value. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no specific commands, no actual Tailwind class optimization techniques (e.g., merging conflicting classes, using clsx/tailwind-merge, removing duplicates). The content only describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The 'step-by-step guidance' mentioned in capabilities is never actually provided. There are no sequences, validation checkpoints, or any process description whatsoever. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of boilerplate with no meaningful structure. There are no references to detailed resources, no separation of quick-start vs. advanced content, and the sections that exist contain no real information. | 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
3076d78
- 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.