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 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, which slightly reduces specificity. The trigger term coverage is excellent, including both the current and former library names.
Suggestions
Rephrase capability categories as concrete actions, e.g., 'Generates Reka UI component code, configures accessibility attributes, implements controlled/uncontrolled state patterns' instead of listing feature nouns.
| 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'). 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', and 'controlled/uncontrolled state'. These cover the primary name, the former name, and key concepts a user would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific library (Reka UI / formerly Radix Vue) with unique trigger terms that are unlikely to conflict with general Vue or other component library skills. The mention of both current and former names further narrows the niche. | 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 key concepts, installation, and usage patterns with executable examples. The content is concise, actionable, and well-structured with tables and clear section organization. The main weakness is that progressive disclosure relies on referenced files (references/components.md, components/*.md) that aren't provided in the bundle, and several guides are deferred to an external website rather than being bundled.
Suggestions
Include the referenced bundle files (references/components.md and at least a few component files) to make the progressive disclosure structure verifiable and functional.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude's competence with Vue, 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 asChild usage. 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, apply concepts) are unambiguous. The loading files checklist provides clear guidance on when to load references. | 3 / 3 |
Progressive Disclosure | References to components.md and per-component files are well-signaled with a clear table, and the loading checklist is good. However, no bundle files were provided to verify these references exist, and the guides section just points to an external URL rather than bundled files, which limits the skill's self-contained usefulness. | 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
- onmax/nuxt-skills
- Commit
3110745
- 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.