CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vue-expert

Builds Vue 3 components with Composition API patterns, configures Nuxt 3 SSR/SSG projects, sets up Pinia stores, scaffolds Quasar/Capacitor mobile apps, implements PWA features, and optimises Vite builds. Use when creating Vue 3 applications with Composition API, writing reusable composables, managing state with Pinia, building hybrid mobile apps with Quasar or Capacitor, configuring service workers, or tuning Vite configuration and TypeScript integration.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

Excellent body structure: a sequenced workflow with explicit validate-and-retry loops, a runnable quick example, clear constraints, and a well-signaled one-level reference table covering the whole Vue 3 domain. The only flaw is mild padding in the Knowledge Reference section and the role/attributions lines that could be trimmed for token efficiency.

Suggestions

Remove the "Knowledge Reference" section — it only lists technologies (Vue 3, Pinia, Nuxt 3, VueUse, etc.) that Claude already knows and duplicates the description's coverage.

Trim the "Senior Vue specialist with deep expertise..." opener and the maintainer/documentation attribution lines; they consume tokens without adding actionable guidance.

DimensionReasoningScore

Conciseness

The workflow, constraints, and quick example are efficient, but the "Knowledge Reference" section ("Vue 3 Composition API, Pinia, Nuxt 3, Vue Router 4, Vite, VueUse, TypeScript, Vitest...") is a technology list Claude already knows, and the "Senior Vue specialist with deep expertise" opener and maintainer attribution are padding — anchor 4 (minor trimmable instances), not 5.

4 / 5

Actionability

Fully executable guidance: a correct, copy-paste-ready <script setup> TypeScript example; concrete validation commands ("Run `vue-tsc --noEmit`", "Vue Test Utils and Vitest"); and an explicit output template (component file, composable, Pinia store, explanation of reactivity decisions). This matches anchor 5's copy-paste-ready coverage of the common case.

5 / 5

Workflow Clarity

Six clearly sequenced steps (Analyze → Design → Implement → Validate → Optimize → Test) with two explicit validation feedback loops: "If type errors are found: fix each issue and re-run `vue-tsc --noEmit` until the output is clean before proceeding" and "If tests fail: ... fix accordingly, and re-run until all tests pass" — exactly anchor 5's explicit validation with error-recovery loops.

5 / 5

Progressive Disclosure

A clean overview body with one inline example, plus a Topic/Reference/Load-When table pointing to seven real one-level-deep files (all seven paths exist in references/ and none nest further); the Load-When column gives precise navigation triggers, matching anchor 5.

5 / 5

Total

19

/

20

Passed

Description

88%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 description: it names concrete capabilities across the Vue 3 ecosystem and pairs them with an explicit, multi-scenario "Use when" clause. Trigger coverage is good though it misses a few natural variants, and the Vite/TypeScript tail creates minor overlap risk with adjacent skills.

DimensionReasoningScore

Specificity

Six concrete actions are listed ("Builds Vue 3 components with Composition API patterns", "configures Nuxt 3 SSR/SSG projects", "sets up Pinia stores", "scaffolds Quasar/Capacitor mobile apps", "implements PWA features", "optimises Vite builds") with comprehensive coverage of the Vue 3 domain; no gaps that would drop it to anchor 4.

5 / 5

Completeness

Explicitly answers both what (the six-capability action list) and when ("Use when creating Vue 3 applications with Composition API, writing reusable composables, managing state with Pinia, building hybrid mobile apps with Quasar or Capacitor, configuring service workers, or tuning Vite configuration and TypeScript integration") with concrete trigger phrases, matching anchor 5 exactly.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("Vue 3", "Composition API", "composables", "Pinia", "Quasar", "Capacitor", "service workers", "Nuxt 3"), but a few natural terms are missing such as the ".vue" file extension, "Vue.js", and "Vue Router" — anchor 5 requires synonyms and file extensions, so this fits anchor 4.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly Vue 3 (Pinia, Quasar, Capacitor, Nuxt triggers are unmistakable), but "tuning Vite configuration and TypeScript integration" shares surface with generic build and TypeScript skills (the skill itself lists typescript-pro as related), so anchor 4's "minor overlap risk with closely related skills" fits better than anchor 5's minimal conflict risk.

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Jeffallan/claude-skills

Path

skills/vue-expert/SKILL.md

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.