Tailwind Class Optimizer - Auto-activating skill for Frontend Development. Triggers on: tailwind class optimizer, tailwind class optimizer Part of the Frontend Development skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill tailwind-class-optimizerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, consisting only of a title and category metadata without any substantive content. It fails to explain what optimization actions the skill performs, provides no natural trigger terms users would actually say, and lacks any 'Use when...' guidance for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Sorts, deduplicates, and organizes Tailwind CSS classes. Removes conflicting utilities and groups classes by category (layout, spacing, typography).'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions messy Tailwind classes, class ordering, cleaning up utility classes, or optimizing className attributes.'
Add file type triggers and common variations: '.jsx, .tsx, React components, className cleanup, Tailwind sorting, utility class organization'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Tailwind Class Optimizer') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of sorting, deduplicating, organizing, or any specific operations. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides a category label ('Frontend Development') without explaining capabilities or explicit usage triggers. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundantly listed twice ('tailwind class optimizer, tailwind class optimizer') and miss natural variations users would say like 'clean up tailwind classes', 'organize CSS classes', 'sort utility classes', or 'messy tailwind'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Tailwind' provides some specificity to the CSS/frontend domain, the lack of concrete actions means it could conflict with other Tailwind-related skills (e.g., Tailwind component generation, Tailwind configuration). | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is entirely generic boilerplate with no actual Tailwind CSS optimization content. It contains no executable code, no specific optimization techniques (like class merging, purging, or conflict resolution), and no actionable guidance. The content could apply to literally any skill by replacing 'tailwind class optimizer' with any other topic.
Suggestions
Add concrete code examples showing Tailwind class optimization patterns (e.g., merging conflicting classes, using clsx/tailwind-merge, removing duplicates)
Include specific before/after examples demonstrating class optimization transformations
Provide a clear workflow for analyzing and optimizing Tailwind classes in a component (e.g., 1. Identify duplicates, 2. Resolve conflicts, 3. Apply utility functions)
Remove all generic boilerplate text and replace with actual Tailwind-specific techniques and tools
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. It explains what the skill does in abstract terms without any concrete Tailwind-specific information that Claude doesn't already know. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The content describes capabilities in vague terms ('provides step-by-step guidance', 'generates production-ready code') without actually demonstrating any Tailwind class optimization techniques. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no structure pointing to detailed materials, no examples, and no references to additional resources for Tailwind optimization. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Reviewed
Table of Contents
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.