CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vitest-test-runner

Run the Vitest test suite for the @workspace/tc-reference application using `pnpm --filter @workspace/tc-reference test`.

Quality

74%

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 ./.agents/skills/vitest-test-runner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 tight, executable workflow: one exact command, a clear sequence with a fix-and-re-run feedback loop, and well-organized sections appropriate for a simple single-purpose skill. The only weaknesses are minor over-explanation in the analysis step and missing guidance for common variations like running a single test file.

DimensionReasoningScore

Conciseness

The body is lean with no concept explanations or padding, but step 2 over-explains what Claude already knows ("Identify which test suites and specific cases failed", "Look at the error stack traces to understand the root cause"). This matches 'efficient; minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place of anchor 5.

4 / 5

Actionability

The exact executable command `pnpm --filter @workspace/tc-reference test` is copy-paste ready and the analyze-fix-rerun-report loop is concrete, matching 'mostly executable guidance; concrete code or commands with minor gaps'. It stops short of anchor 5 because it offers no variants for common cases, such as running a single test file or one-shot (non-watch) execution.

4 / 5

Workflow Clarity

The sequence run → analyze → fix → re-run → report is clearly ordered, with an explicit validation feedback loop ("Fix the failing code or update the test files... then re-run to confirm all tests pass"). Running tests is non-destructive, so no destructive-operation cap applies, and the loop matches anchor 5's fix-and-retry pattern.

5 / 5

Progressive Disclosure

The skill is under 50 lines, has no need for external references (none exist in the bundle), and is organized into clear 'When to Use' and 'Steps' sections. Per the simple-skill guideline, this qualifies for a 5 with well-organized sections alone.

5 / 5

Total

18

/

20

Passed

Description

53%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 precise and honest about a single, well-scoped action, and includes the exact command, giving it strong distinctiveness. Its main weakness is the absence of any 'Use when...' trigger clause and missing natural keyword variations, which cap completeness and trigger-term quality at the midpoint.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks to run tests, run the Vitest suite, or check that changes to tc-reference or shared library packages didn't break anything."

Include natural keyword variations such as "unit tests", "run tests", and "test failures" so the description matches how users actually phrase the request.

Optionally mention the additional actions the skill covers (analyzing failures, re-running until green, reporting pass/fail statistics) to raise specificity beyond a single action.

DimensionReasoningScore

Specificity

"Run the Vitest test suite for the @workspace/tc-reference application using `pnpm --filter @workspace/tc-reference test`" names one concrete action with the exact command, matching the anchor for 1-2 concrete actions that are not comprehensive. It does not list several specific actions (e.g., analyzing failures, re-running, reporting), so it does not reach anchor 4.

3 / 5

Completeness

The 'what' is clear (run the test suite, with the exact command), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. This is the anchor-3 pattern: clear what, missing or only weakly implied when.

3 / 5

Trigger Term Quality

Natural keywords like "Vitest", "test suite", and "test" are present, but common variations users would say — "unit tests", "run tests", "test failures", "coverage" — are missing, matching the 'some relevant keywords but missing common variations' anchor. It falls short of anchor 4's 'good keyword coverage' exemplified by multiple distinct natural terms.

3 / 5

Distinctiveness Conflict Risk

The description is scoped to a specific package (@workspace/tc-reference), tool (Vitest), and exact command, making it mostly distinct with only minor overlap risk against generic test-running requests. It lacks the explicit distinct trigger phrases of anchor 5, and is well above the generic overlap of anchor 3.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/vitest-test-runner/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.