Skill

python

Auto-activate for .py files, pyproject.toml, requirements.txt, setup.py, setup.cfg. Python project conventions and tooling: uv, ruff, mypy, typing, Cython, Mypyc. Use when: configuring Python packages, linting, type-checking, building extensions, or running scripts with uv. Produces Python project configurations with uv, ruff, mypy, and proper packaging. Not for Mojo (see mojo), Cython build details (see references), or web framework specifics (see litestar).

From flow

Install

Run in your terminal

npx claudepluginhub cofin/flow --plugin flow

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets

View in Repository

references/build.md

references/cython.md

references/mypyc.md

references/quality.md

references/uv.md

Skill Content

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

157.5k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

157.5k

agent-payment-x402

Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.

everything-claude-code

139.9k

Stats

Stars9

Forks4

Last CommitApr 4, 2026

Actions

View Source View Plugin View on GitHub View README

Python Skill

Overview

Expert knowledge for Python development in this workspace. This skill aggregates tooling, build systems, and quality standards.

Core Standards

As per workspace rules, the following are MANDATORY:

Tooling: uv is the required tool for Python package and environment management.
Execution: Always run python programs with the uv run prefix.
Installation: Use uv with pyproject.toml and install to a virtual environment.
Typing: Use >=3.10 types as per PEP 585 (e.g., dict, list instead of typing.Dict, typing.List).
Comments: Prefer docstrings and type annotations over inline comments. Use inline comments only when the logic is non-obvious and cannot be clarified through better naming or type hints.

References Index

For detailed guides on specific tools and sub-systems, refer to the following documents:

Package & Project Management

uv Guide
- Initializing projects, managing dependencies, workspaces, and tool execution (uvx).

Code Quality

Quality Standards
- Ruff, Mypy, and Pyright configurations.

Build Systems & compiled Extensions

Building & Packaging
- Standalone binaries, patching, and distributing.
Cython Extensions
- Compiling C extensions for performance.
Mypyc Extensions
- Mypyc-compatible classes and compilation workflows.

</workflow> <example>

Example: pyproject.toml Setup

[project]
name = "myapp"
version = "0.1.0"
requires-python = ">=3.12"
dependencies = ["litestar>=2.0", "sqlalchemy>=2.0"]

[tool.uv]
dev-dependencies = ["pytest>=8.0", "ruff>=0.8", "mypy>=1.13"]

[tool.ruff]
target-version = "py312"
line-length = 120

[tool.ruff.lint]
select = ["ALL"]
ignore = ["D", "ANN101"]

[tool.mypy]
strict = true
python_version = "3.12"

</example>

Official References

Shared Styleguide Baseline

Use shared styleguides for generic language/framework rules to reduce duplication in this skill.
General Principles
Python
Keep this skill focused on tool-specific workflows, edge cases, and integration details.