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 communicates both what the skill does and when to use it. It uses an explicit 'Use when' clause with highly specific Vue 3 ecosystem terminology that would naturally appear in developer requests. The description is concise yet comprehensive, covering the key areas of Vue 3 development without unnecessary verbosity.
| 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 (editing .vue files, creating Vue 3 components, writing composables, testing Vue code) with an explicit 'Use when' clause. | 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 in requests. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Vue 3-specific triggers like '.vue files', 'Composition API', 'VueUse', and 'composables' that clearly distinguish it from 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 navigation. Its main weakness is redundancy — the reference files are listed three separate times in slightly different formats (table, checklist, descriptions), which wastes tokens without adding proportional value. The actionable content is thin since nearly everything is deferred to sub-files, though the single Quick Start example is executable and useful.
Suggestions
Consolidate the three listings of reference files into a single format (e.g., the table with brief descriptions) to reduce redundancy and save ~40% of the content's tokens.
Add one or two more Quick Start examples covering common patterns (e.g., a composable skeleton, a defineModel usage) to increase actionability without requiring sub-file loading.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but has redundancy: the reference files are listed three times (table, checklist, and descriptions section), which is wasteful. The 'When to Use' section is helpful but the triple listing of the same references inflates token count unnecessarily. | 2 / 3 |
Actionability | The Quick Start provides one executable Vue component example, which is good. However, the skill itself is primarily a routing document to sub-files, so the actual actionable guidance is minimal — most concrete instructions are deferred to reference files. The single example covers only the most basic pattern. | 2 / 3 |
Workflow Clarity | For a reference/routing skill, the workflow is clear: identify what you're working on via the table, load the relevant file, follow its guidance. The 'DO NOT load all files at once' instruction is a clear constraint. This is a simple routing skill where the single action (load the right reference) is unambiguous. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the skill is a concise overview with clear one-level-deep references to 10 sub-files. Navigation is well-signaled via table, checklist, and descriptive links. Content is appropriately split with token estimates 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
- onmax/nuxt-skills
- Commit
00fb59d
- 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.