python-release

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.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/python-release/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an appropriately lean pointer to a well-structured reference file, excelling at progressive disclosure. Its weakness is that no executable steps or sequenced workflow with validation appear in SKILL.md itself — all actionable detail is delegated to the reference.

Suggestions

Add a brief 3-4 step sequenced overview of the release workflow (build → bump pins → regenerate lockfile → verify) with the key validation command inline, so the body is actionable without opening the reference.

Remove or tighten 'Use this skill for Python release and packaging work.' since it duplicates the frontmatter description.

Include the one or two most critical executable commands (e.g. 'uv lock --upgrade-package composio-client' and the import verification) directly in the body as a quick-start, with the reference holding the rest.

Dimension	Reasoning	Score
Conciseness	The body is very lean at three lines and assumes Claude's competence, but 'Use this skill for Python release and packaging work' mildly restates the frontmatter description and could be trimmed.	4 / 5
Actionability	It gives one concrete directive ('Read references/release-workflow.md before changing Python release metadata or generated client pins'), but the executable commands live in the reference rather than the body, leaving key details out of SKILL.md itself.	3 / 5
Workflow Clarity	Only a single gating instruction is present with no sequenced multi-step release workflow or validation checkpoints in the body; since releases are batch operations, the missing validation caps this at 3.	3 / 5
Progressive Disclosure	The body is a clear overview that signals a single one-level-deep reference (references/release-workflow.md, which exists) with its trigger condition, making navigation easy and appropriately split.	5 / 5
	Total	15 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that is specific, well-triggered, and bounded by a clear negative use-case. Minor keyword synonym/extension gaps keep trigger term quality just below full marks.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	It explicitly answers both 'what' (handles release/build/bump/packaging/pin/lock/workflow/verification) and 'when' ('Use for Python release process work or dependency pin bumps'), plus a negative boundary.	5 / 5
Trigger Term Quality	Natural phrases like 'Python SDK release', 'dependency pin bumps', 'PyPI client pin', and 'uv.lock' are present, but it lacks file extensions (e.g. .toml) and common synonyms (e.g. 'version bump', 'publish').	4 / 5
Distinctiveness Conflict Risk	It carves a clear Python-release niche with distinct triggers and an explicit 'do not use for ordinary Python feature implementation' boundary, minimizing overlap with general Python skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ComposioHQ/composio
Path: .agents/skills/python-release/SKILL.md
Commit: b0cf0f9

Reviewed: about 7 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.