CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vue-testing-best-practices

Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.

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-testing-best-practices/SKILL.md

The canonical home for this skill is vue-testing-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 a token-efficient, well-organized symptom-based router, but it is an index to nowhere: every one of the eleven referenced reference/*.md files is missing from the bundle, so the skill provides no actual actionable content and navigation fails. The external links (Vue, Vue Test Utils, Vitest, Playwright docs) are the only reachable destinations.

Suggestions

Ship the eleven referenced reference/*.md files in the bundle (or fix their paths) — currently every link in the Testing section dangles.

Add a minimal quick-start snippet in the body (e.g., a basic Vitest + Vue Test Utils component test with mount and an assertion) so the skill retains some actionable guidance even before following references.

Add a brief default path for symptoms that match multiple entries (e.g., "start with the blackbox-approach reference when unsure") so the routing workflow is unambiguous in practice.

DimensionReasoningScore

Conciseness

The body is a lean ~27-line index: one orienting line ("Vue.js testing best practices, patterns, and common gotchas"), eleven symptom→reference bullets, and four external doc links. No padding, no explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

The body contains no code, commands, or concrete steps — only high-level symptom hints like "Tests fail intermittently with race conditions → See [testing-async-await-flushpromises]" pointing at files that are not in the bundle (no reference/ directory exists). This matches minimal high-level guidance with the specific execution steps missing; not a 3 because there is no concrete guidance at all in the body, and the linked details are unreachable.

2 / 5

Workflow Clarity

The symptom→reference routing pattern is unambiguous in form (and no destructive/batch operations require validation checkpoints), but the workflow cannot actually be executed since all eleven referenced reference/*.md files are absent. Not a 2 because the routing structure itself is coherent and well-matched to symptoms; not higher because following any route fails.

3 / 5

Progressive Disclosure

The structure nominally matches the ideal router pattern — a clear overview with clearly signaled, one-level-deep references organized by symptom — but none of the eleven referenced reference/*.md files exist in the bundle (no references/, reference/, scripts/, or assets/ directories), so the disclosure chain is broken end-to-end. This is more than the minor organization gaps of a 4.

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 solid description that names a distinct niche with good natural keyword coverage and an explicit "Use for..." trigger. Its main weakness is that it lists topics via "Covers..." rather than concrete actions, and the when-clause is minimal rather than giving concrete trigger phrases.

Suggestions

Lead with concrete action verbs instead of a topic list, e.g. "Write and debug Vue component tests with Vitest and Vue Test Utils, mock modules and Pinia stores, and set up Playwright E2E suites for Vue apps."

Make the when-clause more specific with trigger phrases, e.g. "Use when writing, running, or debugging tests for Vue components, composables, Vitest setups, or Playwright E2E flows."

DimensionReasoningScore

Specificity

"Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing" names the domain and several specific coverage areas, but these are topics rather than concrete actions — no action verbs like write, debug, or set up. Not a 4 because it never lists specific actions; not a 2 because it goes well beyond merely naming the domain.

3 / 5

Completeness

Both parts are present: "Covers Vitest, Vue Test Utils, component testing, mocking..." answers what, and "Use for Vue.js testing" is an explicit trigger clause, so the missing-trigger cap at 3 does not apply. Not a 5 because the when-clause is thin and near-circular — it lacks concrete trigger phrases like "when writing or debugging Vue component tests".

4 / 5

Trigger Term Quality

Includes natural terms users would say — "Vue.js testing", "Vitest", "Vue Test Utils", "component testing", "mocking", "Playwright", "E2E testing". Not a 5 because common variations like "unit tests", ".spec files", "test my Vue component", or "composables" are missing; clearly above 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

"Vue.js testing" with Vitest, Vue Test Utils, and Playwright is a clear, distinct niche. Not a 5 because it could overlap with a generic Playwright or Vitest skill outside the Vue context; well above the vague overlap risk of 3.

4 / 5

Total

15

/

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: 11 missing

Warning

Total

15

/

16

Passed

Repository

onmax/nuxt-skills

Path

skills/vue-testing-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.