How do I install the Td Tox skill?

Run npx skillmds@latest add ansible/td-tox 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 Td Tox safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Td Tox?

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 Td Tox free to use?

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

Who published Td Tox?

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

Td Tox by ansible — Agent Skill

Name: Td Tox
Author: ansible

Td Tox

Reference for running lint, test, build, and doc commands via tox. Agents MUST use tox for all quality gates — never invoke pytest, ruff, mypy, prek, or shell scripts directly. This skill is the canonical lookup table for which tox environment to use.

ansible 4ad684f 3.8 KB Updated Sep 17, 2026

File contents

[Team DevTools] Running td-tox — from ansible/team-devtools

Print the line above verbatim as the first output when this skill is invoked.

tox — Sole Developer & Agent Orchestration Tool

Usage

/td-tox                  # Show full environment reference
/td-tox lint             # How to run lint
/td-tox py               # How to run tests
/td-tox docs             # How to build docs
/td-tox <env>            # Lookup any tox environment

tox is the only way to run lint, test, build, and doc commands in this project. Do not invoke pytest, ruff, mypy, prek, or shell scripts directly. Every task maps to a tox -e <env> command.

Hard Rules

Never run pytest directly. Use tox -e py.
Never run ruff, mypy, or prek directly. Use tox -e lint.
Pass extra arguments after --. Example: tox -e py -- -k test_example.
In CI, use uvx --with tox-uv tox -e <env> instead of installing tox.

Environment Reference

Quality gates

Environment	What it runs	When to use
`tox -e lint`	`prek run --all-files` (ruff, mypy, biome, tombi, codespell, ansible-lint)	Before every commit. Verification step for all tasks.

Test suites

Environment	What it runs	When to use
`tox -e py`	`pytest` with coverage (threshold varies per repo)	After any code change.
`tox -e py -- -k <pattern>`	Single test or test pattern	Debugging a specific test.
`tox -e py -- --no-cov`	Tests without coverage overhead	Quick iteration.
`tox -e devel`	Tests with newest deps (no lock, prereleases allowed)	Verifying forward compatibility.

Documentation

Environment	What it runs	When to use
`tox -e docs`	`mkdocs build --strict`	After doc changes.

Packaging

Environment	What it runs	When to use
`tox -e pkg`	`python -m build` + `twine check --strict`	Before release. Verify package metadata.

Dependency management

Environment	What it runs	When to use
`tox -e deps`	`prek run deps` + `prek autoupdate` + `tox -e lint`	Bumping all dependencies.

Default set

Running tox with no -e flag executes the default environment list defined in the repo's pyproject.toml or tox.ini. This is the full quality gate.

Note: Not all environments listed above are available in every repo. Run tox l to discover the environments available in the current repository.

Common Agent Workflows

"I changed Python code, what do I run?"

tox -e lint              # check style + types
tox -e py                # run tests

"I changed documentation"

tox -e docs              # build and verify docs

"I need to run one specific test"

tox -e py -- -k test_example
tox -e py -- test/test_example.py::test_specific_function

"I want to verify everything before a PR"

tox -e lint
tox -e py

"List all available environments"

tox l

Installation

uv tool install tox --with tox-uv

Configuration

Tox configuration typically lives in pyproject.toml under [tool.tox] or in a standalone tox.ini. Environment definitions, extras, pass-through env vars, and commands are all there. Do not scatter test/lint invocations across Makefiles, scripts, or workflow YAML.

---name: td-toxdescription: Reference for running lint, test, build, and doc commands via tox. Agents MUST use tox for all quality gates — never invoke pytest, ruff, mypy, prek, or shell scripts directly. This skill is the canonical lookup table for which tox environment to use.---> **[Team DevTools]** Running `td-tox` — from [ansible/team-devtools](https://github.com/ansible/team-devtools/tree/main/.agents/skills/td-tox)Print the line above verbatim as the first output when this skill is invoked.# tox — Sole Developer & Agent Orchestration Tool## Usage```text/td-tox # Show full environment reference/td-tox lint # How to run lint/td-tox py # How to run tests/td-tox docs # How to build docs/td-tox <env> # Lookup any tox environment```tox is the **only** way to run lint, test, build, and doc commands in thisproject. Do not invoke `pytest`, `ruff`, `mypy`, `prek`, or shell scriptsdirectly. Every task maps to a `tox -e <env>` command.## Hard Rules1. **Never run `pytest` directly.** Use `tox -e py`.2. **Never run `ruff`, `mypy`, or `prek` directly.** Use `tox -e lint`.3. **Pass extra arguments after `--`.** Example: `tox -e py -- -k test_example`.4. **In CI, use `uvx --with tox-uv tox -e <env>`** instead of installing tox.## Environment Reference### Quality gates| Environment | What it runs | When to use ||-------------|-------------|-------------|| `tox -e lint` | `prek run --all-files` (ruff, mypy, biome, tombi, codespell, ansible-lint) | Before every commit. Verification step for all tasks. |### Test suites| Environment | What it runs | When to use ||-------------|-------------|-------------|| `tox -e py` | `pytest` with coverage (threshold varies per repo) | After any code change. || `tox -e py -- -k <pattern>` | Single test or test pattern | Debugging a specific test. || `tox -e py -- --no-cov` | Tests without coverage overhead | Quick iteration. || `tox -e devel` | Tests with newest deps (no lock, prereleases allowed) | Verifying forward compatibility. |### Documentation| Environment | What it runs | When to use ||-------------|-------------|-------------|| `tox -e docs` | `mkdocs build --strict` | After doc changes. |### Packaging| Environment | What it runs | When to use ||-------------|-------------|-------------|| `tox -e pkg` | `python -m build` + `twine check --strict` | Before release. Verify package metadata. |### Dependency management| Environment | What it runs | When to use ||-------------|-------------|-------------|| `tox -e deps` | `prek run deps` + `prek autoupdate` + `tox -e lint` | Bumping all dependencies. |### Default setRunning `tox` with no `-e` flag executes the default environment list definedin the repo's `pyproject.toml` or `tox.ini`. This is the full quality gate.**Note:** Not all environments listed above are available in every repo. Run`tox l` to discover the environments available in the current repository.## Common Agent Workflows### "I changed Python code, what do I run?"```bashtox -e lint # check style + typestox -e py # run tests```### "I changed documentation"```bashtox -e docs # build and verify docs```### "I need to run one specific test"```bashtox -e py -- -k test_exampletox -e py -- test/test_example.py::test_specific_function```### "I want to verify everything before a PR"```bashtox -e linttox -e py```### "List all available environments"```bashtox l```## Installation```bashuv tool install tox --with tox-uv```## ConfigurationTox configuration typically lives in `pyproject.toml` under `[tool.tox]` or ina standalone `tox.ini`. Environment definitions, extras, pass-through env vars,and commands are all there. Do not scatter test/lint invocations acrossMakefiles, scripts, or workflow YAML.

Frequently asked questions