python-packaging

Automate Python packaging and publishing workflows for PyPI and TestPyPI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/LounisBou/claude-code --skill python-packaging-lounisbou
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python-packaging
Source: https://github.com/LounisBou/claude-code/tree/main/skills-available/python/python-packaging
Command: npx skills add https://github.com/LounisBou/claude-code --skill python-packaging-lounisbou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the packaging and publishing workflow for Python libraries, eliminating manual setup steps and reducing errors in metadata configuration.

Core Features & Use Cases

  • Packaging workflows: create pyproject.toml, setup.py, and wheel or source distributions for distribution
  • CLI tool scaffolding and entry points: build CLI tools and publish them to PyPI
  • Metadata management: ensure classifiers and project metadata are correctly defined for PyPI

Quick Start

Run the packaging workflow to generate a wheel and sdist from your project and publish to PyPI.

Frequently Asked Questions about python-packaging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I package a Python library for PyPI distribution?

Python packaging for PyPI involves configuring project metadata and build systems via pyproject.toml or setup.py, then generating source distributions and wheels. This workflow automates that metadata configuration to ensure compliance with modern packaging standards.

What's the best way to build a Python wheel from a pyproject.toml file?

Building a Python wheel from a pyproject.toml file requires specifying a build backend like setuptools, hatchling, poetry, or flit. This workflow configures the necessary build-backend specifications to automate wheel and sdist generation.

Does this packaging workflow support both setuptools and hatchling build backends?

Yes, this packaging workflow supports multiple build backends including setuptools, hatchling, poetry, and flit. It satisfies modern packaging standards across these tools for configuring pyproject.toml and generating distributions.

When do I need to use pyproject.toml instead of setup.py for Python packaging?

You need to use pyproject.toml instead of setup.py to satisfy modern Python packaging standards like PEP 517, 518, 621, and 660. This workflow specifies the correct packaging steps for both formats to ensure proper metadata configuration.

Can I publish a CLI tool to TestPyPI using this packaging workflow?

Yes, you can publish a CLI tool to TestPyPI using this packaging workflow. It scaffolds CLI tool entry points and specifies packaging steps for metadata management across both PyPI and TestPyPI use cases.