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
89
85%
Does it follow best practices?
Impact
97%
1.36xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly identifies its niche (Vue 3 development), lists specific capabilities, and provides explicit trigger conditions. It uses third-person voice appropriately and includes a rich set of natural keywords that Vue developers would use. The 'Use when...' clause at the beginning effectively communicates when this skill should be selected.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and patterns: editing .vue files, creating Vue 3 components, writing composables, testing Vue code, Composition API patterns, props/emits best practices, VueUse integration, and reactive destructuring guidance. | 3 / 3 |
Completeness | Clearly answers both 'what' (Composition API patterns, props/emits best practices, VueUse integration, reactive destructuring guidance) and 'when' (explicitly starts with 'Use when editing .vue files, creating Vue 3 components, writing composables, or testing Vue code'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: '.vue files', 'Vue 3', 'components', 'composables', 'Composition API', 'props', 'emits', 'VueUse', 'reactive destructuring' — these are all terms a Vue developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Vue 3-specific triggers like '.vue files', 'Composition API', 'VueUse', 'composables', and 'reactive destructuring' — these are unlikely to conflict with general JavaScript, React, or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%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-structured routing/index skill that excels at progressive disclosure and directing Claude to the right reference file. Its main weakness is the triple repetition of the file-to-task mapping (table, checklist, and descriptions section), which wastes tokens. The actionable content within the SKILL.md itself is limited to a single Quick Start example, with the real substance presumably in the referenced files.
Suggestions
Consolidate the three file-mapping sections (Quick Reference table, Loading Files checklist, Available Guidance descriptions) into a single section — e.g., keep the table with brief descriptions as a third column, removing the other two redundant sections.
Add one or two more executable quick-reference snippets for the most common patterns (e.g., a composable skeleton, a defineModel example) to improve actionability without needing to load sub-files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but has some redundancy — the quick reference table and the 'Loading Files' checklist and the 'Available Guidance' section all describe essentially the same mapping three times. This repetition wastes tokens without adding meaningful value. | 2 / 3 |
Actionability | The Quick Start provides one executable code example, but the SKILL.md itself is primarily a routing document pointing to reference files. The actionable content is minimal — it tells you which file to load but doesn't provide concrete guidance for most tasks beyond the single component snippet. | 2 / 3 |
Workflow Clarity | For a reference/routing skill, the workflow is clear and unambiguous: identify your task from the table, load the relevant file, follow its guidance. The decision tree (when to use this skill vs nuxt/nuxt-ui/reka-ui/vueuse) and the task-to-file mapping provide clear sequencing for a single-action workflow. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure — concise overview with well-signaled one-level-deep references to 10 specific sub-files. Clear navigation via both table and checklist formats, with explicit instruction not to load all files at once. Token budget estimates are provided. | 3 / 3 |
Total | 10 / 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.