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.

2.69x

Quality

82%

Does it follow best practices?

Impact

97%

2.69x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is actionable and well-structured with executable examples and a clear reference index, but loses points for inline version churn and for referencing per-component files that are absent from the bundle.

Suggestions

Move version-specific entries ('Current version', 'Recent Updates') into a dedicated 'Version history / deprecated' section so time-sensitive details don't bloat the core overview.

Either ship the referenced 'components/*.md' per-component files or reword the body/index so navigation only points to files that actually exist in the bundle.

Add a short explicit task workflow (identify component → load components.md → load the per-component file → apply pattern) with a verification step to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is largely lean with tables and code, but time-sensitive information ('Current version: v2.8.0 (January 2026)' and the 'Recent Updates (v2.6.0-v2.8.0)' list) sits inline rather than in a deprecated/old-patterns section, which the rubric penalizes.	2 / 3
Actionability	Installation snippets and executable Vue SFC examples (Dialog with v-model, uncontrolled Select, asChild trigger) are concrete and copy-paste ready, matching the fully-executable anchor.	3 / 3
Workflow Clarity	A loading-file checklist and 'DO NOT load all files at once' give some guidance, but there is no explicit multi-step task sequence with validation checkpoints, leaving the workflow implicit.	2 / 3
Progressive Disclosure	The overview signals one-level-deep references well (references/components.md exists and is indexed by category), but the per-component 'components/*.md' files referenced in the body and index are not present in the actual bundle, so navigation points to files that are not shipped.	2 / 3
	Total	9 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concise description that covers what the skill does, when to use it, and its naming context with concrete capabilities. No meaningful gaps relative to the rubric anchors.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete capabilities — 'component API, accessibility patterns, composition (asChild), controlled/uncontrolled state, virtualization, and styling integration' — matching the anchor for naming several specific items.	3 / 3
Completeness	It explicitly answers both what ('provides component API, accessibility patterns...') and when ('Use when building with Reka UI (headless Vue components)'), satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Natural user-facing terms are well covered: 'Reka UI', 'headless Vue components', and 'Formerly Radix Vue' capture the aliases a user would actually say, including the prior project name.	3 / 3
Distinctiveness Conflict Risk	The Reka UI / Radix Vue niche is distinct, and the skill defers to separate 'vue' and 'nuxt-ui' skills, making false triggering unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: onmax/nuxt-skills
Commit: a212359

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.