vue-router-best-practices

Vue Router 4 patterns, navigation guards, route params, and route-component lifecycle interactions.

Quality

53%

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 ./skills/vue-router-best-practices/SKILL.md

Quality

Content

50%

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

The body is commendably concise and well-categorized as a gotchas index, but it provides no executable guidance and its progressive-disclosure references are dead links to missing files, leaving the skill unable to actually resolve any of the listed problems.

Suggestions

Add minimal executable inline guidance for the most common issues (e.g., the correct Composition API guard pattern and the async/await example) instead of relying entirely on external reference files.

Create the missing 'references/' bundle directory and the referenced router-*.md files, or remove the dead links and inline the essential content.

Fix the reference path ('reference/' should match the actual bundle directory name) so the pointers resolve, and verify each link target exists.

Dimension	Reasoning	Score
Conciseness	The body is a lean index of one-line problem statements with pointers, with no padding and no explanation of concepts Claude already knows; every line earns its place.	3 / 3
Actionability	The body contains no code, commands, or executable guidance — only problem descriptions ('Users trapped in infinite redirect loops') and 'See [reference]' pointers; it describes rather than instructs, matching the lowest anchor.	1 / 3
Workflow Clarity	Grouping entries under 'Navigation Guards', 'Route Lifecycle', and 'Setup' provides some structure, but there is no real sequenced workflow and the actual resolutions are deferred to reference files rather than stated inline.	2 / 3
Progressive Disclosure	The references are clearly signaled and one level deep in form, but the referenced 'reference/*.md' files do not exist (no references/scripts/assets bundle directories are present, and the path uses 'reference/' rather than 'references/'), so navigation is broken against the actual bundle structure.	2 / 3
	Total	8 / 12 Passed

Description

57%

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 names a clear, distinct Vue Router 4 niche with relevant natural terms, but it reads as a topic list rather than a statement of concrete actions and lacks any explicit 'when to use' trigger guidance.

Suggestions

Lead with concrete actions (e.g., 'Diagnose and fix Vue Router 4 navigation guard issues, configure route params, and resolve route-component lifecycle bugs') instead of noun-phrase topic lists.

Add an explicit trigger clause such as 'Use when debugging Vue Router navigation guards, route param changes, or component lifecycle issues in Vue 3 apps.'

Broaden natural trigger terms to include variations a user might say, e.g. 'Vue Router', 'vue-router', 'routing', 'beforeRouteEnter', 'redirect loops'.

Dimension	Reasoning	Score
Specificity	Names the Vue Router 4 domain and specific topics ('navigation guards, route params, and route-component lifecycle interactions'), but these are subject areas rather than concrete actions; there are no verbs describing what the skill does.	2 / 3
Completeness	It clearly states what the skill covers but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	'Vue Router 4', 'navigation guards', and 'route params' are terms a Vue developer would naturally say, but coverage is narrow with no common variations or synonyms, so it stops short of the broad spread expected at the top level.	2 / 3
Distinctiveness Conflict Risk	The 'Vue Router 4' niche is specific and unlikely to overlap with unrelated skills, so the risk of triggering for the wrong skill is low.	3 / 3
	Total	9 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 8 missing	Warning

	Total	14 / 16 Passed

Repository: vuejs-ai/skills
Path: skills/vue-router-best-practices/SKILL.md
Commit: c9d355f

Reviewed: about 12 hours 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.