CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

unocss

UnoCSS instant atomic CSS engine, superset of Tailwind CSS. Use when configuring UnoCSS, writing utility rules, shortcuts, or working with presets like Wind, Icons, Attributify.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/unocss/SKILL.md

The canonical home for this skill is unocss in antfu/skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

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

The body is an exemplary progressive-disclosure index: well-categorized, accurately linked, and easy to navigate, with a useful check-the-config-first decision note. It is dragged down by an intro that duplicates the frontmatter description, a penalized version/date line, and the absence of any quick-start example or sample configuration in the top-level file.

Suggestions

Trim or remove the opening paragraph that restates the frontmatter description (atomic CSS engine, Tailwind superset), keeping only the non-obvious fact that all utilities come from presets.

Remove the "based on UnoCSS v66.10.5, generated at 2026-09-25" version/date line from the body, or move it into a dedicated old-patterns/deprecated section so time-sensitive details don't consume context.

Add a minimal quick-start snippet to the body — e.g. a sample uno.config.ts with one preset and one shortcut — so the most common task (initial configuration) is actionable before jumping into references/core-config.md.

DimensionReasoningScore

Conciseness

The intro paragraph ("UnoCSS is an instant atomic CSS engine... superset of Tailwind CSS, so you can reuse your Tailwind knowledge") largely duplicates the always-loaded frontmatter description, and the version line "based on UnoCSS v66.10.5, generated at 2026-09-25" is time-sensitive information not placed in a deprecated/old-patterns section, which the guidelines explicitly penalize; this fits "mostly efficient but includes some unnecessary explanation or could be tightened" better than the minor-trimmings anchor 4.

3 / 5

Actionability

The Important paragraph gives genuinely concrete guidance ("check for `uno.config.*` or `unocss.config.*` files", "avoid using attributify mode... stick to basic `class` usage"), but the rest of the body is a navigation index with no quick-start snippet or sample config, fitting "some concrete guidance but incomplete; missing key details"; not 2 because the config-check and fallback guidance is specific and executable rather than a high-level hint.

3 / 5

Workflow Clarity

The Important paragraph encodes a check-first workflow with a decision point and explicit fallback ("If the project setup is unclear, avoid using attributify mode and other advanced features"), and the topic tables make the lookup action unambiguous — matching "clear sequence with most checkpoints present"; not 5 because there is no explicit multi-step sequence for common tasks such as initial configuration.

4 / 5

Progressive Disclosure

The body is a clean overview with category-organized tables (Core, Presets, Transformers, Integrations), each row carrying a topic, description, and one-level-deep link, and all 24 referenced files (e.g. references/core-config.md, references/preset-wind3.md, references/integrations-vite.md) exist in the bundle — matching the "clear overview with well-signaled one-level-deep references; easy navigation" anchor exactly.

5 / 5

Total

15

/

20

Passed

Description

75%Weight 40%Scale 1-5

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 solid description with an explicit and concrete "Use when" clause, good natural trigger terms, and a distinct UnoCSS niche. Its main weakness is that the "what" identifies the tool rather than stating the skill's capabilities as actions, and the Tailwind superset claim introduces slight overlap risk.

DimensionReasoningScore

Specificity

Lists several concrete actions ("configuring UnoCSS, writing utility rules, shortcuts, or working with presets"), matching the several-specific-actions anchor with minor gaps; it falls short of 5 because the opening sentence is tool identification ("instant atomic CSS engine, superset of Tailwind CSS") rather than capability actions, and covered areas like transformers and integrations are unmentioned.

4 / 5

Completeness

Both parts are present: the "what" ("UnoCSS instant atomic CSS engine, superset of Tailwind CSS") and an explicit "Use when..." clause with concrete triggers; not 5 because the "what" is a noun-phrase tool identification rather than a statement of what the skill does, while the anchor-5 pattern expresses capabilities as actions, and not 4-to-3 since the "when" is explicit and specific rather than weakly implied.

4 / 5

Trigger Term Quality

Good natural keyword coverage including "UnoCSS", "Tailwind CSS", "utility rules", "shortcuts", "presets", "Wind", "Icons", and "Attributify", which users would naturally say; not 5 because synonyms like "atomic CSS", "Windi", or config-file phrases are missing, and not 3 since coverage clearly exceeds "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

Triggers are strongly UnoCSS-specific (presets "Wind", "Icons", "Attributify"), but the "superset of Tailwind CSS" claim creates minor overlap risk with plain Tailwind work, fitting the "mostly distinct; minor overlap risk with closely related skills" anchor rather than the clear-niche anchor 5.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

onmax/nuxt-skills

Path

skills/unocss/SKILL.md

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.