CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

python-development

Modern Python coding standards, best practices, testing patterns, and implementation guidelines

Quality

52%

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 ./skill/python-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 dense, topical catalog of modern Python patterns with mostly executable examples, but it is padded with explanations of concepts Claude already knows, contains several code defects and a broken fence, and inlines ~555 lines with no external reference structure.

Suggestions

Strip commentary that restates common knowledge (e.g. what Pylance does, what generics are) and remove duplicated definitions such as the two `DatabaseConfig`/`process_user_data` versions.

Fix the broken code fence in the 'Development Workflow with Static Analysis' section and replace invalid `any` with `Any`; remove undefined `get_user` and the deprecated Pydantic v1 `Config` class.

Move the bulk API examples, logging config, and pre-commit/ruff configuration into separate reference files and link to them from a concise overview, so SKILL.md stays a lean entry point.

DimensionReasoningScore

Conciseness

Many comments restate what Claude already knows ('Pylance provides real-time type checking', 'Generic types', 'Now Pylance knows user is not None') and there is redundant/duplicated code, placing it at 'Noticeably verbose; several unnecessary explanations or padded sections'.

2 / 5

Actionability

Code is mostly concrete and executable, but contains real defects: a broken code fence that drops mid-method into TOML/YAML, invalid lowercase `any` instead of `Any`, undefined `get_user`, and a deprecated Pydantic v1 `Config` class — gaps beyond the 'minor' threshold for a 4.

3 / 5

Workflow Clarity

This is a topical pattern catalog rather than a sequenced multi-step process; sections are organized by topic but there is no ordered workflow or validation checkpoints, matching 'Steps listed but ... checkpoints missing'.

3 / 5

Progressive Disclosure

No bundle files exist and all ~555 lines are inlined in SKILL.md; substantial API and config material that clearly belongs in separate reference files is inlined, matching 'content that clearly belongs in separate files is inlined'.

2 / 5

Total

10

/

20

Passed

Description

45%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 identifies the Python domain and its main topic areas but stops at generic category labels with no concrete actions or 'when to use' guidance. It is adequately specific but lacks trigger phrases and completeness.

Suggestions

Add a concrete action verb list, e.g. 'Apply type hints, write pytest fixtures, configure ruff/mypy, and structure async code'.

Append an explicit 'Use when...' clause naming natural trigger phrases such as 'write Python', 'add type hints', 'set up pytest', or 'refactor Python'.

Narrow the niche with distinct triggers (e.g. 'Modern Python 3.10+ with type hints, dataclasses/Pydantic, and pytest') to reduce overlap with generic coding-style skills.

DimensionReasoningScore

Specificity

Names the Python domain and several categories ('coding standards, best practices, testing patterns, and implementation guidelines') but uses only generic noun-phrases with no concrete verbs, placing it below the midpoint toward 'Names the domain but actions are minimal or generic'.

2 / 5

Completeness

Provides a clear 'what' but no 'Use when...' or equivalent trigger clause; per the judging guidelines a missing 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant natural terms ('Python coding standards', 'best practices', 'testing patterns') but lacks synonyms and specific trigger keywords (e.g. 'type hints', 'pytest', 'refactor'), matching 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

Python-specific language narrows the niche, but 'coding standards / best practices' is broad enough to overlap with general linting or coding-style skills, matching 'Somewhat specific but could still overlap with similar skills'.

3 / 5

Total

11

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (566 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

vircung/opencode-config

Path

skill/python-development/SKILL.md

Revision

e2b74bf

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill