vue-component-generator
Vue Component Generator - Auto-activating skill for Frontend Development. Triggers on: vue component generator, vue component generator Part of the Frontend Development skill category.
35
Quality
3%
Does it follow best practices?
Impact
95%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/05-frontend-dev/vue-component-generator/SKILL.mdQuality
Discovery
7%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 description is essentially a placeholder that provides almost no useful information for skill selection. It relies entirely on the skill name without explaining capabilities, use cases, or providing meaningful trigger terms. The redundant trigger term and boilerplate structure suggest auto-generated content that needs substantial human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Creates Vue 3 single-file components with Composition API, generates props/emits definitions, scaffolds component templates with TypeScript support'
Include a proper 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user asks to create Vue components, scaffold .vue files, set up Vue templates, or work with Vue 3 Composition API'
Add diverse trigger term variations users would naturally say: 'vue component', 'vue template', '.vue file', 'vue SFC', 'create component in vue', 'vue 3 component'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Vue Component Generator' without listing any concrete actions. It doesn't specify what the skill actually does - no mention of creating components, templates, props, state management, or any specific Vue-related operations. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. The 'Triggers on' section is not a proper 'Use when...' clause with meaningful context. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('vue component generator' listed twice) and overly narrow. Missing natural variations users would say like 'create vue component', 'vue template', '.vue file', 'vue SFC', 'single file component', or 'vue setup'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Vue' provides some specificity that distinguishes it from generic component generators, the lack of detail about what Vue-specific features it handles could cause overlap with general frontend or JavaScript component skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is entirely template boilerplate with no actual Vue component generation guidance. It contains zero executable code, no component patterns, no props/emit examples, and no practical information about Vue development. The content describes what a skill 'would do' rather than actually teaching Claude how to generate Vue components.
Suggestions
Add concrete Vue 3 component code examples showing Composition API patterns (setup, ref, computed, etc.)
Include a clear workflow for component generation: 1) Define props interface, 2) Create template structure, 3) Add script setup, 4) Style with scoped CSS
Provide specific examples of common component patterns (form inputs, modals, lists) with copy-paste ready code
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual Vue component templates and best practices
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual Vue-specific information. It explains what the skill does in abstract terms without providing any concrete Vue component generation guidance, wasting tokens on meta-description rather than actionable content. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples are provided. The content only describes what the skill 'could' do in vague terms like 'provides step-by-step guidance' without actually providing any guidance, code snippets, or Vue component patterns. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, sequences, or processes for generating Vue components. The 'Capabilities' section mentions 'step-by-step guidance' but none is actually provided. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no structure pointing to detailed materials, no references to component templates, API documentation, or examples. The 'Related Skills' section mentions a category but provides no actual navigation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
994edc4
- 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.