CtrlK
BlogDocsLog inGet started
Tessl Logo

unit-tests

Use when running unit tests in the VS Code repo. Covers the runTests tool, scripts/test.sh (macOS/Linux) and scripts/test.bat (Windows), and their supported arguments for filtering, globbing, and debugging tests.

64

Quality

76%

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 ./.github/skills/unit-tests/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A well-structured, actionable reference for running VS Code unit tests with executable examples for every shell option and a clear preferred/fallback decision tree. The main gaps are a conceptual-only runTests example and the absence of an explicit validation/feedback loop for the noted stale-output pitfall.

Suggestions

Replace the runTests 'Example (conceptual)' with a concrete, copy-pasteable tool invocation matching the shell examples.

Add an explicit validation step for the stale-output pitfall (e.g., 'If tests fail unexpectedly, confirm the build watch task has compiled, then rerun').

Consider splitting the dense per-option reference into a separate reference file so SKILL.md stays a concise overview.

DimensionReasoningScore

Conciseness

The body is efficient and mostly lean, with short sections and targeted examples; a few descriptive sentences (e.g., 'Useful for running all tests under a feature area') could be trimmed but generally earn their place.

4 / 5

Actionability

The shell fallback provides fully executable, copy-paste-ready commands with examples for every option, but the runTests section gives only a conceptual example and no concrete tool invocation, leaving a minor gap.

4 / 5

Workflow Clarity

A clear preferred-then-fallback structure is present with a stated compilation precondition and scope boundary (integration tests excluded), though an explicit validation checkpoint for stale output is only implied rather than sequenced.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections covering each option, but the options reference is presented as a single inline block with no one-level-deep references to split out the denser material.

4 / 5

Total

16

/

20

Passed

Description

77%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 strong, trigger-led description that clearly scopes the skill to running unit tests in the VS Code repo and names the concrete tooling involved. It is specific and complete, with only minor gaps in synonym coverage and adjacent-skill differentiation.

DimensionReasoningScore

Specificity

Names concrete tools (runTests, scripts/test.sh, scripts/test.bat) and argument categories (filtering, globbing, debugging), but the actions are stated as abstract categories rather than fully concrete operations, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' (covers the runTests tool and platform scripts plus their supported arguments) and 'when' ('Use when running unit tests in the VS Code repo'), but the 'when' clause scopes only to the repo rather than naming the full set of natural triggers (filtering, globbing, debugging tests).

4 / 5

Trigger Term Quality

Includes natural phrases a user would say ('running unit tests', 'VS Code repo', 'filtering, globbing, and debugging tests') with good coverage, though synonyms like 'test runner' or 'Mocha' are absent.

4 / 5

Distinctiveness Conflict Risk

The niche (unit tests in the VS Code repo via specific tools) is clear and mostly distinct, with only minor overlap risk against the related integration-tests skill referenced in the body.

4 / 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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
posit-dev/positron
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.