CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

python-project-structure

Python project organization, module architecture, and public API design. Use when setting up new projects, organizing modules, defining public interfaces with __all__, or planning directory layouts.

Quality

77%

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-project-structure/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-organized, concrete reference for Python project layout with executable code examples and clear good/avoid contrasts throughout. Its weaknesses are the absence of any ordered procedure with validation checkpoints (especially for the reorganization use case it advertises) and minor redundancy between the Core Concepts and Best Practices Summary.

Suggestions

Add a short ordered procedure to Quick Start (create structure → write pyproject.toml → define __all__ → run tests) so setup/reorganization has a sequence with a validation checkpoint.

Cut the "Best Practices Summary" items that restate Core Concepts verbatim, or merge the two sections to remove redundancy.

Either give pyproject.toml a minimal example in Quick Start or remove it from the tree, since it is never explained.

Move Pattern 6 (Layered) and Pattern 7 (Domain-Driven) into a one-level-deep reference file (e.g., ADVANCED_STRUCTURES.md) linked from an Advanced section.

DimensionReasoningScore

Conciseness

Pattern sections lead directly with concrete examples ("Prefer minimal nesting. Deep hierarchies make imports verbose and navigation difficult") and code blocks carry the weight. Only minor trimming needed: the "Best Practices Summary" restates the Core Concepts nearly verbatim, and the naming/import conventions cover basics Claude already knows. Not 5 because of that redundancy; not 3 since nothing is heavily padded.

4 / 5

Actionability

Copy-paste-ready "__init__.py"/"__all__" examples, a concrete split threshold ("300-500 lines (varies by complexity)"), full directory trees, and matched naming rules ("UserService in user_service.py") make the guidance mostly executable. Not 5: "pyproject.toml" appears in Quick Start with no guidance, and "Reorganizing an existing codebase" is a listed use case with no migration procedure.

4 / 5

Workflow Clarity

Content is organized as parallel patterns rather than any sequenced process: Quick Start is a directory tree, not steps, and there are no validation checkpoints (e.g., verify imports resolve or tests pass after restructuring). The destructive/batch cap does not apply, but neither the sequence of anchor 4 nor the explicit validation of anchor 5 is present.

3 / 5

Progressive Disclosure

No bundle files exist, and the 253-line body is well-sectioned with a logical progression (Quick Start → Fundamental Patterns → Advanced Patterns → Naming → Summary), so navigation is easy. Not 5 because the skill exceeds the single-file small-skill exception: the Advanced Patterns (layered, domain-driven) are self-contained topics that could be split into one-level-deep reference files.

4 / 5

Total

15

/

20

Passed

Description

75%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 solid description that explicitly covers both what and when, with concrete and fairly natural trigger phrases anchored by the distinctive "__all__" keyword. Its main weakness is that the capability half is a noun-list of domains rather than action verbs, leaving coverage slightly less comprehensive than the body warrants.

Suggestions

Convert the what-half into concrete actions, e.g., "Structures Python projects, defines module boundaries and public APIs (__all__), and plans src-layout directory trees".

Add natural synonyms to the trigger clause such as "package structure", "src layout", or "project scaffolding".

Mention test-file organization in the trigger list since it is one of the body's core patterns.

DimensionReasoningScore

Specificity

"Python project organization, module architecture, and public API design" names the domain, and "setting up new projects, organizing modules, defining public interfaces with __all__, planning directory layouts" lists several concrete actions — matching anchor 4. Not 5 because the what-half is a scope list rather than comprehensive action coverage (e.g., test placement and import conventions from the body are absent).

4 / 5

Completeness

Both halves are present: the what ("Python project organization, module architecture, and public API design") and an explicit when ("Use when setting up new projects, organizing modules, defining public interfaces with __all__, or planning directory layouts") with concrete triggers. Not 5 because the what is a noun-scope enumeration rather than the explicit action phrasing of the anchor-5 exemplar.

4 / 5

Trigger Term Quality

Natural phrases like "setting up new projects", "organizing modules", "directory layouts", and the distinctive "__all__" give good keyword coverage. Not 5 because common synonyms such as "package structure", "src layout", or "project scaffolding" are missing.

4 / 5

Distinctiveness Conflict Risk

The "Python" qualifier and distinctive triggers ("__all__", "directory layouts", "module architecture") carve a clear niche. Not 5 because "setting up new projects" and "planning directory layouts" could overlap with a general code-organization or Python-packaging skill.

4 / 5

Total

16

/

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-project-structure/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.