How do I install the Publish Python skill?

Run npx skillmds@latest add open-agent-tools/publish-python in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Publish Python safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Publish Python?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Publish Python free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Publish Python?

Open-Agent-Tools (@open-agent-tools) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Publish Python by open-agent-tools — Agent Skill

Name: Publish Python
Author: Open-Agent-Tools

Publish Python

Prepares and triggers a new Python package release: runs cleanup, validates semantic versioning, updates pyproject.toml and docs, builds with uv, creates a GitHub release, and monitors the publishing workflow. Supports patch/minor/major auto-increment. Use when the user wants to cut a release, bump the version, or publish a new Python package version.

File contents

Prepare and trigger a new release for version: $ARGUMENTS

Follow these steps:

Output Format: Use clear section headers, timestamps for each step, and progress indicators for release operations.

Tool Validation: First verify that required tools are installed (uv, gh, git) and the project has proper release configuration.

Version Validation: Validate that the provided version follows semantic versioning format (e.g., 1.2.3, 1.0.0-alpha.1).

Run cleanup first: Execute all cleanup steps (linting, formatting, type checking)
Version increment options: Support auto-increment with 'patch', 'minor', or 'major' keywords instead of explicit version numbers
Update pyproject.toml: Update the version field in pyproject.toml with the new version number
Update version in docs: Update all references to the next version based on the provided version number
Check version: Verify version in pyproject.toml and init.py match the target version and are greater than the current version
Build test: Run uv build to ensure the package builds correctly
Create release: Use gh release create with the appropriate version tag and release notes
Monitor: Track the publishing workflow with gh run list to ensure it completes successfully

Error Handling: If any step fails, attempt to fix the issue automatically. If unable to fix, report the specific error and suggested solutions before proceeding.

Frequently asked questions