skills/python-packaging-uv/SKILL.md
Use when building or publishing Python packages with uv, including dist artifacts and pre-publish checks.
npx skillsauth add narumiruna/agent-skills python-packaging-uvInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use uv build and publish commands to produce wheels/sdists and ship to package indexes. Core principle: build from release-ready sources, verify artifacts, test installation, then publish.
| Task | Command |
| --- | --- |
| Build wheel+sdist | uv build |
| Build wheel only | uv build --wheel |
| Build for release (ignore local path overrides) | uv build --no-sources |
| Publish to PyPI | uv publish --token $PYPI_TOKEN |
| Publish to Test PyPI | uv publish --publish-url https://test.pypi.org/legacy/ --token $TEST_PYPI_TOKEN |
| Inspect wheel contents | unzip -l dist/<wheel>.whl |
| Test wheel install | uv run --with dist/<wheel>.whl python -c "import <module>" |
dist/ with uv build --no-sources.prek run -a
uv build --no-sources
unzip -l dist/my_package-1.0.0-py3-none-any.whl
uv run --with dist/my_package-1.0.0-py3-none-any.whl python -c "import my_package"
uv publish --publish-url https://test.pypi.org/legacy/ --token $TEST_PYPI_TOKEN
[tool.uv.sources] overrides are active.references/packaging.md - Build and publish detailsdevelopment
Score or compare one or more agent skills across trigger clarity, workflow actionability, safety boundaries, verification rigor, incremental knowledge value, and leanness. Use only when the user explicitly asks for ratings, numerical quality scores, rubric-based scorecards, or scored comparisons; use creating-agent-skills for unscored reviews or revisions.
development
Assess or improve an existing codebase's architecture when the user asks about module boundaries, coupling, scattered ownership, testability, change locality, deep modules, seams, or behavior-preserving structural refactoring. Use for cross-module design rather than ordinary diff review or a confirmed edge-case bug fix.
development
Perform read-only security audits, vulnerability assessments, or threat-focused reviews of diffs, pull requests, code paths, or explicitly scoped repositories when security is the primary objective or acceptance criterion. Use reviewing-code for ordinary review with baseline security coverage and hardening-code-paths for fixing confirmed findings.
development
Run iterative multi-reviewer panels over a code diff, verify their findings, apply explicitly authorized fixes, and re-review the updated change until it passes or reaches a stopping condition. Use when the user asks for a panel loop, multi-model code-review consensus, or a review-fix-re-review cycle.