CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vue-router-best-practices

Use when adding routes or navigation guards with Vue Router 4 or 5: async guards without `next()`, redirect loops, components that keep stale data when only the params change, and `beforeRouteEnter` without `this`.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/vue-router-best-practices/SKILL.md

The canonical home for this skill is vue-router-best-practices in vuejs-ai/skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 an extremely lean, well-organized index in the ideal progressive-disclosure shape, but it is an empty shell: no inline actionable guidance exists and every reference link is dangling because the target files are missing from the bundle. Overlapping same-route/param-change triggers further blur which reference to consult.

Suggestions

Inline a minimal quick-reference pattern (e.g., the async guard without `next()` and a `watch` on `$route.params` for param changes) so the skill yields actionable guidance without following links.

Ship the eight referenced files, or fix the `reference/` paths to an existing `references/` directory — every link currently dead-ends, breaking progressive disclosure entirely.

Disambiguate the overlapping triggers: "Navigating between same route with different params" and "Stale data when navigating between same route" are near-identical symptoms routed to two different files; clarify when to use each.

DimensionReasoningScore

Conciseness

At ~17 lines the body is a pure symptom→pointer index with zero padding, no explanation of concepts Claude already knows, and no fluff; every bullet maps a specific trigger to a target file. Clearly matches the anchor-5 'lean and efficient; every token earns its place' pattern.

5 / 5

Actionability

The body contains no code, commands, or inline patterns — every line is a "See [file]" pointer, and none of the eight referenced `reference/router-*.md` files exist in the bundle, so no executable guidance is reachable. It avoids a 1 only because the symptom→file mapping is itself specific, concrete navigation rather than vague abstraction.

2 / 5

Workflow Clarity

The lookup structure is organized into clear categories (Navigation Guards, Route Lifecycle, Setup), but overlapping triggers create ambiguity — "Navigating between same route with different params" and "Stale data when navigating between same route" are near-identical symptoms pointing to two different files. There is no guidance on what to do after consulting a reference, and the links dead-end since the target files are absent.

3 / 5

Progressive Disclosure

As written, the body is the textbook one-level-deep index pattern (clear sections, well-signaled references, symptom-based navigation), but the eight referenced `reference/router-*.md` files do not exist — there is no `references/` or `reference/` directory in the bundle — so the promised detail layer is absent and navigation fails at the first hop. Scored between the strong written structure (4-5) and the broken actual disclosure (2).

3 / 5

Total

13

/

20

Passed

Description

70%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 lean, highly distinctive trigger description with concrete Vue Router terminology and an explicit 'Use when' clause. Its main weakness is the missing capability statement — it says when to fire but never says what the skill does, capping completeness and specificity below their top anchors.

Suggestions

Lead with an explicit capability statement before the 'Use when' clause, e.g., "Apply Vue Router best-practice patterns for navigation guards, route lifecycle, and production SPA setup. Use when…", to fix the missing 'what'.

Add natural synonyms users actually say — the "vue-router" package name, "watch route params", "router.push" — to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description lists several concrete, specific conditions ("async guards without `next()`", "redirect loops", "components that keep stale data when only the params change", "`beforeRouteEnter` without `this`") anchored to a named domain ("Vue Router 4 or 5"). It falls short of a 5 because these are triggering scenarios rather than concrete actions the skill performs, and coverage has gaps (e.g., lazy loading, router-link, scroll behavior).

4 / 5

Completeness

The 'when' is explicit and detailed ("Use when adding routes or navigation guards with Vue Router 4 or 5: …"), but the 'what' is never stated — the enumerated gotchas only imply the skill's capabilities. This is the mirror image of anchor 3 (clear 'what', weak 'when'), and richer than anchor 2's bare 'when'-only example, so it sits at 3 rather than 4 (which requires both explicitly present).

3 / 5

Trigger Term Quality

Good natural keyword coverage — a Vue developer would genuinely say "adding routes", "navigation guards", "redirect loop", "beforeRouteEnter", "params". Not a 5 because common synonyms and variations are missing, such as the "vue-router" package name, "watch route params", or "router.push".

4 / 5

Distinctiveness Conflict Risk

"Vue Router 4 or 5" pins a clear niche with distinct, unambiguous triggers (beforeRouteEnter, next(), redirect loops); minimal risk of triggering for the wrong skill. Clearly matches the anchor-5 example's clear-niche pattern.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 8 possibly missing (reference/router-beforeenter-no-param-trigger.md, reference/router-beforerouteenter-no-this.md, reference/router-guard-async-await-pattern.md, reference/router-navigation-guard-infinite-loop.md, reference/router-navigation-guard-next-deprecated.md, +3 more)

Warning

Total

15

/

16

Passed

Repository

onmax/nuxt-skills

Path

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