vueuse
Use when working with VueUse composables - track mouse position with useMouse, manage localStorage with useStorage, detect network status with useNetwork, debounce values with refDebounced, and access browser APIs reactively. Check VueUse before writing custom composables - most patterns already implemented.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Failed to scan
The risk profile of this skill
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 the VueUse library domain, lists specific composable functions and their purposes, and provides explicit trigger guidance with 'Use when.' The inclusion of concrete function names serves double duty as both specificity and natural trigger terms that developers would use. The additional guidance about checking VueUse before writing custom composables adds practical value for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: track mouse position with useMouse, manage localStorage with useStorage, detect network status with useNetwork, debounce values with refDebounced, and access browser APIs reactively. Also includes the practical guidance to check VueUse before writing custom composables. | 3 / 3 |
Completeness | Clearly answers both 'what' (track mouse position, manage localStorage, detect network status, debounce values, access browser APIs reactively) and 'when' (opens with 'Use when working with VueUse composables' and adds 'Check VueUse before writing custom composables'). The explicit 'Use when' clause is present. | 3 / 3 |
Trigger Term Quality | Includes highly natural keywords users would say: 'VueUse', 'composables', 'useMouse', 'useStorage', 'localStorage', 'useNetwork', 'network status', 'refDebounced', 'debounce', 'browser APIs'. These cover both the library name and specific use-case terms a developer would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to the VueUse library specifically, with named composable functions (useMouse, useStorage, useNetwork, refDebounced) that create a very distinct niche. Unlikely to conflict with general Vue skills or other utility library skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid VueUse skill with strong actionability — concrete code examples, real installation commands, and practical patterns. The progressive disclosure structure is reasonable with references to deeper files, though the main file carries more inline content than ideal (large categories table, multiple SSR approaches). Conciseness could be improved by trimming the categories table and consolidating the SSR section.
Suggestions
Move the large categories table into references/composables.md and keep only a brief summary or top-5 most-used composables inline in SKILL.md.
Consolidate the SSR section to show one primary pattern (e.g., the @vueuse/nuxt auto-handling or isClient check) and reference a separate file for alternative approaches.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some unnecessary content. The categories table is quite large and mostly lists composable names Claude could look up. The SSR section has three separate approaches shown when one or two would suffice. The 'Check VueUse before writing custom composables' line is repeated from the description. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples throughout — installation commands, composable usage patterns, SSR handling, and element ref patterns are all concrete and specific with real import paths and realistic values. | 3 / 3 |
Workflow Clarity | For a reference/utility skill like this, there isn't a complex multi-step workflow requiring validation checkpoints. The single-task patterns are unambiguous, the SSR section clearly sequences the gotchas with solutions, and the loading files section gives clear guidance on when to load what. | 3 / 3 |
Progressive Disclosure | References to composables.md and composable-specific files are well-signaled, but no bundle files were provided to verify these exist. The categories table inlines a lot of content that could arguably live in the referenced composables.md file, and the SKILL.md itself is moderately long with content that could be split (SSR section, Target Element Refs could be separate references). | 2 / 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
b132148
- 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.