CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/pytest-tests

Configures and runs pytest - the de facto Python test framework with fixture-based dependency injection (`@pytest.fixture` with scopes module/session/function), parametrize for table-driven tests (`@pytest.mark.parametrize`), markers (`@pytest.mark.skip` / `xfail` / `slow`), `conftest.py` for shared fixtures, plugin ecosystem (pytest-cov, pytest-asyncio, pytest-mock, pytest-xdist), `--lf`/`--ff` for fail-loop, coverage gating. Use when working with Python and needing the modern test framework.

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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

A lean, code-driven skill body that progresses through a clear install-to-coverage workflow with executable examples at every step and a well-signaled offload of deeper CI/coverage config to a real reference file. The only marginal area is the brief Overview that restates pytest basics Claude already knows.

DimensionReasoningScore

Conciseness

Each section is a code/command block with one or two tight supporting sentences; the Overview's four-line framing is the only mild concession to known concepts, and every other token (config, fixtures, markers, flags, anti-patterns, limitations) earns its place.

3 / 3

Actionability

All ten steps give executable, copy-paste-ready material — pip installs, a runnable test, a complete pyproject config, fixture/parametrize/marker/mocker/async examples, and concrete pytest flags — with no pseudocode placeholders.

3 / 3

Workflow Clarity

Ten steps are clearly sequenced from install through fast-feedback flags, and built-in checkpoints exist via --strict-markers (Step 3) and --cov-fail-under coverage gating (Step 9); the task is config/run rather than destructive batch work, so no validate-fix-retry loop is required.

3 / 3

Progressive Disclosure

The spine keeps only the minimal `pytest --cov ... --cov-fail-under=80` command and signals a single one-level-deep reference — "Full [tool.coverage.*] config, CI wiring, and parallel execution: references/coverage-and-ci.md" — which exists and holds the deeper material, matching the well-signaled one-level reference anchor.

3 / 3

Total

12

/

12

Passed

Description

85%

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 specific, third-person description that concretely enumerates pytest capabilities and includes an explicit Use-when trigger. Its main weakness is the trigger phrasing, which leans on technical jargon rather than natural user language.

Suggestions

Rewrite the 'Use when' clause with natural user phrasing, e.g. 'Use when the user asks to run, write, or debug Python tests, or mentions pytest, fixtures, parametrize, or test failures.'

Drop or condense the dense inline feature inventory (scopes, marker list, plugin names) in favor of a few high-signal keywords; the body already covers the details.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and mechanisms — "Configures and runs pytest", "fixture-based dependency injection", "parametrize for table-driven tests", "markers", "coverage gating" — matching the anchor for several specific concrete actions.

3 / 3

Completeness

Clearly answers both what (configures/runs pytest with the listed features) and when via the explicit "Use when working with Python and needing the modern test framework" clause, satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Includes relevant terms ("pytest", "Python test framework") but the only trigger phrasing is "Use when working with Python and needing the modern test framework", which lacks natural variations a user would actually say (e.g. "run my tests", "my tests are failing", "write a test"); the bulk is technical jargon.

2 / 3

Distinctiveness Conflict Risk

Names pytest explicitly as a distinct modern framework niche with its own trigger; unlikely to fire for the sister tools (unittest/doctest/nose2) it distinguishes itself from, matching the clear-niche anchor.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents