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 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' (opens with 'Use when building styled UI with @nuxt/ui v4 components'). Also provides 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
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 excellent hub 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 maintaining strong progressive disclosure through well-organized reference files. The checklist-based loading guidance 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. Cross-skill routing (vue, nuxt, reka-ui) is specific and actionable. | 3 / 3 |
Workflow Clarity | For a hub/routing skill, the workflow is clear: identify your task from the 'When to Use' list, load the relevant reference file(s) from the checklist, and use the quick reference for basic setup. The explicit 'DO NOT load all files at once' constraint is a clear operational guardrail. This is a single-purpose routing skill, so no multi-step validation is needed. | 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 one-level-deep references. The checklist format with task-based guidance for when to load each file is exemplary. References are clearly signaled with descriptions of what each contains. | 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.
b132148
Table of Contents
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.