CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

python-packaging

Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, creating CLI tools, or distributing Python code.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/python-development/skills/python-packaging/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%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 a well-organized overview with executable pyproject.toml examples and a clearly signaled reference tier, but it restates packaging concepts Claude already knows and, despite covering an inherently sequential build-and-publish process, contains no ordered workflow with validation checkpoints in the top tier. One of the two bundle files is invisible from SKILL.md, reachable only via a second hop through details.md.

Suggestions

Add a numbered core workflow to the body — `pip install build twine`, `python -m build`, `twine check dist/*`, trial upload to TestPyPI, then `twine upload dist/*` — with explicit validation checkpoints, instead of deferring the entire publishing sequence to references/details.md.

Cut the 'Core Concepts' section (PEP summaries, build-backend comparison, PyPI vs TestPyPI) and the 'When to Use This Skill' bullet list that duplicates the frontmatter description; keep only skill-specific decisions such as the src-vs-flat layout recommendation.

Reference references/advanced-patterns.md directly from SKILL.md so both bundle files are discoverable one level deep, rather than linking it only from the end of references/details.md.

DimensionReasoningScore

Conciseness

The "Core Concepts" section restates knowledge Claude already has ("PEP 517/518: Build system requirements", the setuptools/hatchling/flit/poetry backend list, "PyPI: Python Package Index (public)"), and the 9-bullet "When to Use This Skill" duplicates the frontmatter description. Not anchor 2 because there is no padded prose and the Quick Start and pattern trees are tight and concrete; it sits above the midpoint as mostly-efficient with trimmable sections.

3 / 5

Actionability

Provides a copy-paste-ready minimal pyproject.toml, concrete directory trees, and the exact source-layout config (`[tool.setuptools.packages.find]` / `where = ["src"]`). Below anchor 5 because the body contains no build or publish commands at all — `python -m build`, `twine check`, and upload steps exist only in references/details.md.

4 / 5

Workflow Clarity

Packaging and publishing to PyPI is an inherently multi-step, outward-facing operation, yet the body presents no sequenced steps — only a pattern catalog with an implicit structure-then-configure order, and the validate-then-publish workflow (twine check, TestPyPI trial) is entirely deferred to the reference file. Anchor 3 does not fit because steps are not 'listed' in the body, and anchor 1 does not fit because the content is coherent and a rough sequence is recoverable from the Quick Start.

2 / 5

Progressive Disclosure

The pointer to `references/details.md` is clearly signaled ("Read that file when the navigation tier above is insufficient"), but the second bundle file, references/advanced-patterns.md, is never mentioned in SKILL.md and is reachable only through a link buried near the end of details.md — a two-level chain with one file undiscoverable from the top tier. Better organized than anchor 2 (the body is a genuine overview, not inlined reference material), but short of anchor 4's 'most content appropriately placed'.

3 / 5

Total

12

/

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 in third person that clearly states both capabilities and explicit 'Use when' triggers, with concrete named artifacts. Minor room to widen trigger coverage with publishing-related phrases users naturally say.

DimensionReasoningScore

Specificity

"Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI" names several concrete actions with specific artifacts (project structure, config files, PyPI publishing). It is below anchor 5 because coverage has gaps (building wheels, versioning, entry points are absent from the description), but well above anchor 3's 1-2 actions.

4 / 5

Completeness

Explicitly answers both questions: what ("Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI") and when ("Use when packaging Python libraries, creating CLI tools, or distributing Python code") with concrete trigger phrases — matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

"Use when packaging Python libraries, creating CLI tools, or distributing Python code" supplies natural phrases users would say. Not anchor 5 because common variations are missing — e.g. "publish to PyPI", "pip installable", "wheel", "setup.py" appear only in the what-clause or not at all as triggers.

4 / 5

Distinctiveness Conflict Risk

"Python packages", "pyproject.toml", "PyPI" carve out a clear niche with distinct triggers unlikely to fire for unrelated skills; only a trace of overlap with a hypothetical generic Python-development skill via "creating CLI tools", which keeps it at anchor 5 rather than suggesting anchor 4's "minor overlap risk".

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

wshobson/agents

Path

plugins/python-development/skills/python-packaging/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.