Python Release
Use this skill for Python release and packaging work.
Read references/release-workflow.md before changing Python release metadata or generated client pins.
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
Use this Skill: https://skilld.dev/gh/composiohq/composio/python-release Nothing lands on disk. Nothing to clean up.
Edit a local copy. It keeps the author and licence.
≈68 tokens for metadata: the name and description. ≈44 when used: this file. ≈538 more on demand in 1 file.
Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.
In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈272 characters, or 3.4%.
The 1% threshold is a size suggestion. Longer descriptions can still fit.
Your model, settings, and other Skills decide how much text your Agent can read.
The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.
Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.
Use this skill for Python release and packaging work.
Read references/release-workflow.md before changing Python release metadata or generated client pins.
Source: SKILL.md on GitHub
No rule matched.
skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.
skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.
The skill facilitates Python SDK release workflows, including building, dependency management, and import verification using standard tools like uv, make, and the GitHub CLI. It interacts with the vendor's own packages and official registries. Security findings are limited to the inherent risks of automated command execution based on documentation.
No alerts
Risk: LOW · No issues
Signed by skilld at 85dab73. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.
Last checked against GitHub yesterday.