vue

Use when editing .vue files, creating Vue 3 components, writing composables, or testing Vue code - provides Composition API patterns, props/emits best practices, VueUse integration, and reactive destructuring guidance

1.36x

Quality

92%

Does it follow best practices?

Impact

97%

1.36x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

85%

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-structured as a progressive-disclosure index with an executable Quick Start example and clear reference navigation, all of which verify against the actual bundle. Its main weakness is conciseness: the reference list is triplicated and it carries time-sensitive version/marketing stats that don't belong in the lean overview.

Suggestions

Consolidate the reference listing into a single section — the Quick Reference table, Loading Files checklist, and Available Guidance all repeat the same 10 files; keep one table and one set of one-line descriptions.

Move or drop the 'Current stable: Vue 3.5+ with enhanced reactivity performance (-56% memory, 10x faster array tracking)' line — time-sensitive version/perf numbers are not durable guidance and add tokens that age quickly.

If version-specific notes are needed, relocate them to references/gotchas.md or a clearly labeled 'version notes' subsection rather than the top-of-file overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but the same 10 reference files are listed three times (Quick Reference table, Loading Files checklist, Available Guidance) and 'Current stable: Vue 3.5+ with enhanced reactivity performance (-56% memory, 10x faster array tracking)' is time-sensitive marketing-flavored content not placed in a deprecated/old-patterns section, both of which add tokens that don't earn their place.	2 / 3
Actionability	The Quick Start provides a complete, copy-paste-ready .vue component using defineProps/defineEmits, and the When-to-Use section gives concrete, actionable triggers, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Although this is a reference-index skill rather than a multi-step destructive workflow, the task-to-file decision table plus the Loading Files checklist make the single 'pick the right reference' action unambiguous, satisfying the simple-skills allowance for scoring 3 when the action is clear and well-organized.	3 / 3
Progressive Disclosure	The body is a lean overview pointing one level deep to references/*.md, every referenced file (components, composables, utils-client, testing, typescript, router, reactivity, directives, provide-inject, gotchas) exists in references/, and navigation is well-signaled via both the task→file table and the checklist, matching the 'clear overview with well-signaled one-level-deep references' anchor.	3 / 3
	Total	11 / 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.

The description is strong across the board: it states concrete capabilities, includes natural trigger terms, and explicitly pairs what-it-does with when-to-use guidance. It carves a distinct Vue 3 niche that is unlikely to conflict with unrelated skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'editing .vue files, creating Vue 3 components, writing composables, or testing Vue code' plus 'Composition API patterns, props/emits best practices, VueUse integration, and reactive destructuring guidance' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both 'what' ('provides Composition API patterns, props/emits best practices...') and 'when' ('Use when editing .vue files, creating Vue 3 components...'), matching the anchor requiring clear answers to both with explicit triggers.	3 / 3
Trigger Term Quality	Natural user-facing terms like '.vue files', 'Vue 3 components', 'composables', and 'testing Vue code' give good coverage of phrases a user would actually say, matching the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	The '.vue files' / 'Vue 3 components' / 'composables' triggers carve a clear Vue-3 niche unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	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.