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.
95
92%
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 hits all the marks. It provides highly specific capabilities, includes abundant natural trigger terms that developers would use, explicitly addresses both what the skill does and when to use it, and carves out a very distinct niche (Vue 3 + JS-only + JSDoc) that minimizes conflict risk 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'. These are highly specific and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates Vue 3 components, builds composables, configures Vite, generates JSDoc-typed code) and 'when' with an explicit 'Use when...' clause covering multiple trigger scenarios including building Vue 3 apps without TypeScript, JSDoc-based type hints, migrating from Vue 2, and teams preferring vanilla JS. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Vue 3', 'JavaScript only', 'no TypeScript', 'JSDoc', 'Composition API', 'Vue 2', 'Options API', 'Vite', 'vanilla JavaScript', '.mjs modules', 'quick prototypes'. These are terms a developer would naturally use when seeking this kind of help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: Vue 3 + JavaScript-only (no TypeScript) + JSDoc typing. The repeated emphasis on 'no TypeScript' and JSDoc-based approach clearly distinguishes this from general Vue skills or TypeScript-based Vue skills. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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 skill with excellent actionability through concrete, executable code examples and good progressive disclosure via a reference table. The workflow includes appropriate validation checkpoints. Minor weaknesses include some redundancy in the constraints section that restates what's already demonstrated in examples, and the Output Templates and Knowledge Reference sections add little value.
Suggestions
Remove or tighten the 'Output Templates' section — it's vague and doesn't add actionable guidance beyond what the code examples already show.
Trim the 'Constraints' MUST DO list to only items not already obvious from the code examples (e.g., remove 'Use Composition API with <script setup>' since every example demonstrates this).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy — the constraints section restates things already clear from the examples (e.g., 'Use Composition API with <script setup>' is obvious from every code example). The 'Knowledge Reference' line at the end is just a keyword list that adds little value. The Output Templates section is vague filler. | 2 / 3 |
Actionability | Provides fully executable, copy-paste-ready code examples for components, composables, and shared typedefs. The JSDoc patterns are concrete and complete, showing real Vue 3 syntax with proper annotations. The examples cover the key use cases comprehensively. | 3 / 3 |
Workflow Clarity | The core workflow has clear sequencing with validation checkpoints — step 3 includes running ESLint to verify JSDoc coverage with a fix-before-proceeding gate, and step 4 includes a feedback loop (re-run until green). For a skill that's primarily about code patterns rather than destructive operations, this is well-structured. | 3 / 3 |
Progressive Disclosure | Excellent use of a reference table with clear 'Load When' conditions, plus cross-references to shared vue-expert resources. The SKILL.md serves as a concise overview with inline examples for the most common patterns, deferring detailed guidance to well-organized reference files one level deep. | 3 / 3 |
Total | 11 / 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.
3d95bb1
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.