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.
100
Does it follow best practices?
Validation for skill structure
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 composables with their purposes, and includes explicit 'Use when' guidance. The description uses third person voice correctly and provides both conceptual triggers ('composables', 'browser APIs') and specific function names for matching.
| 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', 'access browser APIs reactively'. These are concrete, named composables with specific purposes. | 3 / 3 |
Completeness | Explicitly answers both what (track mouse, manage localStorage, detect network, debounce values, access browser APIs) AND when ('Use when working with VueUse composables', 'Check VueUse before writing custom composables'). The 'Use when' clause is present at the start. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'VueUse', 'composables', 'mouse position', 'localStorage', 'network status', 'debounce', 'browser APIs', plus specific function names like 'useMouse', 'useStorage', 'useNetwork', 'refDebounced'. Good coverage of both conceptual and technical terms. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on VueUse library composables with named functions. Unlikely to conflict with general Vue skills or other utility libraries due to explicit VueUse branding and specific composable names. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%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-crafted skill that efficiently covers VueUse essentials. It provides actionable code examples, clear navigation to deeper references, and addresses common pitfalls (SSR, component refs) without over-explaining. The category table and quick reference section make it easy to find relevant composables.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient, assuming Claude's competence with Vue. No unnecessary explanations of what composables are or how Vue works - jumps straight to installation and usage patterns. | 3 / 3 |
Actionability | Provides fully executable code examples throughout - installation commands, TypeScript snippets for common patterns, SSR handling, and component ref patterns are all copy-paste ready. | 3 / 3 |
Workflow Clarity | For a reference/utility skill, the workflow is appropriately simple. Clear guidance on when to load which files, and SSR gotchas section provides clear decision paths (check isClient, wrap in onMounted, or use SSR-safe composables). | 3 / 3 |
Progressive Disclosure | Excellent structure with quick reference table pointing to specific files, clear 'Loading Files' section with one-level-deep references, and explicit instruction not to load all files at once. | 3 / 3 |
Total | 12 / 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.
Table of Contents
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.