vuejs-project-starter

Scaffold a Vue 3.5+ project with Composition API (`<script setup>`), Pinia stores, Vue Router 4, TypeScript, Vite, and auto-imports via unplugin.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./frontend/vuejs-project-starter/SKILL.md

Quality

Content

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

The body is highly actionable with executable, copy-paste-ready code for the full Vue stack, and offers a clear post-scaffold checklist. It is weakened by inlining several full pattern examples that would be better placed in separate reference files, which hurts both conciseness and progressive disclosure.

Suggestions

Move the more advanced pattern examples (Pinia store, composable, provide/inject, watchers, teleport) into separate reference files under references/ and link to them from a concise 'Essential Patterns' overview.

Trim redundant explanatory comments that restate Vue concepts Claude already knows (e.g. the inject undefined note) to improve token efficiency.

Add an explicit end-to-end workflow section tying scaffold → first steps → verification into a single guided path with validation checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and the code examples earn their place, but it includes inline reference-style content (full Pinia store, composable, watchers, teleport, provide/inject) that pads the overview with material Claude already knows and that could live in separate reference files.	3 / 5
Actionability	Copy-paste-ready scaffold commands, a complete vite.config, router, store, composable, and component examples all directly executable; common commands and first-steps are concrete and specific.	5 / 5
Workflow Clarity	'First Steps After Scaffold' gives a clear numbered sequence with verification steps (`npm run type-check`, 'Verify the app loads'), but the overall flow from scaffold to running app is presented as parallel sections rather than one guided path, leaving minor sequencing gaps.	4 / 5
Progressive Disclosure	There is section structure, but no bundle files exist and the SKILL.md inlines substantial reference material (multiple full pattern implementations) that would belong in separate reference files; references are not signaled or split out.	3 / 5
	Total	15 / 20 Passed

Description

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

The description is highly specific and clearly distinct, naming a concrete Vue stack. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which limits completeness and slightly narrows trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when scaffolding or bootstrapping a new Vue 3 frontend project, or when the user asks to set up Vue with Pinia, Vue Router, and TypeScript.'

Include common natural synonyms and the version-less term (e.g. 'Vue 3', 'frontend project', 'bootstrap a Vue app') to broaden trigger-term coverage.

Keep the existing concrete stack list — it is the strongest part of the description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and stack specifics — 'Scaffold a Vue 3.5+ project with Composition API (`<script setup>`), Pinia stores, Vue Router 4, TypeScript, Vite, and auto-imports via unplugin' — comprehensive coverage of what it produces.	5 / 5
Completeness	It clearly states 'what' the skill does (scaffolds a specific Vue stack) but contains no 'Use when...' clause or explicit trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural terms like 'Scaffold', 'Vue', 'Pinia stores', 'Vue Router', 'TypeScript', 'Vite' are present, but it lacks synonyms/variations (e.g. 'Vue 3', 'frontend project', 'bootstrap') that a user might naturally say.	4 / 5
Distinctiveness Conflict Risk	The specific Vue 3.5+/Pinia/Vue Router/Vite/unplugin combination carves a clear niche unlikely to trigger for unrelated skills, with minimal conflict risk.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: achreftlili/deep-dev-skills
Path: frontend/vuejs-project-starter/SKILL.md
Commit: 181fcbc

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.