python-packaging

Comprehensive guide to creating, structuring, and distributing Python packages using modern packaging tools, pyproject.toml, and publishing to PyPI.

Quality

51%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/python-packaging/SKILL.md

The canonical home for this skill is python-packaging in rmyndharis/antigravity-skills

Quality

Content

36%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 brief and well-sectioned but almost entirely abstract, with no executable packaging guidance and a broken reference to a missing playbook file. It needs concrete examples and a working, one-level-deep reference to be genuinely useful.

Suggestions

Add concrete, copy-paste-ready packaging guidance: a minimal pyproject.toml example and the build/publish commands (e.g. `python -m build`, `twine upload dist/*`).

Provide a real sequenced workflow with validation checkpoints, including a verify-before-publish step given PyPI publishing is effectively irreversible.

Create the referenced resources/implementation-playbook.md (or correct the path) so the progressive-disclosure reference resolves to an actual file.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept over-explanation, but the generic instruction bullets ("Apply relevant best practices and validate outcomes") are mild filler rather than Python-packaging-specific value.	4 / 5
Actionability	No concrete code, commands, or executable guidance appear; the body only offers abstract directives and defers all detail to a referenced file that does not exist.	1 / 5
Workflow Clarity	A rough generic sequence is present (clarify goals, apply best practices, verify) but it is not a real packaging workflow and lacks any validation checkpoints for the publishing/batch operations.	2 / 5
Progressive Disclosure	A one-level reference to resources/implementation-playbook.md is signaled in a Resources section, but the referenced file does not exist and no bundle directory is present, leaving navigation broken.	3 / 5
	Total	10 / 20 Passed

Description

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

The description is specific and well-targeted to a clear niche, naming concrete actions and tools. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps its completeness.

Suggestions

Add an explicit "Use when..." clause listing concrete triggers, e.g. "Use when creating Python libraries, building wheels/sdists, configuring pyproject.toml, or publishing to PyPI."

Include more natural synonyms and file extensions users say (wheels, sdist, build, twine, .whl, .tar.gz) to broaden trigger coverage.

Consider naming a couple more concrete actions (e.g. dependency management, classifiers, entry points) to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete actions ("creating, structuring, and distributing Python packages") and specific tools ("pyproject.toml", "PyPI"), with only minor coverage gaps.	4 / 5
Completeness	Clearly states what the skill does but lacks any "Use when..." trigger clause; per the rubric, a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms users would say ("Python packages", "pyproject.toml", "PyPI", "packaging"), but misses common synonyms like wheels, sdist, build, or twine.	4 / 5
Distinctiveness Conflict Risk	The pyproject.toml / PyPI / Python-packages niche is mostly distinct with only minor overlap risk against a generic Python skill.	4 / 5
	Total	15 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/python-packaging/SKILL.md
Commit: 57c135b

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