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.
100
100%
Does it follow best practices?
Impact
100%
1.16xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that clearly defines its scope around @nuxt/ui v4 components, lists concrete actions, includes natural trigger terms, and explicitly delineates boundaries with related skills. The 'Use when' clause is present and specific, and the disambiguation from vue and reka-ui skills is a strong differentiator. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'create forms with validation', 'implement data tables with sorting', 'build modal dialogs and overlays', 'configure Tailwind Variants theming'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('create forms with validation, implement data tables with sorting, build modal dialogs and overlays, configure Tailwind Variants theming') and when ('Use when building styled UI with @nuxt/ui v4 components'). The explicit 'Use when' clause is present at the start. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: '@nuxt/ui', 'forms with validation', 'data tables', 'sorting', 'modal dialogs', 'overlays', 'Tailwind Variants', 'theming', 'styled UI', 'v4 components'. Good coverage of terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by specifying '@nuxt/ui v4' as the niche, and explicitly differentiates from related skills ('Use vue skill for raw component patterns, reka-ui for headless primitives'), which actively reduces conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary hub/index skill that efficiently routes Claude to the right reference material based on the task at hand. It provides just enough inline content (setup code, key concepts) to be immediately useful while deferring detailed guidance to well-organized reference files. The task-based checklist for loading files and cross-skill routing are particularly well done.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It avoids explaining what Nuxt UI, Tailwind CSS, or Vue are. Every section serves a clear purpose—routing to the right reference file or providing minimal setup code. The token budget note at the bottom is a nice touch. | 3 / 3 |
Actionability | The quick reference section provides fully executable, copy-paste ready code for nuxt.config.ts, main.css, and app.vue setup. The checklist-style loading guidance gives concrete direction on which files to load for which tasks. Component-specific details are deferred to reference files appropriately. | 3 / 3 |
Workflow Clarity | For a hub/index skill, the workflow is clear: identify your task from the 'When to Use' list, load the relevant reference file(s) from the checklist, and follow the guidance there. The explicit 'DO NOT load all files at once' instruction is a clear constraint. This is not a multi-step destructive operation, so validation checkpoints are not required. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The main skill is a concise overview (~300 tokens as noted) with a well-organized table of reference files, a task-based checklist for loading them, and clear one-level-deep references. Cross-skill references (vue, nuxt, reka-ui) are clearly signaled. However, no bundle files were provided to verify the referenced paths actually exist. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- onmax/nuxt-skills
- Commit
3110745
- 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.