Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

python-architecture

Python system design patterns, project structure, and scalable architecture guidelines

Quality

61%

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 ./skill/python-architecture/SKILL.md

Quality

Content

57%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, mostly executable catalog of Python architecture patterns, but it inlines reference material Claude largely already knows into one monolithic file with no progressive disclosure to supporting files. A few code examples are stubs or buggy.

Suggestions

Move the bulk pattern catalogs into separate reference files (e.g. references/creational.md, references/structural.md, references/async.md) and keep SKILL.md as a concise overview with one-level-deep links.

Replace the stub Strategy sort bodies and fix the retry decorator (return wrapper outside the loop) so all examples are copy-paste ready.

Trim well-known pattern introductions to Python-specific idioms only, trusting Claude's existing knowledge of the underlying patterns.

Dimension	Reasoning	Score
Conciseness	Presentation is code-first with minimal prose padding, but the body largely restates standard GoF/SOLID concepts Claude already knows, so per the guideline penalizing known concepts it sits at anchor 3 ('Mostly efficient but includes some unnecessary explanation') rather than 4.	3 / 5
Actionability	Most examples (Factory, Adapter, Observer, SOLID, REST, async) are concrete, executable Python, but the Strategy sort classes are stubs ('# Implementation here' returning sorted()) and the retry decorator has a control-flow bug, matching anchor 4 ('Mostly executable guidance; minor gaps') not 5.	4 / 5
Workflow Clarity	This is a pattern reference, not a multi-step workflow; sections are well organized but there is no sequenced process with validation checkpoints, matching anchor 3 ('Steps listed but validation gaps') and below 4 which requires explicit checkpoints.	3 / 5
Progressive Disclosure	Content has clear section headers but ~390 lines of patterns are inlined in a single SKILL.md with no bundle files or references to separate files, matching anchor 3 ('Some structure but content that should be separate is inline') rather than 2 thanks to the sectioning.	3 / 5
	Total	13 / 20 Passed

Description

48%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 clearly scopes a Python architecture domain but is noun-heavy with no concrete actions and no 'Use when' trigger guidance, capping completeness at 3. It is reasonably distinct but would benefit from action verbs and explicit trigger phrases.

Suggestions

Lead with concrete verbs, e.g. 'Design, structure, and scale Python applications using system design patterns.'

Add an explicit trigger clause: 'Use when planning Python project structure, applying design patterns, or reasoning about scalable architecture.'

Include natural synonyms users say ('refactoring', 'SOLID', 'clean code', 'code organization') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Python system design patterns, project structure, and scalable architecture guidelines' names the domain and three topic areas but uses no concrete action verbs, matching anchor 2 ('Names the domain but actions are minimal or generic') rather than 3 which requires 1-2 concrete actions.	2 / 5
Completeness	A clear 'what' is present (the three topic areas) but there is no 'when' / 'Use when...' clause, so per the cap rule completeness cannot exceed 3 and matches anchor 3 ('Has a clear what but when is missing').	3 / 5
Trigger Term Quality	'design patterns', 'project structure', and 'scalable architecture' are relevant terms an architect might say, but common synonyms and variations like 'refactoring', 'SOLID', 'clean code', or 'code organization' are absent, matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	The Python-specific architecture niche is mostly distinct with only minor overlap risk against general Python or clean-code skills, matching anchor 4 better than 3 (which implies broader overlap).	4 / 5
	Total	12 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: vircung/opencode-config
Path: skill/python-architecture/SKILL.md
Revision: e2b74bf

Reviewed: 24 days ago

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.

python-architecture

Table of Contents

Is this your skill?