modern-python-toolchain

Modern Python project setup with uv, ruff, and pyright. Use when initializing a new Python project, configuring the Python environment, setting up linting/formatting, or when a project needs uv (the fast Python package manager). Trigger on: 'set up Python', 'new Python project', 'configure uv', 'install uv', 'ruff', 'pyright', 'Python linting', 'Python formatting', or when a task requires Python and no pyproject.toml exists yet.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/opencode/src/skill/builtin/.bundle/modern-python-toolchain/SKILL.md

Quality

Content

60%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.

A practical, mostly actionable guide with strong command coverage and clean sectioning. Its main weaknesses are mild over-explanation of tool capabilities Claude already knows, embedded version numbers that will date, and absence of explicit validation checkpoints in the workflow.

Suggestions

Cut introductory tool summaries that restate what uv/ruff/pyright are ('It replaces pip, pip-tools, pipx, pyenv, virtualenv, poetry, etc.') to assume Claude's competence and save tokens.

Move the pinned uv build-backend version ('0.11.28') into a note or document how to discover the current bound rather than hard-coding a value that will drift.

Add an explicit verification step after batch operations (e.g., run 'uv sync' then verify the environment with 'uv run python -c "import sys; print(sys.executable)"') to introduce a validation checkpoint into the workflow.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with command tables and lean rules, but it over-explains concepts Claude already knows ('uv is an extremely fast Python package and project manager. It replaces pip, pip-tools...') and notes version numbers like '0.11.28' that risk staleness, keeping it below the efficient anchors.	3 / 5
Actionability	Provides copy-paste-ready commands and TOML snippets for installation, init, add/remove/sync, ruff config, pyright usage, and coding style, with only minor gaps (e.g., no example of the actual ruff format invocation beyond the workflow line).	4 / 5
Workflow Clarity	Sections are sequenced (install -> uv basics -> ruff -> pyright -> coding style) and the ruff post-edit workflow is clear, but there are no explicit validation/verification checkpoints for batch-style operations such as 'uv sync' or 'uv run ruff check --fix' across the tree.	3 / 5
Progressive Disclosure	Well-organized into clearly headed sections that act as a navigable overview, and external docs are linked one level deep (docs.astral.sh links); there are no bundle files to split content into, so structure is appropriate, with only minor gaps in cross-referencing between sections.	4 / 5
	Total	14 / 20 Passed

Description

81%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 names the tools, lists concrete actions, and supplies an explicit 'Use when' clause plus natural trigger phrases. It is mostly third-person, though the second-person phrasing ('when a task requires Python') introduces a minor specificity issue.

Suggestions

Reword second-person clauses ('when a task requires Python and no pyproject.toml exists yet') into third-person voice (e.g., 'Triggers when no pyproject.toml exists yet') to fully meet the third-person guideline.

Add pyright/type-checking trigger phrases (e.g., 'type checking', 'type checker') alongside the existing 'pyright' trigger for fuller keyword coverage.

Tighten the broad phrase 'configuring the Python environment' to a more distinctive trigger to further reduce overlap with generic Python setup skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions (initializing a project, configuring the environment, setting up linting/formatting, installing uv) tied to specific tools (uv, ruff, pyright), though coverage of pyright's role is thinner than uv/ruff.	4 / 5
Completeness	Explicitly states what the skill does ('Modern Python project setup with uv, ruff, and pyright') and provides an explicit 'Use when' clause plus a concrete 'Trigger on' list, satisfying both what and when.	5 / 5
Trigger Term Quality	Includes many natural trigger phrases ('set up Python', 'new Python project', 'configure uv', 'ruff', 'pyright', 'Python linting') users would actually say; only minor synonyms/extensions are missing to reach full coverage.	4 / 5
Distinctiveness Conflict Risk	The uv/ruff/pyright niche and the 'no pyproject.toml exists yet' trigger carve a clear niche with minimal conflict risk, though broad phrases like 'configure the Python environment' could lightly overlap with general Python skills.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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: XiaomiMiMo/MiMo-Code
Path: packages/opencode/src/skill/builtin/.bundle/modern-python-toolchain/SKILL.md
Commit: ec3f989

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.