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 and covers a specific niche (Reka UI). Its main weakness is that the capabilities are listed as feature categories rather than concrete actions (e.g., 'provides component API' rather than 'generates component implementations' or 'configures accessible dialog/popover/menu components'). The trigger term coverage is excellent, especially with the 'Formerly Radix Vue' alias.
Suggestions
Rewrite capability list using concrete action verbs, e.g., 'implements accessible dialogs, popovers, menus, and other headless components' instead of 'provides component API, accessibility patterns'.
| 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, state management, virtualization, styling integration for Reka UI) and 'when' (starts with 'Use when building with Reka UI (headless Vue components)'). 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 terminology like 'asChild', '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 introduces Reka UI with concrete, executable examples while maintaining excellent progressive disclosure through referenced component files. It respects Claude's intelligence by avoiding explanations of basic concepts, provides actionable installation and usage patterns, and clearly delineates when to use this skill versus related ones (vue, nuxt-ui).
| 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—key concepts are tabled concisely, installation shows two real patterns without fluff, and the token budget note at the bottom shows awareness of efficiency. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for installation (both Nuxt and Vite), Dialog with controlled state, Select with uncontrolled default, and asChild usage. The examples are complete Vue SFCs with imports and template code. | 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 files section has clear guidance on when to load what, and cross-references to other skills are well-signaled. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure: the main file is a concise overview with a clear table pointing to references/components.md and per-component files. The 'Loading Files' section explicitly instructs not to load all files at once. References are one level deep and clearly signaled. | 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
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.