How do I install the Modern Python skill?

Run npx skillmds@latest add tomevault-io/modern-python-4 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 Modern Python 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 Modern Python?

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 Modern Python free to use?

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

Who published Modern Python?

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

Modern Python by tomevault-io — Agent Skill

Name: Modern Python
Author: tomevault-io

Modern Python

Apply Trail of Bits “modern python” conventions (uv, ruff, ty, pytest, prek, pyproject.toml-first). Use when editing/adding Python code in this repo or when the user asks to modernize Python tooling. Avoid reformatting vendored Python under lib/** unless explicitly requested. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Modern Python (Trail of Bits style)

Based on the Trail of Bits modern-python plugin patterns (uv + ruff + ty + pytest + prek) described in their README: https://raw.githubusercontent.com/trailofbits/skills/main/plugins/modern-python/README.md.

Scope rules for this repo

Do apply to first-party Python files (project code, scripts, tooling).
Do NOT apply to vendored/third-party Python under lib/** (and other vendor dirs like node_modules/**) unless the user explicitly asks. If asked, keep changes minimal and avoid sweeping formatting.

Defaults (recommended)

Python: require 3.11+
Dependency management: uv (uv sync, uv add, uv run)
Lint/format: ruff (format + lint)
Type checking: ty (fast type checker) if acceptable; otherwise mypy/pyright only if user asks
Tests: pytest (+ coverage gate if project is test-heavy)
Hooks: prek (or pre-commit if already in use)
Config: prefer pyproject.toml as the single source of truth

Command translation (legacy → modern)

python … → uv run python … (or uv run … for scripts)
pip install X → uv add X (project dep) or uv run --with X … (one-off)
pip uninstall X → uv remove X
pip freeze → uv export

When creating or modernizing a Python package

Detect existing tooling: check for pyproject.toml, requirements*.txt, setup.cfg, tox.ini, .pre-commit-config.yaml and decide whether to migrate or keep compatible.
Add/standardize pyproject.toml:
- add tool configs for ruff (format + lint) and pytest
- keep settings minimal and consistent (no redundant formatters)
Use src/ layout for importable packages when appropriate.
Add CI hooks only when requested (don’t spam checks).

When reviewing Python changes

Prefer small diffs: functional changes separate from formatting/tooling changes.
If introducing new tools, ensure they’re runnable with simple commands (uv run …, uv sync).
Avoid pinning excessive versions unless the repo already pins; keep constraints compatible.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: modern-python-4description: Apply Trail of Bits “modern python” conventions (uv, ruff, ty, pytest, prek, pyproject.toml-first). Use when editing/adding Python code in this repo or when the user asks to modernize Python tooling. Avoid reformatting vendored Python under lib/** unless explicitly requested. Use when this capability is needed.---# Modern Python (Trail of Bits style)Based on the Trail of Bits `modern-python` plugin patterns (uv + ruff + ty + pytest + prek) described in their README: `https://raw.githubusercontent.com/trailofbits/skills/main/plugins/modern-python/README.md`.## Scope rules for this repo- **Do apply** to first-party Python files (project code, scripts, tooling).- **Do NOT apply** to vendored/third-party Python under `lib/**` (and other vendor dirs like `node_modules/**`) unless the user explicitly asks. If asked, keep changes minimal and avoid sweeping formatting.## Defaults (recommended)- **Python**: require **3.11+**- **Dependency management**: `uv` (`uv sync`, `uv add`, `uv run`)- **Lint/format**: `ruff` (format + lint)- **Type checking**: `ty` (fast type checker) if acceptable; otherwise `mypy`/`pyright` only if user asks- **Tests**: `pytest` (+ coverage gate if project is test-heavy)- **Hooks**: `prek` (or `pre-commit` if already in use)- **Config**: prefer `pyproject.toml` as the single source of truth## Command translation (legacy → modern)- `python …` → `uv run python …` (or `uv run …` for scripts)- `pip install X` → `uv add X` (project dep) or `uv run --with X …` (one-off)- `pip uninstall X` → `uv remove X`- `pip freeze` → `uv export`## When creating or modernizing a Python package1. **Detect existing tooling**: check for `pyproject.toml`, `requirements*.txt`, `setup.cfg`, `tox.ini`, `.pre-commit-config.yaml` and decide whether to migrate or keep compatible.2. **Add/standardize `pyproject.toml`**: - add tool configs for ruff (format + lint) and pytest - keep settings minimal and consistent (no redundant formatters)3. **Use `src/` layout** for importable packages when appropriate.4. **Add CI hooks only when requested** (don’t spam checks).## When reviewing Python changes- Prefer **small diffs**: functional changes separate from formatting/tooling changes.- If introducing new tools, ensure they’re runnable with simple commands (`uv run …`, `uv sync`).- Avoid pinning excessive versions unless the repo already pins; keep constraints compatible.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/wenakita) — claim your Tome and manage your conversions.

Frequently asked questions