nuxt-ui
tessl i github:onmax/nuxt-skills --skill nuxt-uiUse when building styled UI with @nuxt/ui v4 components (Button, Modal, Form, Table, etc.) - provides ready-to-use components with Tailwind Variants theming. Use vue skill for raw component patterns, reka-ui for headless primitives.
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
Implementation
100%This is an exemplary skill file that serves as a well-organized index/router to detailed documentation. It's highly token-efficient (~300 tokens noted), provides actionable quick-start code, and clearly directs users to appropriate sub-files based on their specific needs. The structure respects Claude's intelligence while providing exactly the navigation and context needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Nuxt UI is or how component libraries work. Every section serves a clear purpose with minimal prose. | 3 / 3 |
Actionability | Provides executable code snippets for nuxt.config.ts, CSS imports, and app.vue setup. Clear, copy-paste ready examples for the core setup pattern. | 3 / 3 |
Workflow Clarity | For a reference/index skill, the workflow is clear: identify your task from the 'When to Use' list, then load the appropriate reference file. The 'Usage Pattern' section provides explicit guidance on which file to load for each context. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview pointing to one-level-deep references. Well-organized table mapping topics to files, explicit instruction to not load all files at once, and appropriate content split between main skill and reference files. | 3 / 3 |
Total | 12 / 12 Passed |
Activation
90%This is a well-crafted description that excels at disambiguation and trigger terms, clearly positioning itself relative to related skills (vue, reka-ui). The main weakness is that it lists component types rather than describing concrete actions the skill enables. Adding action verbs like 'create', 'style', or 'implement' would strengthen specificity.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Create and style UI components like buttons, modals, forms, and tables using @nuxt/ui v4'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (@nuxt/ui v4) and provides examples of components (Button, Modal, Form, Table), but doesn't describe concrete actions like 'create forms', 'build modals', or 'implement data tables'. | 2 / 3 |
Completeness | Clearly answers both what ('building styled UI with @nuxt/ui v4 components with Tailwind Variants theming') and when ('Use when building styled UI with @nuxt/ui v4 components'), plus provides disambiguation guidance for related skills. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'styled UI', 'Button', 'Modal', 'Form', 'Table', '@nuxt/ui', 'Tailwind Variants', 'theming', and 'components' - good coverage of terms developers would use. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly distinguishes itself from 'vue skill' and 'reka-ui' with clear boundaries - this skill is for styled @nuxt/ui v4 components specifically, not raw Vue patterns or headless primitives. | 3 / 3 |
Total | 11 / 12 Passed |
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.