CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fastmcp-python-tests

Write and evaluate effective Python tests using pytest. Use when writing tests, reviewing test code, debugging test failures, or improving test coverage. Covers test design, fixtures, parameterization, mocking, and async testing.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 delivers excellent, actionable project-specific constraints (async auto mode, module-level imports, in-memory transport, result.data accessor, inline-snapshot workflow) but dilutes them with substantial generic pytest guidance Claude already knows. Structure and actionability are solid; the main improvement is cutting or relocating the generic content.

Suggestions

Cut or move generic pytest sections (Test Naming, Error Testing, tmp_path, basic mocking, function-scoped fixtures) to a references file, keeping SKILL.md focused on the project-specific rules Claude cannot infer.

Replace placeholder-dependent snippets (User, calculate, my_function, MyModel) with runnable examples using real project imports like the FastMCP in-memory transport example.

Add a short explicit workflow (write test -> uv run pytest -n 2 -x -> fix or --inline-snapshot=fix -> re-run) to turn the implied feedback loop into a checkpointed sequence.

DimensionReasoningScore

Conciseness

The project-specific rules (asyncio_mode auto, module-level imports, in-memory transport, result.data vs result[0].text, inline-snapshot) are high-value, but roughly half the body restates generic pytest knowledge Claude already has (descriptive test names, pytest.raises with match, tmp_path, mock-at-the-boundary, function-scoped fixtures, basic parameterization). It fits 'mostly efficient but includes some unnecessary explanation' better than the padded anchor at 2, since the writing itself is terse.

3 / 5

Actionability

Good/bad code pairs, copy-paste run commands ("uv run pytest -n 2 --inline-snapshot=create"), and a complete in-memory transport example make the guidance mostly executable. It falls short of 5 because several snippets use undefined placeholders (User, calculate, my_function, MyModel), making them illustrative patterns rather than fully executable code.

4 / 5

Workflow Clarity

Sections are clearly organized with a pre-submit checklist and a snapshot create-then-fix command flow, providing most checkpoints; no destructive or batch operations apply, so no cap is triggered. It is not 5 because the write-test -> run -> fix feedback loop is implied by the run commands but never laid out as a sequence.

4 / 5

Progressive Disclosure

No bundle files exist, and the single ~230-line file is well-sectioned with one clearly signaled external reference. The generic pytest sections (Test Naming, Error Testing, Fixtures, Mocking) could be split into a reference file to keep SKILL.md focused on project constraints, matching the minor-organization-gaps anchor at 4 rather than the ideal split at 5.

4 / 5

Total

15

/

20

Passed

Description

88%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 description: it states concrete capabilities with an explicit 'Use when' clause covering natural trigger phrases. Its only weaknesses are slightly incomplete keyword synonyms (no 'unit tests' or file-pattern triggers) and mild overlap risk with generic testing requests.

Suggestions

Add natural synonyms and file patterns to the trigger clause, e.g. 'Use when writing or reviewing unit tests, test suites, or test_*.py / conftest.py files, or when pytest fails or coverage is low'.

Consider narrowing distinctiveness by mentioning the project context (e.g. FastMCP/pytest-based projects) so it does not trigger for testing tasks in unrelated stacks.

DimensionReasoningScore

Specificity

"Write and evaluate effective Python tests using pytest" names multiple concrete actions (write, review, debug, improve coverage) and enumerates topic coverage ("fixtures, parameterization, mocking, and async testing"), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

It explicitly answers what ("Write and evaluate effective Python tests using pytest. Covers test design, fixtures, parameterization, mocking, and async testing") and when ("Use when writing tests, reviewing test code, debugging test failures, or improving test coverage") with concrete trigger phrases, matching the top anchor; the 4 anchor applies only when the 'when' clause is less explicit.

5 / 5

Trigger Term Quality

Natural phrases like "writing tests, reviewing test code, debugging test failures" are present, but common synonyms such as "unit tests" or "test suite" and file patterns like test_*.py are missing, fitting the good-coverage-with-a-few-gaps anchor rather than comprehensive coverage at 5.

4 / 5

Distinctiveness Conflict Risk

Anchoring to Python and pytest makes it mostly distinct from unrelated skills, but generic triggers like "debugging test failures" or "writing tests" could fire for other languages' testing skills, giving minor overlap risk consistent with anchor 4 rather than minimal conflict risk at 5.

4 / 5

Total

18

/

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

Jamie-BitFlight/claude_skills

Path

plugins/fastmcp-creator/skills/fastmcp-python-tests/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.