How do I install the Testing Pytest skill?

Run npx skillmds@latest add tomevault-io/testing-pytest in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Testing Pytest safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Testing Pytest?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Testing Pytest free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Testing Pytest?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Testing Pytest by tomevault-io — Agent Skill

Name: Testing Pytest
Author: tomevault-io

Testing Pytest

Python pytest adapter for TDD workflows. Use this skill when users need pytest test design, red-green-refactor execution, fixture/parametrize strategy, or CI test quality improvements in Python projects. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Use when

Project uses Python + pytest.
User asks to write/refactor/debug tests with pytest.
User asks for TDD in Python.
User asks for fixture design, flaky test fixes, coverage, or performance checks in pytest.

Avoid when

Scope is not Python/pytest.
User asks for language-agnostic TDD only (use tdd-core first).

Relationship to tdd-core

Apply tdd-core as the base doctrine.
This skill adds pytest-specific execution patterns.

Pytest-specific workflow

Pick one behavior from the TDD plan.
RED: add one failing pytest test.
GREEN: minimal implementation to pass.
REFACTOR: clean code/fixtures while tests stay green.
Repeat in small vertical slices.

Pytest guardrails

Prefer public-interface tests over internals.
Use @pytest.mark.parametrize for behavior matrices.
Use Hypothesis for invariants/properties.
Keep fixtures explicit by scope; avoid hidden coupling in conftest.py.
Use boundary mocks only; avoid mocking your own domain modules.

See TDD_REFERENCE.md for commands and troubleshooting.

Output

Behavior coverage for this cycle
Test files/fixtures changed
Commands run + results
Remaining gaps/risks + next cycle

Source: pesap/agents — distributed by TomeVault.

Frequently asked questions