reka-ui
Use when building with Reka UI (headless Vue components) - provides component API, accessibility patterns, composition (asChild), controlled/uncontrolled state, virtualization, and styling integration. Formerly Radix Vue.
96
95%
Does it follow best practices?
Impact
97%
2.69xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%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 a solid skill description that clearly identifies when it should be used (building with Reka UI) and what it covers (component API, accessibility, composition patterns, state management, virtualization, styling). The inclusion of the former name 'Radix Vue' is a smart touch for discoverability. The main weakness is that capabilities are listed as noun phrases/categories rather than concrete actions, which slightly reduces specificity.
Suggestions
Rephrase capability list using action verbs for greater specificity, e.g., 'Generates Reka UI component implementations, configures accessibility patterns, handles controlled/uncontrolled state management...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Reka UI / headless Vue components) and lists several capabilities (component API, accessibility patterns, composition, controlled/uncontrolled state, virtualization, styling integration), but these are more like feature categories than concrete actions. It doesn't use action verbs like 'generates', 'configures', or 'implements'. | 2 / 3 |
Completeness | Explicitly answers both 'what' (provides component API, accessibility patterns, composition, controlled/uncontrolled state, virtualization, styling integration) and 'when' (starts with 'Use when building with Reka UI'). The 'Use when...' clause is present and clear. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'Reka UI', 'headless Vue components', 'asChild', 'Radix Vue', 'accessibility patterns', 'virtualization', 'controlled/uncontrolled state'. Users working with this library would naturally use these terms, and the alias 'Formerly Radix Vue' captures users who know the old name. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific library (Reka UI / formerly Radix Vue) with specific concepts like 'asChild' composition and headless Vue components. Very unlikely to conflict with other skills unless there's another Reka UI skill. | 3 / 3 |
Total | 11 / 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 a high-quality skill that efficiently covers Reka UI's key concepts, installation, and usage patterns while maintaining excellent progressive disclosure to detailed component references. The code examples are complete and executable, the key concepts table is concise, and the file loading guidance prevents unnecessary token consumption. The recent updates section with version-specific changes adds practical value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It avoids explaining what Vue components are or how headless UI works. Every section earns its place—tables for quick reference, code examples without preamble, and clear cross-references. The token budget note at the bottom is a nice touch. | 3 / 3 |
Actionability | Provides fully executable code examples for installation (both Nuxt and Vite), a complete Dialog component with controlled state, a Select with uncontrolled default, and the asChild pattern. All examples are copy-paste ready with proper imports. | 3 / 3 |
Workflow Clarity | This is primarily a component library reference skill rather than a multi-step destructive workflow. The single-task patterns (install, use component) are unambiguous. The loading guidance with checkboxes provides clear sequencing for how to discover and use components. No destructive operations require validation loops. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure: the SKILL.md serves as a concise overview with a clear table pointing to references/components.md and per-component files. References are one level deep and well-signaled. The explicit 'DO NOT load all files at once' instruction is a strong navigation cue. | 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
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.