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

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is actionable with strong executable examples, but it is somewhat verbose for what Claude already knows and lacks an explicit build-to-publish workflow with validation. A broken bundle reference path ('details.md' vs the real 'advanced-patterns.md') weakens progressive disclosure.

Suggestions

Add an explicit end-to-end workflow with sequenced commands (e.g., `python -m build`, `twine check`, `twine upload`) and a validation checkpoint before publishing.

Fix the broken reference path: the body cites 'references/details.md' but the actual bundle file is 'references/advanced-patterns.md' — align the citation with the real filename.

Trim redundant concept restatements (PEP blurbs, 'When to Use' list, build-backend one-liners) that restate what Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete config examples, but it restates concepts Claude already knows (PEP one-liners, build-backend blurbs like 'setuptools: Traditional, widely used') and a 9-item 'When to Use' list that could be trimmed — matching the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	Provides executable, copy-paste-ready material — a complete minimal pyproject.toml, package tree layouts, and concrete setuptools config snippets — matching the 'fully executable code; specific examples' anchor.	3 / 3
Workflow Clarity	The packaging lifecycle (structure → configure → build → publish) is never given as an explicit sequenced workflow, and build/publish commands and validation steps are absent; per the guideline, a risky/batch operation like publishing with no validation checkpoints caps this at 2.	2 / 3
Progressive Disclosure	The body signals a one-level-deep reference, but it points to 'references/details.md' while the only bundle file present is 'references/advanced-patterns.md' — the reference path is wrong, so navigation is present but broken and not correctly signaled.	2 / 3
	Total	9 / 12 Passed

Description

100%

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: it names specific concrete actions, uses natural trigger terms a user would say, and pairs a clear capability statement with an explicit 'Use when' clause. It is concise without padding and occupies a distinct niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Create distributable Python packages', 'proper project structure, setup.py/pyproject.toml', and 'publishing to PyPI' — matching the anchor for naming several specific actions.	3 / 3
Completeness	Explicitly states what the skill does and includes an explicit 'Use when...' clause with concrete triggers, satisfying both the what and the when.	3 / 3
Trigger Term Quality	Covers natural phrasings a user would say — 'packaging Python libraries', 'creating CLI tools', 'distributing Python code' — giving good coverage of common variations rather than only jargon.	3 / 3
Distinctiveness Conflict Risk	The Python-packaging niche is clear and the triggers (packaging libraries, CLI tools, distributing Python code) are distinct enough to be unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: wshobson/agents
Path: plugins/python-development/skills/python-packaging/SKILL.md
Commit: c4b82b0

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