CtrlK
BlogDocsLog inGet started
Tessl Logo

nuxt-ui

Use when building styled UI with @nuxt/ui v4 components - create forms with validation, implement data tables with sorting, build modal dialogs and overlays, configure Tailwind Variants theming. Use vue skill for raw component patterns, reka-ui for headless primitives.

85

1.16x
Quality

78%

Does it follow best practices?

Impact

100%

1.16x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/nuxt-ui/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The body is well-structured with excellent progressive disclosure and real reference files, but it duplicates its file listing and omits concrete component-usage examples and validation checkpoints. Tightening the duplication and adding a minimal worked component example would lift it.

Suggestions

Collapse the 'Available Guidance' table and 'Loading Files' checklist into a single list to remove the duplicated file enumeration.

Add one small executable component example (e.g., a validated Form or a Table) in the body so the skill is actionable without forcing a reference load.

For install/configure tasks, add a short sequenced workflow with a validation checkpoint (e.g., 'verify @nuxt/ui is registered in nuxt.config.ts modules before adding UApp').

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude knows, but the 'Available Guidance' table and 'Loading Files' checkbox list enumerate the same six files twice, adding redundancy.

2 / 3

Actionability

The Quick Reference gives copy-paste-ready setup code, but actual component usage (Button, Table, Form) is deferred to references rather than shown, leaving the body's guidance incomplete.

2 / 3

Workflow Clarity

The Loading Files checklist provides some sequence, but there is no explicit multi-step workflow with validation checkpoints for the install/configure/build cycle this skill covers.

2 / 3

Progressive Disclosure

Clear overview with one-level-deep references; all referenced files (installation, theming, components, forms, overlays, composables) exist under references/ and are signaled with a task-based loading checklist.

3 / 3

Total

9

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, action-oriented, and clearly scoped, with explicit triggers and disambiguation against sibling skills. It uses third-person voice and avoids fluff. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('create forms with validation', 'implement data tables with sorting', 'build modal dialogs and overlays', 'configure Tailwind Variants theming') rather than vague language.

3 / 3

Completeness

Explicitly answers both what (concrete actions) and when ('Use when building styled UI with @nuxt/ui v4 components'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes natural terms users would say — forms, data tables, modal dialogs, overlays, theming — paired with 'Use when building styled UI with @nuxt/ui v4 components'.

3 / 3

Distinctiveness Conflict Risk

Niche is clearly scoped to @nuxt/ui v4, and explicit routing ('Use vue skill for raw component patterns, reka-ui for headless primitives') prevents overlap with adjacent skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
onmax/nuxt-skills
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.