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 extremely weak—it is essentially a title repeated with boilerplate category metadata. It provides no concrete actions, no natural trigger terms beyond the skill name itself, and no guidance on when Claude should select this skill. It would be nearly indistinguishable from any other Vue-related skill in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Vue 3 composables with reactive state, lifecycle hooks, and TypeScript support following Composition API patterns.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a composable, build reusable Vue logic, write a useXxx function, or work with the Vue Composition API.'
Include common user-facing keywords and file/concept variations such as 'composable', 'custom hook', 'Composition API', 'reactive logic', 'Vue 3', 'useXxx pattern' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names 'Vue Composable Creator' but does not describe any concrete actions. There is no mention of what the skill actually does—no verbs like 'creates', 'generates', 'extracts', etc. It is essentially just a label repeated. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'vue composable creator' repeated twice. It misses natural user phrases like 'create a composable', 'Vue composition API', 'custom hook', 'reusable logic', 'useXxx', or 'Vue 3 composable'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Vue Composable' does narrow the domain somewhat compared to generic frontend skills, but without specific actions or triggers, it could still overlap with general Vue development skills or other frontend composition tools. | 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 an empty placeholder with no substantive content. It contains no Vue composable patterns, no code examples, no concrete instructions, and no references to supporting materials. It reads as auto-generated boilerplate that provides zero value beyond what Claude already knows about Vue composables.
Suggestions
Add concrete, executable Vue 3 composable code examples (e.g., a useCounter, useFetch, or useLocalStorage composable) with TypeScript types and proper ref/reactive usage.
Define a clear workflow for creating composables: 1) identify shared logic, 2) extract into composable function, 3) define return types, 4) write unit tests, with validation at each step.
Remove all generic boilerplate sections (Purpose, When to Use, Example Triggers) and replace with actionable content like composable naming conventions, reactivity patterns, and common pitfalls.
Include specific patterns such as composable composition, lifecycle hook usage within composables, and SSR considerations with concrete code snippets.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the trigger phrase 'vue composable creator' excessively, and provides zero domain-specific information. Every section is padded with generic text. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code examples, no composable patterns, no API usage, no executable commands. The content only vaguely describes what the skill could do without actually doing any of it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | There are no references to supporting files, no bundle files exist, and the content is a monolithic block of generic placeholder text with no meaningful structure or 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
13d35b8
- 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.