CtrlK
BlogDocsLog inGet started
Tessl Logo

vue

Use when editing .vue files, creating Vue 3 components, writing composables, or testing Vue code - provides Composition API patterns, props/emits best practices, VueUse integration, and reactive destructuring guidance

89

1.36x
Quality

85%

Does it follow best practices?

Impact

97%

1.36x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized reference skill with clear progressive disclosure, a useful task-to-file routing table, and an executable quick-start example. The three near-duplicate file listings (Quick Reference, Loading Files, Available Guidance) add redundancy, and the version-performance line is mild padding.

Suggestions

Consolidate the three overlapping file lists (Quick Reference table, Loading Files checklist, Available Guidance) into one navigation section to reduce redundancy and token cost.

Trim the version-performance marketing line ('-56% memory, 10x faster array tracking') or move it to a 'gotchas/version notes' reference file since time-sensitive stats age quickly.

Add one or two more inline code snippets (e.g., a composable skeleton) so the body is more immediately actionable before sub-files must be loaded.

DimensionReasoningScore

Conciseness

Mostly lean overview that assumes Claude knows Vue basics, but the 'Current stable: Vue 3.5+... -56% memory, 10x faster array tracking' version-performance detail is borderline token padding that could be trimmed.

4 / 5

Actionability

Provides a copy-paste executable Quick Start SFC example and a task-to-file routing table, but offers only a single in-body example and relies on sub-files for the rest.

4 / 5

Workflow Clarity

A clear selection workflow via 'When to Use', the Quick Reference table, and the Loading Files checklist; this single-purpose reference needs no destructive-op validation, though the navigation between the three overlapping file lists could be consolidated.

4 / 5

Progressive Disclosure

Excellent one-level-deep structure: an overview SKILL.md pointing to 10 verified real reference files, signaled three ways (Quick Reference table, Loading Files checklist, Available Guidance descriptions), with an explicit 'DO NOT load all files at once' instruction.

5 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concrete description that names specific Vue 3 actions and capabilities with an explicit 'Use when' trigger and clear disambiguation from adjacent skills. Only minor room to add synonyms like 'Vue.js' and 'single-file components'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('editing .vue files, creating Vue 3 components, writing composables, or testing Vue code') plus specific capabilities (Composition API patterns, props/emits best practices, VueUse integration, reactive destructuring), giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' ('provides Composition API patterns, props/emits best practices...') and 'when' with a clear 'Use when editing .vue files, creating...' trigger clause.

5 / 5

Trigger Term Quality

Includes natural terms users say ('.vue files', 'Vue 3 components', 'composables', 'testing Vue code'), but misses common synonyms like 'Vue.js' or the bare '.vue' extension and 'single-file components'.

4 / 5

Distinctiveness Conflict Risk

Clear Vue-specific niche with distinct triggers; body further disambiguates against sibling skills (nuxt, nuxt-ui, reka-ui, vueuse), minimizing wrong-skill activation.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
onmax/nuxt-skills
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.