vue-composable-creator
Vue Composable Creator - Auto-activating skill for Frontend Development. Triggers on: vue composable creator, vue composable creator Part of the Frontend Development skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill vue-composable-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It relies entirely on the skill name without explaining what creating a Vue composable entails, what specific actions the skill performs, or when Claude should select it over other frontend development skills.
Suggestions
Add specific actions the skill performs, e.g., 'Creates reusable Vue 3 composables with reactive state, lifecycle hooks, and TypeScript support'
Include a 'Use when...' clause with natural trigger terms like 'extract logic into composable', 'create custom hook', 'reusable reactive function', 'composition API helper'
Add variations of terminology users might use: 'Vue hooks', 'composition functions', 'shared reactive logic', 'useXxx pattern'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Vue Composable Creator' without describing any concrete actions. It doesn't explain what creating a composable involves or what specific capabilities are provided. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('vue composable creator' repeated twice) and overly specific. Missing natural variations users would say like 'create composable', 'vue hooks', 'reusable logic', 'composition API', or 'extract composable'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Vue Composable' is somewhat specific to Vue.js development, the lack of detail about what distinguishes this from general Vue development skills or other frontend composition patterns creates potential overlap. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is entirely generic boilerplate with no Vue-specific guidance whatsoever. It fails to provide any actionable information about creating Vue composables—no code examples, no patterns, no API references, and no workflow. The content could apply to virtually any topic by swapping the phrase 'vue composable creator'.
Suggestions
Add executable Vue 3 composable code examples showing the Composition API pattern (e.g., a useCounter or useFetch composable)
Include the specific structure of a composable: reactive state, computed properties, methods, and return values
Provide a clear workflow: 1) Define reactive state, 2) Create computed/watchers, 3) Define methods, 4) Return public API
Remove all generic boilerplate text and replace with Vue-specific patterns, naming conventions, and best practices
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Vue composables. Phrases like 'automated assistance' and 'industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The skill describes what it does in abstract terms but never shows how to actually create a Vue composable. | 1 / 3 |
Workflow Clarity | No steps, sequences, or processes are defined. The content only lists vague capabilities without any workflow for creating composables. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials, examples, or references. No navigation to deeper content exists. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%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
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.