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.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

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 library reference skill with excellent actionability—every pattern includes executable code. The progressive disclosure structure is reasonable with clear pointers to reference files, though the inline categories table and detailed SSR section make the overview slightly heavier than ideal. Conciseness is good but could be tightened by moving the full category listing to the reference file.

Suggestions

Move the full categories table to references/composables.md and keep only 3-4 most common categories inline to reduce the overview's token footprint.

Condense the SSR section to one recommended approach (e.g., just the @vueuse/nuxt auto-handling note plus the isClient check) and move the alternatives to a reference file.

Dimension	Reasoning	Score
Conciseness	Generally efficient but includes some unnecessary content. The categories table is quite large and mostly serves as a lookup that could be in a reference file. The SSR section is somewhat verbose with three separate approaches shown. However, most content earns its place and avoids explaining basic concepts.	2 / 3
Actionability	All code examples are concrete, executable, and copy-paste ready. Installation commands are specific, common patterns show real usage with actual API calls, and SSR gotchas include working code solutions with clear ✅/❌ markers.	3 / 3
Workflow Clarity	For a library reference skill (not a multi-step destructive process), the workflow is clear: install, find composable via reference files, use patterns shown. The loading files section provides clear guidance on what to load when. No destructive or batch operations require validation checkpoints.	3 / 3
Progressive Disclosure	References to composables.md and composables/<name>.md files are well-signaled, but no bundle files were provided to verify these exist. The categories table (12 rows) could arguably live in the referenced composables.md file rather than inline, and the SSR/Target Element sections are fairly detailed for an overview file.	2 / 3
	Total	10 / 12 Passed

Description

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 as excellent trigger terms and distinctiveness markers. 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', 'custom composables'. These cover both the library name and specific use cases users would mention.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to VueUse composables specifically, with named functions (useMouse, useStorage, useNetwork, refDebounced) that create a distinct niche. Unlikely to conflict with general Vue skills or other utility library skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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: 4 months ago

Table of Contents

Discovery Implementation Validation

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.