Automated summary
This skill guides creating, structuring, and publishing modern Python packages with pyproject.toml, including distribution to PyPI or a private repository.
Strengths
- Covers the full lifecycle: project layout, metadata, dependencies, wheels/sdist, versioning, and release
- Explicitly targets modern tooling (pyproject.toml) instead of legacy setup.py setups
- Addresses CLI entry points, namespace packages, and publishing to private repositories
- Points to a detailed implementation playbook under resources/ for concrete patterns
Limitations
- The visible content stays generic: concrete instructions live in resources/implementation-playbook.md, which is not included here
- No automated validation of builds or uploads, so real-environment verification is left to the user
- Does not cover alternative build backends or complex monorepo scenarios beyond the listed scope
Use it whenever you need to turn Python code into an installable package, configure a pyproject.toml, or ship a release to PyPI or a private index.
Avoid it for work outside Python packaging, such as application refactoring, infrastructure deployment, or day-to-day virtualenv management.
Security analysis
SafeThe skill is a documentation/guide about Python packaging with no declared tools, no destructive commands, no network exfiltration, and no obfuscated or unsafe instructions. It does not execute anything itself.
No concerns found
How this analysis is madeExamples
I wrote a small utility library and want to publish it to PyPI. Help me write the pyproject.toml, set up the src layout, build the wheel and sdist, and walk me through the upload steps.Turn my existing Python module into an installable package that exposes a `mytool` command via an entry point, and show me how to test it after a local pip install.Set up my Python package for distribution to a private package index instead of PyPI, including versioning and metadata classifiers.name: python-packaging description: "Comprehensive guide to creating, structuring, and distributing Python packages using modern packaging tools, pyproject.toml, and publishing to PyPI." risk: safe source: community date_added: "2026-02-27"
Python Packaging
Comprehensive guide to creating, structuring, and distributing Python packages using modern packaging tools, pyproject.toml, and publishing to PyPI.
Use this skill when
- Creating Python libraries for distribution
- Building command-line tools with entry points
- Publishing packages to PyPI or private repositories
- Setting up Python project structure
- Creating installable packages with dependencies
- Building wheels and source distributions
- Versioning and releasing Python packages
- Creating namespace packages
- Implementing package metadata and classifiers
Do not use this skill when
- The task is unrelated to python packaging
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
Resources
resources/implementation-playbook.mdfor detailed patterns and examples.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/python-packaging-ms47vpvo/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/python-packaging-ms47vpvo' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/python-packaging-ms47vpvo/download' --output '.skill-downloads/python-packaging-ms47vpvo/SKILL.md.part' && mv '.skill-downloads/python-packaging-ms47vpvo/SKILL.md.part' '.skill-downloads/python-packaging-ms47vpvo/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/python-packaging-ms47vpvo/SKILL.md' && test -s '.skill-downloads/python-packaging-ms47vpvo/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/python-packaging' && cp -R '.skill-downloads/python-packaging-ms47vpvo' '.claude/skills/python-packaging'Cursor
test -f '.skill-downloads/python-packaging-ms47vpvo/SKILL.md' && test -s '.skill-downloads/python-packaging-ms47vpvo/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/python-packaging' && cp -R '.skill-downloads/python-packaging-ms47vpvo' '.cursor/skills/python-packaging'Codex
test -f '.skill-downloads/python-packaging-ms47vpvo/SKILL.md' && test -s '.skill-downloads/python-packaging-ms47vpvo/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/python-packaging' && cp -R '.skill-downloads/python-packaging-ms47vpvo' '.agents/skills/python-packaging'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/python-packaging-ms47vpvo'openskills read 'python-packaging-ms47vpvo'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/python-packaging-ms47vpvo/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.