Creates Vue 3 components, builds vanilla JS composables, configures Vite projects, and sets up routing and state management using JavaScript only — no TypeScript. Generates JSDoc-typed code with @typedef, @param, and @returns annotations for full type coverage without a TS compiler. Use when building Vue 3 applications with JavaScript only (no TypeScript), when projects require JSDoc-based type hints, when migrating from Vue 2 Options API to Composition API in JS, or when teams prefer vanilla JavaScript, .mjs modules, or need quick prototypes without TypeScript setup.
98
100%
Does it follow best practices?
Impact
97%
1.21xAverage score across 6 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 an excellent skill description that excels across all dimensions. It provides specific concrete actions, includes comprehensive natural trigger terms that developers would actually use, explicitly answers both what and when questions, and carves out a clear niche (Vue 3 + JS-only + JSDoc) that minimizes conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Creates Vue 3 components', 'builds vanilla JS composables', 'configures Vite projects', 'sets up routing and state management', and 'Generates JSDoc-typed code with @typedef, @param, and @returns annotations'. | 3 / 3 |
Completeness | Clearly answers both what (creates components, builds composables, configures Vite, generates JSDoc-typed code) AND when with explicit 'Use when...' clause covering four distinct trigger scenarios including JS-only Vue projects, JSDoc requirements, Vue 2 migration, and team preferences. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Vue 3', 'JavaScript', 'no TypeScript', 'JSDoc', 'Vite', 'Composition API', 'Vue 2 Options API', 'vanilla JavaScript', '.mjs modules', 'prototypes'. These are terms developers naturally use when discussing this stack. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: Vue 3 + JavaScript-only + JSDoc typing is a specific combination. The explicit 'no TypeScript' qualifier and mention of JSDoc annotations clearly distinguishes this from general Vue skills or TypeScript-based Vue skills. | 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 high-quality skill that efficiently teaches Vue 3 development with JavaScript and JSDoc typing. It excels in providing concrete, executable examples while maintaining excellent organization through progressive disclosure. The workflow includes proper validation checkpoints for both linting and testing, making it robust for real-world use.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with Vue and JavaScript. No unnecessary explanations of basic concepts; every section provides actionable, specific guidance without padding. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for components, composables, and typedef patterns. The examples are complete with proper imports, annotations, and realistic use cases. | 3 / 3 |
Workflow Clarity | The core workflow has clear numbered steps with explicit validation checkpoints (ESLint verification, test re-runs until green). Feedback loops are present for both annotation validation and testing. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear reference table pointing to topic-specific files, plus cross-references to shared vue-expert resources. Content is appropriately split between overview and detailed references. | 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.
5b76101
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.