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

86%

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

Quality

Content

72%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.

An exemplary progressive-disclosure skeleton — minimal, lean, and correctly routing to a real, one-level-deep reference — but the body itself carries almost no operational substance. Workflow sequencing and executable detail exist only in the reference file, leaving body-level actionability and workflow clarity merely adequate.

Suggestions

Add a 3-5 line overview of the release workflow phases (build → pin bump → verification) so the body conveys the process shape without duplicating the reference's commands.

Inline the one or two most critical commands (e.g. `uv lock --upgrade-package <pkg>` and the import verification check) directly in the body so the highest-risk steps are visible before opening the reference.

State the validation gate explicitly in the body (e.g. "do not proceed to publish until the import and nox checks pass") to surface the checkpoint that is currently only implicit.

Dimension	Reasoning	Score
Conciseness	The body is two lean sentences with zero padding and no explanation of concepts Claude already knows ("Use this skill for Python release and packaging work." / "Read `references/release-workflow.md` before changing..."). Every token earns its place, matching the 5 anchor.	5 / 5
Actionability	"Read `references/release-workflow.md` before changing Python release metadata or generated client pins" is a concrete directive, but the body itself contains no commands, code, or steps — all executable content is delegated to the reference. This fits the 3 anchor (some concrete guidance but incomplete) rather than 4, which expects concrete code or commands in the content itself.	3 / 5
Workflow Clarity	The body offers only a single gating instruction; the release workflow's sequence and its validation checkpoints (import check, nox run) live entirely in the referenced file and are implicit from the body alone. Not 4 because the body presents no sequenced steps or checkpoints of its own; not 2 because the one instruction it does give is unambiguous and correctly conditioned.	3 / 5
Progressive Disclosure	Scored against the actual bundle: the body routes cleanly to `references/release-workflow.md`, which exists, is exactly one level deep, and is well-signaled with an explicit precondition ("before changing Python release metadata or generated client pins"). No content is inlined that belongs in the reference, matching the 5 anchor's clear overview with well-signaled one-level-deep references.	5 / 5
	Total	16 / 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 description: dense with concrete domain-specific triggers, an explicit use-when clause, and an explicit non-use boundary that sharply reduces conflict risk. The only weakness is modest synonym coverage for how users phrase release requests.

Suggestions

Add one or two common synonyms for trigger phrases, e.g. "version bump" or "publish to PyPI", to widen the natural-language trigger surface.

Dimension	Reasoning	Score
Specificity	The description enumerates concrete, specific operations across the release domain: "release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes". Coverage within its niche is comprehensive, matching the 5 anchor rather than 4, where only minor gaps would be expected.	5 / 5
Completeness	It explicitly answers "what" ("Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes") and "when" with concrete triggers ("Use for Python release process work or dependency pin bumps"), plus an explicit exclusion ("do not use for ordinary Python feature implementation"). This matches the 5 anchor; score 4 would require a weaker or less explicit 'when' clause, which is not the case.	5 / 5
Trigger Term Quality	Strong natural terms users would say: "Python release", "bump", "dependency pin bumps", "PyPI", "uv.lock", "publish". A few natural synonyms are missing (e.g. "version bump", "cut a release"), so it fits the 4 anchor (good coverage, a few terms missing) rather than the 5 anchor's comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	"do not use for ordinary Python feature implementation" explicitly fences the skill off from general Python work, and the trigger terms (PyPI pin, uv.lock, nox/build) form a clear release niche. Minimal conflict risk, matching the 5 anchor.	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: 98b10d7

Reviewed: 4 days 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.