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.
93
91%
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 its niche (Reka UI headless Vue components) and includes an explicit 'Use when' trigger clause. The trigger terms are excellent, covering both the current and former library names plus key concepts. The main weakness is that the capabilities listed are more like feature categories than specific concrete actions (e.g., 'provides component API' rather than 'generates Reka UI component code, configures accessibility attributes').
Suggestions
Rephrase capability list with more concrete action verbs, e.g., 'Generates Reka UI component implementations, configures accessibility attributes, sets up controlled/uncontrolled state patterns' instead of listing feature categories.
| 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 'provides examples for' or 'generates components'. | 2 / 3 |
Completeness | Explicitly answers both 'what' (provides component API, accessibility patterns, composition, controlled/uncontrolled state, virtualization, styling integration) and 'when' (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', 'accessibility patterns', 'virtualization', 'Radix Vue'. A user working with this library would naturally mention these terms, and the alias 'Formerly Radix Vue' catches 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
92%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-crafted skill that efficiently covers Reka UI's core concepts, installation, and usage patterns. It excels at conciseness and actionability with executable examples and compact table-based reference. The main weakness is that bundle files weren't provided to verify the referenced progressive disclosure structure, and some content (recent updates, resources) could potentially be offloaded to reference files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude's competence with Vue and component libraries, avoids explaining what headless components or WAI-ARIA are, and uses tables for compact information delivery. Every section earns its place. | 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 an asChild pattern. All examples are copy-paste ready with proper imports. | 3 / 3 |
Workflow Clarity | This is primarily a reference/component-library skill rather than a multi-step destructive workflow. The single-task patterns (install, use component) are unambiguous, and the loading guidance includes clear instructions about when to load reference files. No destructive operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | The skill references `references/components.md` and `components/*.md` files, and provides a clear loading checklist. However, no bundle files were provided to verify these references exist. The guides section points to external docs rather than bundled files, which limits self-contained progressive disclosure. Some content like the Recent Updates section could arguably be in a separate reference file. | 2 / 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
- popey/nuxt-skills
- Commit
6b12458
- 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.