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

71%

Does it follow best practices?

Impact

97%

2.69x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/reka-ui/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

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

The body is well-organized, action-oriented, and uses progressive disclosure effectively with a real reference index. Its main weaknesses are time-sensitive version/changelog content baked into the main flow and references to per-component files that do not exist in the bundle.

Suggestions

Move version-specific notes ('Current version: v2.8.0', 'Recent Updates v2.6.0-v2.8.0') into a clearly marked 'Deprecated / old patterns' or separate changelog file so time-sensitive content does not bloat the main body as it ages.

Either generate and include the per-component 'components/*.md' files referenced in the Available Guidance table, or relabel that row to clarify these are external docs rather than bundle files, so navigation targets are real.

Add the missing <script setup> import blocks to the Select and asChild examples so every code snippet is fully copy-paste executable.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes Claude's competence, but the 'Recent Updates (v2.6.0-v2.8.0)' and 'Current version: v2.8.0 (January 2026)' sections embed time-sensitive version numbers and dated changelog items outside a deprecated/old-patterns section, which the guidelines penalize.	3 / 5
Actionability	Provides copy-paste-ready Dialog and Select examples plus installation config covering the common cases, but the Select and asChild snippets omit the <script setup> import lines, leaving minor gaps for full executability.	4 / 5
Workflow Clarity	A clear 'Loading Files' checklist with explicit 'DO NOT load all files at once' guidance sequences the discovery task well; no destructive/batch operation is present so the cap does not apply, though there is no explicit validation loop.	4 / 5
Progressive Disclosure	Well-structured overview with clearly signaled one-level-deep references to references/components.md and a dedicated loading guidance section, but the per-component 'components/*.md' files referenced in the body are not actually present in the bundle, leaving navigation partially aspirational.	4 / 5
	Total	15 / 20 Passed

Description

75%Weight 40%Scale 1-5

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

The description is specific, trigger-rich, and clearly distinguishes the skill's niche, capably stating both what it provides and when to use it. It falls just short of top marks because some capability terms are abstract and the 'when' trigger is a single phrase rather than a comprehensive enumeration.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities ('component API, accessibility patterns, composition (asChild), controlled/uncontrolled state, virtualization, and styling integration') rather than vague language, but 'accessibility patterns' and 'styling integration' are abstract compared to the discrete named actions of the score-5 anchor.	4 / 5
Completeness	Explicitly answers both 'what' ('provides component API, accessibility patterns...') and 'when' ('Use when building with Reka UI'), though the 'when' is a single trigger phrase rather than a comprehensive enumerated list.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('Reka UI', 'headless Vue components', 'Formerly Radix Vue'), but lacks common synonyms or file extensions beyond the library name.	4 / 5
Distinctiveness Conflict Risk	Targets a clearly named niche library ('Reka UI', 'Formerly Radix Vue') with distinct triggers, but has minor overlap risk with the general 'vue' and 'nuxt-ui' skills that also handle Reka-based work.	4 / 5
	Total	16 / 20 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
Path: skills/reka-ui/SKILL.md
Commit: 4754673

Reviewed: 9 days 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.