styling

CSS and Tailwind, cn(), flex layouts. Use for "style this", "fix the CSS", "add classes", "not scrolling", "overflow", Tailwind utilities.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%

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

A high-quality, actionable styling reference with concrete code, clear decision rules, and verification checkpoints; the main gap is progressive disclosure, since deep material is monolithically inline rather than split into reference files.

Suggestions

Move the detailed Flex Column Scroll Trap material (paneforge/ScrollArea subsections and the utility table) into a references/ file, keeping SKILL.md as a concise overview with a one-level link.

Add a short table of contents or 'When to read each section' pointer at the top so the inline sections are navigable as progressive-disclosure entry points.

Dimension	Reasoning	Score
Conciseness	The body is dense with codebase-specific, non-obvious guidance (the flex scroll trap, primitive-override heuristics) and assumes Claude's competence; it avoids generic concept padding, so every section earns its place.	3 / 3
Actionability	Each topic ships concrete, executable Svelte/Tailwind code via Good/Avoid and Before/After blocks plus specific class combinations, making the guidance copy-paste ready.	3 / 3
Workflow Clarity	Decision rules are unambiguous and sequenced (problem -> three-utility fix -> verification that all three are required -> Before/After -> Rule of Thumb), with an explicit completeness checklist for the flex fix.	3 / 3
Progressive Disclosure	The body is well-sectioned and its one external reference is clearly signaled one level deep, but all substantive content lives inline in a ~190-line SKILL.md with no internal split into reference files for the substantial flex/ScrollArea/paneforge material.	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.

A tight, trigger-rich description with an explicit Use-for clause and a clear styling niche; its only weakness is that the capability statement lists technologies rather than concrete actions.

Dimension	Reasoning	Score
Specificity	The description names a concrete domain ("CSS and Tailwind, cn(), flex layouts") but lists technologies rather than concrete actions; there are no verbs describing what the skill does, so it stops short of the multi-action score-3 anchor.	2 / 3
Completeness	It states what the skill covers (CSS/Tailwind, cn(), flex layouts) and provides an explicit "Use for ..." trigger clause answering when to invoke it, so both what and when are present.	3 / 3
Trigger Term Quality	The "Use for" clause lists natural phrases users would actually say ("style this", "fix the CSS", "add classes", "not scrolling", "overflow", "Tailwind utilities"), giving good coverage of natural trigger terms.	3 / 3
Distinctiveness Conflict Risk	The CSS/Tailwind styling niche with specific triggers (cn(), flex layouts, overflow, Tailwind utilities) is a clear, distinct niche unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: EpicenterHQ/epicenter
Path: .agents/skills/styling/SKILL.md
Commit: cb12bcc

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.