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.
95
92%
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 capabilities, includes natural trigger terms, and explicitly disambiguates from related skills. The 'Use when...' clause is present and well-formed, and the cross-references to other skills (vue, reka-ui) are a strong differentiator that reduces conflict risk.
| 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' (forms with validation, data tables, modals, theming) and 'when' with an explicit 'Use when building styled UI with @nuxt/ui v4 components'. Also provides disambiguation guidance ('Use vue skill for raw component patterns, reka-ui for headless primitives'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: '@nuxt/ui', 'v4', 'forms', 'validation', 'data tables', 'sorting', 'modal dialogs', 'overlays', 'Tailwind Variants', 'theming'. Good coverage of terms a developer working with Nuxt UI would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by specifying '@nuxt/ui v4' as the niche, and explicitly differentiates from related skills (vue skill for raw components, reka-ui for headless primitives), which directly reduces conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured index/routing skill that efficiently directs Claude to the right reference files based on the task at hand. Its strengths are excellent progressive disclosure, token efficiency, and clear navigation. The main weakness is that the skill body itself provides minimal actionable content beyond initial setup—most concrete guidance is deferred to reference files, which is appropriate for a 125+ component library but means the skill alone doesn't demonstrate much executable usage.
| 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 provides executable setup code (nuxt.config.ts, main.css, app.vue), which is good. However, the skill itself is primarily a routing document—it doesn't provide concrete examples of using components, forms, or overlays directly. The actionable content lives in referenced files, so the skill body itself is more of a directory than an instruction set. | 2 / 3 |
Workflow Clarity | This is primarily a routing/index skill rather than a multi-step workflow skill. The 'Loading Files' checklist with clear conditional guidance ('if installing...', 'if customizing theme...') provides an unambiguous decision workflow. The 'DO NOT load all files at once' constraint is a clear validation checkpoint for resource management. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure. The main skill is a concise overview with a well-organized table of references, a checklist for conditional loading, and clear one-level-deep navigation to specific reference files. Content is appropriately split across installation, theming, components, forms, overlays, and composables. | 3 / 3 |
Total | 11 / 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
48efc7a
- 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.