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 specific concrete capabilities, includes natural trigger terms developers would use, and explicitly disambiguates from related skills. The 'Use when...' clause is present and well-formed, and the cross-references to vue and reka-ui skills are a strong addition for reducing selection conflicts.
| 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, build modals, configure theming) and 'when' ('Use when building styled UI with @nuxt/ui v4 components'). Also provides explicit disambiguation guidance for related skills (vue, reka-ui). | 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 ('Use vue skill for raw component patterns, 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 hub skill that excels at progressive disclosure and conciseness. It efficiently directs Claude to the right reference file based on the task at hand, with clear navigation and minimal token overhead. The main weakness is that the skill body itself provides limited actionable guidance beyond initial setup—nearly all concrete instructions are deferred to reference files, which means Claude must load additional files for almost any task.
Suggestions
Add 1-2 brief, executable examples of common component usage (e.g., a UButton with variants, a simple UForm with Zod validation) directly in the main skill to improve actionability without requiring file loads for basic tasks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Nuxt UI, Tailwind, or Reka UI are beyond brief identifiers. Every section serves a clear purpose. The token budget note at the bottom is a nice touch. | 3 / 3 |
Actionability | The Quick Reference section provides executable setup code (nuxt.config.ts, CSS import, UApp wrapper), but the skill itself delegates all substantive guidance to reference files. There are no concrete examples of actually using components, building forms, or working with overlays in the main skill body. | 2 / 3 |
Workflow Clarity | For a hub/index skill, the workflow is clear: identify your task from the checklist, load the relevant reference file, and follow its guidance. The 'Loading Files' checklist with task-based conditions provides an unambiguous decision process. The explicit 'DO NOT load all files at once' constraint is a good guardrail. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure. The main skill is a concise overview with a well-organized table of reference files, each clearly described by topic. References are one level deep, clearly signaled with both a table and a task-based checklist. Content is appropriately split across reference files. | 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
00fb59d
- 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.