CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

python-type-safety

Python type safety with type hints, generics, protocols, and strict type checking. Use when adding type annotations, implementing generic classes, defining structural interfaces, or configuring mypy/pyright.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 patterns skill with substantive, mostly executable examples and a textbook one-level-deep reference split. The main improvement opportunities are removing the redundant Core Concepts preamble and grounding examples in concrete types.

Suggestions

Cut or merge the "Core Concepts" section — its one-line definitions duplicate the Fundamental Patterns that follow and restate knowledge Claude already has.

Make at least the Quick Start example fully self-contained/executable (e.g. define a minimal User dataclass or use built-in types) so it can be run as-is.

DimensionReasoningScore

Conciseness

The body is dominated by useful code examples with brief guidance, but the "Core Concepts" section one-lines concepts Claude already knows ("Write reusable code that preserves type information across different types") and duplicates the Patterns that follow — minor over-explanation that could be trimmed, matching the 4 anchor.

4 / 5

Actionability

Concrete commands ("mypy --strict", pyproject.toml config) and structurally complete code cover the common cases, but examples rely on undefined domain types (User, Database, Item) and `...` placeholder bodies, so they are not fully copy-paste ready — below the 5 anchor, well above pseudocode.

4 / 5

Workflow Clarity

This is a patterns/reference skill, not a multi-step process: content follows a clear, unambiguous progression (Quick Start → Fundamental Patterns → references → best-practices checklist) with no destructive or batch operations requiring validation checkpoints, which fits the 4 anchor better than the explicit-sequence-with-validation 5 anchor.

4 / 5

Progressive Disclosure

The body keeps fundamental patterns inline and moves advanced material to references/details.md with a clear, well-signaled pointer ("Detailed sections (starting with `## Advanced Patterns`) live in `references/details.md`"), and the referenced file and section both exist — one level deep, appropriately split, easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

82%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 strong description with explicit what/when structure and distinctive tool-name triggers. Its main weakness is that the capability statement is a topic inventory rather than a list of concrete actions, which limits specificity.

Suggestions

Rewrite the capability clause with action verbs, e.g. "Add type annotations to Python code, implement generic classes and Protocol-based interfaces, and configure mypy/pyright for strict type checking."

Add common user phrasings such as "typing", "static type checking", or "type errors" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain and specific subtopics ("type hints, generics, protocols, and strict type checking") but presents a topic list rather than concrete actions, matching the 'names domain and 1-2 concrete actions' anchor rather than the action-verb list of the 4 anchor.

3 / 5

Completeness

It explicitly answers both what ("Python type safety with type hints, generics, protocols, and strict type checking") and when ("Use when adding type annotations, implementing generic classes, defining structural interfaces, or configuring mypy/pyright") with concrete trigger phrases, matching the top anchor's structure.

5 / 5

Trigger Term Quality

Good natural trigger coverage — "type hints", "type annotations", "generic classes", "structural interfaces", "mypy", "pyright" — but common variations like "typing", "static type checking", or "type errors" are missing, placing it between the 3 and 5 anchors.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (Python static typing) with distinct tool-name triggers like mypy and pyright that would not fire for unrelated skills, satisfying the 'clear niche with distinct triggers' anchor.

5 / 5

Total

17

/

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-type-safety/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.