CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 thin-router skill body: minimal token footprint, one unambiguous conditioned pointer to a single real reference file that carries the executable workflow with verification steps. The gaps are minor — a redundant purpose sentence duplicating the description, and no inline signpost of what the reference covers.

Suggestions

Drop or repurpose "Use this skill for Python release and packaging work." — it duplicates the frontmatter description and earns no new information.

Add a one-line signpost of what the reference covers (e.g., build, dependency bounds, client pin bumps, verification) so the body navigates rather than only points.

Inline the single most common command (e.g., `make build`) so the frequent case is actionable without opening the reference file.

DimensionReasoningScore

Conciseness

The body is three lean lines with no concept explanations Claude already knows, but "Use this skill for Python release and packaging work" duplicates the frontmatter description and could be trimmed. Anchor 4 (efficient, minor instances that could be trimmed) fits better than anchor 5, which requires every token to earn its place.

4 / 5

Actionability

"Read `references/release-workflow.md` before changing Python release metadata or generated client pins" is a concrete, unambiguous, executable directive with a real file path (verified to exist in the bundle). Per the scoring note, absence of code in an instruction-only skill is not penalized since the guidance is actionable, but the body itself contains no commands or examples — the executable content (make build, uv lock, pip index versions) lives one level deep — so anchor 4 fits better than the copy-paste-ready coverage of anchor 5.

4 / 5

Workflow Clarity

The body's single routing action is clear and conditioned, and the referenced workflow file supplies the actual sequence with validation checkpoints (verify version with "pip index versions composio-client", regenerate lockfile with "uv lock --upgrade-package composio-client", and a Verification section with import checks). This is not a single-task skill, so the simple-skill 5 exception does not apply; the body itself gives no inline sequence overview, matching anchor 4 (clear sequence with checkpoints, minor gaps) rather than 5.

4 / 5

Progressive Disclosure

The bundle is exactly one reference file (references/release-workflow.md) matching the path cited in the body, clearly signaled with a condition for when to read it — a clean one-level-deep split where the body is the overview and all detail lives in the reference. This matches anchor 5 (clear overview, well-signaled one-level-deep references, appropriate split); the reference's pointer to repo-internal docs (`ts/docs/internal/release.md`) is an external doc citation, not nested bundle content.

5 / 5

Total

17

/

20

Passed

Description

87%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: concrete domain objects, an explicit "Use for" trigger clause, and an effective negative boundary. The only weaknesses are the single generic verb "Handle" wrapping a noun list and a few missing natural trigger phrasings like "version bump".

DimensionReasoningScore

Specificity

"Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes" enumerates many concrete objects (PyPI client pin, uv.lock, nox/build workflow), but the action verbs are compressed into a single generic "Handle...changes" rather than distinct concrete actions. This matches anchor 4 (several specific items, minor gaps) better than anchor 5, which requires multiple distinct concrete actions like "extract, fill, merge, convert".

4 / 5

Completeness

The "what" is explicit ("Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes") and the "when" is explicit with concrete trigger phrases ("Use for Python release process work or dependency pin bumps") plus a negative boundary. This clearly matches anchor 5: both what and when answered explicitly with concrete triggers.

5 / 5

Trigger Term Quality

Natural trigger terms are present: "Python SDK release", "build", "bump", "PyPI client pin", "uv.lock", "dependency pin bumps", "publish verification". Coverage is good but a few natural phrasings users would say are missing (e.g., "version bump", "cut a release", "publish to PyPI" as a phrase), fitting anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct (SDK release/packaging toolchain with repo-specific artifacts like uv.lock, nox, PyPI client pin) and the exclusion clause "do not use for ordinary Python feature implementation" sharply separates it from generic Python skills. Clear niche with distinct triggers and minimal conflict risk — anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.