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.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill vue-component-generator

What are skills?

Overall
score

19%

Review — 4%

Does it follow best practices?

Validation — 11 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Activation

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 wasn't customized.

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 triggers: 'Use when the user asks to create Vue components, .vue files, Vue templates, or needs help with Vue component structure'

Add varied trigger terms users would naturally say: 'vue component', 'create vue', '.vue file', 'vue template', 'vue SFC', 'composition API 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 skills.	2 / 3
	Total	5 / 12 Passed

Implementation

This skill content is essentially a placeholder template with no actual Vue component generation guidance. It contains only generic meta-descriptions about what the skill claims to do, without any concrete code examples, component patterns, CLI commands, or actionable instructions. The content would be completely unhelpful for actually generating Vue components.

Suggestions

Add executable Vue component code examples showing common patterns (e.g., Composition API setup, props/emits, slots)

Include specific CLI commands for scaffolding components (e.g., using Vue CLI or Vite)

Provide a clear workflow: 1) Define component purpose, 2) Generate template structure, 3) Add script logic, 4) Style with scoped CSS

Replace generic capability claims with actual Vue-specific guidance like naming conventions, file structure, and TypeScript integration patterns

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual Vue-specific information.	1 / 3
Actionability	There is zero concrete guidance - no Vue component code, no CLI commands, no actual patterns or examples. The content describes what the skill supposedly does rather than providing any executable instructions.	1 / 3
Workflow Clarity	No workflow is defined at all. There are no steps for generating Vue components, no validation checkpoints, and no actual process to follow. The 'Capabilities' section lists abstract claims without any implementation details.	1 / 3
Progressive Disclosure	The content is a monolithic block of generic text with no references to detailed documentation, no links to examples, and no structured navigation to additional resources. Everything is surface-level with nowhere to go deeper.	1 / 3
	Total	4 / 12 Passed

Validation

69%

Warnings & errors only

Validation — 11 / 16 Passed

Validation for skill structure

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
body_steps	No step-by-step structure detected (no ordered list); consider adding a simple workflow	Warning

	Total	11 / 16 Passed

Reviewed

22 days ago

Table of Contents

Activation Implementation Validation

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.