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.
36
3%
Does it follow best practices?
Impact
96%
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-composable-creator/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 title with no substantive content. It lacks concrete actions, natural trigger terms, and any 'Use when...' guidance. It would be nearly impossible for Claude to reliably select this skill from a pool of similar frontend development skills.
Suggestions
Add specific concrete actions such as 'Creates reusable Vue 3 composable functions, extracts shared reactive logic from components, generates composables with proper lifecycle hook management'.
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user asks to create a Vue composable, extract reusable logic, build a use* function, work with Vue Composition API, or refactor component logic into shared composables'.
Include common keyword variations users might say: 'composable', 'composition API', 'useX function', 'Vue 3 hook', 'reactive logic extraction', '.vue composable file'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Vue Composable Creator') but does not describe any concrete actions like 'creates reusable composable functions', 'extracts component logic into composables', or 'generates reactive state management hooks'. It is essentially just a title repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title and completely lacks a 'when should Claude use it' clause. There is no explicit trigger guidance or use-case description. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'vue composable creator' repeated twice. It misses natural user phrases like 'composable', 'Vue composition API', 'reusable hook', 'use function', 'extract logic', 'reactive state', or 'Vue 3 composable'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Vue Composable' provides some specificity that distinguishes it from generic frontend skills, but without concrete actions or clear triggers, it could overlap with other Vue-related or frontend development 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 is essentially an empty placeholder with no substantive content. It repeatedly references 'vue composable creator' without ever defining what a Vue composable is, how to create one, or providing any code examples. The entire body is self-referential metadata that provides zero actionable value to Claude.
Suggestions
Add concrete, executable Vue 3 composable code examples (e.g., a useCounter or useFetch composable) with TypeScript types and proper ref/reactive usage.
Define a clear workflow for creating composables: identify shared logic → extract to composable function → define reactive state and return values → integrate into components.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching the actual technique.
Include specific patterns and anti-patterns for Vue composables, such as proper lifecycle hook usage, cleanup with onUnmounted, and when to use ref vs reactive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague information about 'vue composable creator' without teaching anything Claude doesn't already know. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no composable patterns, no API usage, no executable commands. The skill describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill mentions 'step-by-step guidance' but never delivers any steps. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive wall of meta-descriptions with no meaningful structure. There are no references to detailed files, no quick-start section, and no organized navigation to deeper content. | 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
3e83543
- 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.