Automates the building and publishing of the Weave Python SDK to PyPI.
Install
mkdir -p .claude/skills/publish-pypi && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5510" && unzip -o skill.zip -d .claude/skills/publish-pypi && rm skill.zipInstalls to .claude/skills/publish-pypi
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Build and publish the Weave Python SDK to PyPI. Use when releasing a new version.Key capabilities
- →Build Python packages for PyPI
- →Perform dry-run verification
- →Publish to Test PyPI
- →Publish to production PyPI
How it works
The skill executes a Python script to build and upload the package, supporting both production and test environments via environment variables or configuration files.
Inputs & outputs
When to use publish-pypi
- →Publish a new package version
- →Verify package builds
- →Deploy to Test PyPI
About this skill
Publish to PyPI
This replicates the GitHub Actions publish-pypi-release workflow.
Arguments
$ARGUMENTScan betestto publish to Test PyPI, or empty for production PyPI
Instructions
First, run a dry-run to build and verify the package:
uv run ./scripts/publish_pypi_release.py --dry-run
If the user wants to publish to Test PyPI (or $ARGUMENTS contains "test"):
uv run ./scripts/publish_pypi_release.py --test
If the user wants to publish to production PyPI:
uv run ./scripts/publish_pypi_release.py
Authentication
Before publishing, ensure the user has set up authentication. Options:
TWINE_API_KEYenvironment variable (recommended for production)TWINE_TEST_API_KEYenvironment variable (for Test PyPI).pypircfile in home directory
If authentication fails, help the user set up their credentials.
After Publishing
Remind the user to verify the package:
- Test PyPI: https://test.pypi.org/project/weave/
- Production PyPI: https://pypi.org/project/weave/
When not to use it
- →When authentication credentials are not configured
- →When the package build fails dry-run verification
Prerequisites
Limitations
- →Requires pre-configured authentication
- →Depends on local script execution
How it compares
Unlike manual twine uploads, this skill provides a structured, automated workflow that includes dry-run verification and environment-specific authentication.
Compared to similar skills
publish-pypi side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| publish-pypi (this skill) | 1 | 6mo | Review | Intermediate |
| release-bump | 0 | 5mo | No flags | Intermediate |
| build-release | 0 | 1mo | Review | Intermediate |
| release | 0 | 5mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by wandb
View all by wandb →You might also like
release-bump
himatts
Prepare versioned release updates for Lime Pipeline. Use when user-visible behavior changes require bumping `bl_info["version"]`, updating `CHANGELOG.md`, and producing release-ready QA notes.
build-release
tsilva
Launch and monitor a SuperMarioBros-Nes-turbo PyPI release. Use when the user says /build-release, asks to cut a release, asks to tag/publish a version, asks whether a release made it to PyPI, or asks for macOS and Linux supermariobrosnes-turbo wheels.
release
DanTsai0903
Guide the release procedure for namingpaper - version bump, commit, GitHub release, and PyPI publish.
azure-functions
aj-geddes
Create serverless functions on Azure with triggers, bindings, authentication, and monitoring. Use for event-driven computing without managing infrastructure.
ml-pipeline-workflow
wshobson
Build end-to-end MLOps pipelines from data preparation through model training, validation, and production deployment. Use when creating ML pipelines, implementing MLOps practices, or automating model training and deployment workflows.
ollama-setup
jeremylongshore
Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.