author-vitest-tests

Use when writing or adding Vitest tests for Positron src/vs/ or extensions/ code, checking a branch/PR for test-coverage gaps, or testing React components with RTL.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

81%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 highly actionable, well-sequenced multi-phase workflow with strong validation checkpoints and feedback loops, and it appropriately offloads detail to referenced rules files. Its main weakness is conciseness: repeated mandatory-confirmation emphasis and a Hard Rules section that restates guidance already present in Phase 2.

Suggestions

Collapse the repeated 'stop and wait for confirmation' emphasis into a single authoritative statement in Phase 2's Draft-the-plan section; remove the duplicated restatements elsewhere.

Trim the Hard Rules section to only rules not already stated in Phase 2 (e.g., keep 'no E2E', 'no upstream modification', 'no auto-commit') and drop 'Test for regressions, not coverage' / 'Don't pad for category coverage' which rephrase the partition guidance above.

Consider extracting the full analysis-subagent prompt and the test-plan template into a bundled reference file so the SKILL.md body reads as a tighter overview.

Dimension	Reasoning	Score
Conciseness	The body mostly assumes Claude's competence (no explaining what Vitest/RTL is) and is operational, but repeats the 'stop and wait for confirmation' / 'Do not skip this step' emphasis and restates Phase 2 partition guidance in the Hard Rules, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean level 4.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (gh pr diff, git fetch, grep -rq, npx vitest run, npm run test:positron:check-ts, npx eslint) plus concrete file paths and Agent() invocations, matching the 'fully executable, copy-paste ready, covers common cases' anchor.	5 / 5
Workflow Clarity	A clear three-phase sequence (Analysis, Writing, Review) with explicit validation checkpoints (run test, type-check, eslint, builder-enforcement grep, single full-suite run) and feedback loops ('iterate on missing stubs', fix and re-validate) plus checklists, matching the top anchor.	5 / 5
Progressive Disclosure	Well-organized phase sections with one-level-deep, clearly signaled links to external repo files (vitest-tests.md, vitest-rtl.md, positronTestContainer.ts, review skill) and detailed patterns kept out of the body, but the body is a dense single ~200-line file so it sits at 'good structure, references mostly clear, minor organization gaps' rather than the cleanly-split level 5.	4 / 5
	Total	17 / 20 Passed

Description

87%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 a strong, specific trigger statement that clearly defines both what the skill does and when to invoke it, tightly scoped to the Positron Vitest niche with minimal conflict risk. Its only weakness is slight under-coverage of natural synonyms.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('writing or adding Vitest tests', 'checking a branch/PR for test-coverage gaps', 'testing React components with RTL'), with only minor coverage gaps, matching the 'lists several specific actions' anchor rather than the fully comprehensive level 5.	4 / 5
Completeness	Explicitly answers both what (the three testing actions) and when ('Use when writing or adding Vitest tests... checking a branch/PR... or testing React components'), matching the 'clearly and explicitly answers both what AND when with concrete trigger phrases' anchor.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('writing or adding Vitest tests', 'test-coverage gaps', 'React components', 'RTL') with good coverage, though a few synonyms like 'unit tests' are missing, fitting the 'good keyword coverage, a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	The Positron-specific Vitest niche with distinct triggers (Vitest, src/vs/, extensions/, RTL) has minimal conflict risk, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	18 / 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
relative_links	Relative link issues: 4 suspicious	Warning

	Total	15 / 16 Passed

Repository: posit-dev/positron
Path: .claude/skills/author-vitest-tests/SKILL.md
Commit: 10323ef

Reviewed: 38 minutes 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.