run-unit-tests

Use when asked to run unit tests.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/run-unit-tests/SKILL.md

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a tight, fully executable single-purpose skill: it gives the exact command and the path context needed to run it, with no unnecessary explanation. A minor typo ("commend" for "command") does not materially reduce any dimension.

Dimension	Reasoning	Score
Conciseness	The body is lean — one orienting sentence plus a single executable command with a path clarification — with no padding of concepts Claude already knows, matching the lean anchor 3.	3 / 3
Actionability	It provides a concrete, copy-paste-ready command (`uv run --group test pytest packages/flet/tests`) with the relative-path context needed to run it, matching anchor 3.	3 / 3
Workflow Clarity	This is a simple single-command, non-destructive skill where the single action is unambiguous; the simple-skills note allows a 3 without explicit multi-step validation.	3 / 3
Progressive Disclosure	The skill is under 50 lines with no need for external references and is organized into a clear Instructions section, satisfying the simple-skill exception for a score of 3.	3 / 3
	Total	12 / 12 Passed

Description

50%

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 provides an explicit trigger but is extremely terse, omitting a clear statement of what the skill does beyond the trigger itself. It is barely adequate rather than vague, with limited trigger coverage and notable overlap risk.

Suggestions

Add a concrete capability clause, e.g. "Runs the flet Python package unit tests via uv/pytest." to explicitly answer the 'what'.

Broaden trigger terms to natural variations users say, such as "pytest", "test suite", or "flet tests".

Add a domain qualifier (Flet/Python) to the description so it is distinguishable from generic test-running skills.

Dimension	Reasoning	Score
Specificity	The phrase "run unit tests" names a domain and a single action, but it lists no concrete, comprehensive capabilities — closer to anchor 2 than the vague anchor 1, yet not the multi-action anchor 3.	2 / 3
Completeness	It has an explicit "Use when" trigger (the when), but the "what" is only implied by the trigger itself and never stated as a capability, so it does not reach the explicit what+when of anchor 3.	2 / 3
Trigger Term Quality	"asked to run unit tests" is a natural phrase a user might say, but coverage is thin with no common variations (e.g., pytest, test suite, tests failing), matching anchor 2.	2 / 3
Distinctiveness Conflict Risk	"run unit tests" is generic and would overlap with many test-running skills, but it is bounded enough to avoid the fully-generic anchor 1.	2 / 3
	Total	8 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: flet-dev/flet
Path: .agents/skills/run-unit-tests/SKILL.md
Commit: db0df8e

Reviewed: 4 days 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.