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 defines both what it does and when to use it, with excellent Vue 3-specific trigger terms. It lists concrete capabilities (Composition API patterns, props/emits, VueUse, reactive destructuring) and provides explicit trigger conditions. The description is concise, uses third person voice appropriately, and is highly distinguishable from other frontend framework skills.
| 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' (provides 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 inflates token usage without adding new information. The skill itself contains minimal actionable content beyond a single code example, relying entirely on reference files for substance.
Suggestions
Consolidate the three redundant file-mapping sections (quick reference table, loading files checklist, available guidance descriptions) into a single section — e.g., keep the table with brief descriptions and remove the other two.
Add one or two more quick-reference code snippets for the most common patterns (e.g., defineModel, a basic composable structure) so the base skill provides some actionable value without needing to load sub-files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but has some redundancy — the quick reference table, loading files checklist, and available guidance section all convey largely the same information (which reference file to load for which task), tripling the token cost for the same content. | 2 / 3 |
Actionability | The Quick Start provides one executable Vue component example, and the routing to reference files is clear. However, the SKILL.md itself contains almost no actionable guidance beyond that single snippet — all real instructions are deferred to reference files that aren't provided, making the base skill light on concrete, executable content. | 2 / 3 |
Workflow Clarity | For a reference/routing skill like this, the workflow is clear: identify what you're working on, load the relevant reference file, follow its guidance. The decision tree (table + checklist) makes the single-step routing unambiguous, and the 'when to use' vs 'use X skill instead' boundaries are well-defined. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure — the SKILL.md serves as a lean overview with clear one-level-deep references to 10 specific sub-files, each with a brief description of when to load it. The explicit instruction to not load all files at once reinforces the pattern. Token budget estimates are a nice touch. | 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
3110745
- 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.