vue-expert-js
Use when building Vue 3 applications with JavaScript only (no TypeScript). Invoke for JSDoc typing, vanilla JS composables, .mjs modules.
Install with Tessl CLI
npx tessl i github:jeffallan/claude-skills --skill vue-expert-jsOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
72%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at distinctiveness and trigger terms, clearly carving out a JavaScript-only Vue 3 niche with relevant keywords. However, it lacks concrete action verbs describing what the skill actually does - it tells Claude when to use it but not what capabilities it provides. Adding specific actions would significantly improve the description.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Creates Vue 3 components, sets up composables, configures Vite builds' before the 'Use when' clause
Expand the capability description to include specific tasks like 'scaffold projects', 'write reactive state management', or 'implement component patterns'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Vue 3 applications with JavaScript) and mentions some specific elements (JSDoc typing, vanilla JS composables, .mjs modules), but doesn't list concrete actions like 'create components', 'set up routing', or 'configure build tools'. | 2 / 3 |
Completeness | Has a 'Use when' clause addressing when to invoke, but the 'what does this do' portion is weak - it describes the context/constraints (JS only, no TypeScript) rather than concrete capabilities or actions the skill performs. | 2 / 3 |
Trigger Term Quality | Includes good natural keywords users would say: 'Vue 3', 'JavaScript', 'no TypeScript', 'JSDoc', 'composables', '.mjs modules'. These cover common variations and terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche: Vue 3 + JavaScript-only (explicitly excluding TypeScript). The combination of 'no TypeScript', 'JSDoc typing', and '.mjs modules' creates distinct triggers unlikely to conflict with TypeScript-based Vue skills or other frameworks. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has good organizational structure and appropriate progressive disclosure through its reference table, but critically lacks concrete code examples showing JSDoc typing patterns in Vue 3 components. The content tells Claude what to do without showing how, making it difficult to execute consistently. The role definition and usage scenarios add tokens without adding value.
Suggestions
Add 2-3 executable code examples showing JSDoc typing in Vue components: a component with typed props using @type, a composable with @typedef and @param, and a Pinia store with JSDoc annotations
Remove or significantly condense the 'Role Definition' and 'When to Use This Skill' sections as Claude can infer these from context
Add a concrete example in the Output Templates section showing the actual file structure and JSDoc syntax expected
Include a validation step in the workflow for checking JSDoc coverage (e.g., using VS Code's JS type checking or a linting rule)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'Role Definition' that restates the description, and 'When to Use This Skill' lists scenarios Claude can infer. However, the constraints and reference table are appropriately concise. | 2 / 3 |
Actionability | The skill lacks any concrete code examples showing JSDoc typing in Vue components, composables, or the actual syntax patterns. It describes what to do ('Use JSDoc comments') but never shows executable examples of how. | 1 / 3 |
Workflow Clarity | The 5-step core workflow is listed but lacks specificity and validation checkpoints. Steps like 'Analyze requirements' and 'Design architecture' are vague without concrete guidance on what constitutes success at each step. | 2 / 3 |
Progressive Disclosure | Good structure with clear reference table pointing to external files one level deep. Appropriately defers shared Vue concepts to vue-expert skill and organizes content into logical sections with clear navigation. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 12 / 16 Passed | |
- 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.