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 uses proper third-person voice and lists concrete, specific capabilities without being verbose. The description would effectively differentiate this skill from other frontend framework skills in a large skill library.
| 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 other framework skills (React, Angular, etc.). | 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 navigation hub skill that excels at progressive disclosure and directing Claude to the right reference file. Its main weakness is redundancy—the same 10 reference files are listed three times in slightly different formats (table, checklist, descriptions), which wastes tokens without adding clarity. The actionability of the hub itself is limited since nearly all concrete guidance is delegated to sub-files.
Suggestions
Consolidate the three listings of reference files (table, checklist, descriptions) into a single format—the table with brief descriptions would suffice, saving ~40% of the content's tokens.
Add one or two more executable quick-reference patterns inline (e.g., a composable skeleton or defineModel usage) so the base file provides more immediate actionable value without needing to load sub-files.
| 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, but the main skill body is primarily a routing/navigation document pointing to other files. The actual actionable guidance lives in the referenced files, so this file itself provides limited concrete instruction beyond the single code snippet. | 2 / 3 |
Workflow Clarity | For a reference/routing skill like this, the workflow is clear: identify what you're working on, load the relevant file, follow its guidance. The table and checklist make task-to-file mapping unambiguous. This is a simple single-purpose skill (navigation hub) and the single action is clear. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure design. The skill serves as a lean overview hub with well-signaled one-level-deep references. Token budget estimates are provided, files are clearly categorized by task, and there's an explicit instruction not to load all files at once. | 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
48efc7a
- 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.