CtrlK
BlogDocsLog inGet started
Tessl Logo

test-python

Run Python CLI tests. Use after making changes to cli/ code.

65

Quality

78%

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 ./.claude/skills/test-python/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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 an exemplary lean, executable two-step workflow for a simple skill: exact commands, numbered sequence, and a failure-handling note. The only minor gap is the implicit error-recovery loop, which could state that tests should be re-run until they pass.

DimensionReasoningScore

Conciseness

The body is two exact commands with terse annotations and a single recovery line — no padding and no concepts Claude already knows, matching the lean/efficient anchor.

5 / 5

Actionability

"cd cli && uv sync" and "cd cli && uv run pytest -v" are fully executable, copy-paste-ready commands covering the common case, matching the anchor-5 example.

5 / 5

Workflow Clarity

A clear numbered sequence with exact commands plus a failure branch ("If tests fail, diagnose and fix the issues"), but the recovery loop is implicit — no explicit re-run-until-green checkpoint — matching anchor 4 rather than 5.

4 / 5

Progressive Disclosure

A simple single-purpose skill under 50 lines with no need for external references; the content is well-organized, and no bundle files exist to reference, so the simple-skill exception applies.

5 / 5

Total

19

/

20

Passed

Description

62%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 concise, uses third person, and answers both what and when with an explicit trigger clause. Its main weakness is thin capability and keyword coverage — one action, one trigger phrase, no synonyms or tooling terms.

Suggestions

List the concrete actions performed, e.g. "Install dependencies with uv, run the CLI test suite with pytest" so specificity reaches several concrete actions.

Add natural trigger variations users would actually say, such as "Use when the user asks to run tests, check the CLI test suite, or after editing Python code under cli/".

Consider naming the tooling (pytest, uv) so the description is distinguishable from generic Python test-running skills.

DimensionReasoningScore

Specificity

"Run Python CLI tests" names the domain with one concrete action but is not comprehensive — it does not list several specific capabilities like the anchor-4 example expects.

3 / 5

Completeness

It has a clear what ("Run Python CLI tests") and an explicit when ("Use after making changes to cli/ code"), matching anchor 4; the single trigger condition keeps it below anchor 5's multiple concrete trigger phrases.

4 / 5

Trigger Term Quality

"Python CLI tests" and "changes to cli/ code" are relevant, domain-specific keywords, but common variations and synonyms (pytest, "run the tests", unit tests) are missing.

3 / 5

Distinctiveness Conflict Risk

Scoping to the repo's cli/ directory makes it mostly distinct with only minor overlap risk against generic Python-testing skills, matching anchor 4.

4 / 5

Total

14

/

20

Passed

Validation

100%

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
katanemo/plano
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.