python-mypy

Static type checking with Mypy for Python code quality. Use when writing or reviewing Python code to ensure type safety, catch bugs early, and maintain code quality through proper type annotations and Mypy configuration.

Quality

62%

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/python-experts/skills/python-mypy/SKILL.md

Quality

Content

50%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 thorough, executable reference for Mypy typing patterns and configuration, scoring well on actionability. It is held back by significant verbosity — re-teaching typing concepts Claude already knows — and by a reference-catalog structure with no progressive disclosure or validation workflow.

Suggestions

Cut tutorial explanations of concepts Claude already knows (Optional, Protocol, TypedDict, generics, overloads); keep only non-obvious Mypy-specific guidance and the minimal executable examples.

Move the bulk of config reference and domain integrations (mypy.ini/pyproject blocks, Django plugin section, anti-pattern catalog) into separate reference files and link to them one level deep from SKILL.md.

Add an explicit run-and-fix workflow with a validation checkpoint, e.g. 'run mypy --show-error-codes; if errors, fix and re-run until clean', to improve workflow clarity for the destructive/batch aspect of type-check runs.

Dimension	Reasoning	Score
Conciseness	At ~440 lines the body extensively documents concepts Claude already knows (Optional, Protocol, TypedDict, generics, overloads, Django models) with tutorial-style comments like '# Mypy knows value is str here', which is noticeably padded rather than lean; it sits below the mostly-efficient anchor 3.	2 / 5
Actionability	It provides many complete, executable code and config examples (mypy.ini, pyproject.toml, CI YAML, annotated functions) with only minor gaps such as undefined symbols (Connection, get_connection) in a couple of samples, keeping it just below fully copy-paste-ready anchor 5.	4 / 5
Workflow Clarity	The 'Gradual Adoption' section gives a numbered sequence, but the skill is primarily a reference catalog rather than a sequenced workflow, and there are no validation/retry checkpoints for running Mypy and fixing reported errors, so it sits at the steps-present-but-checkpoints-implicit anchor 3.	3 / 5
Progressive Disclosure	There are no bundle files (references/scripts/assets) and everything is inlined into SKILL.md; section headers provide some structure but large reference blocks (mypy.ini, anti-patterns, Django integration) that could live in separate files are inline, and external links are plain markdown rather than well-signaled one-level references.	3 / 5
	Total	12 / 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.

The description clearly states both what the skill does (Mypy-based static type checking) and when to use it (writing/reviewing Python code), using third person and concrete actions. It is well above the midpoint but stops short of the top anchor due to generic triggers and minor overlap with general Python quality skills.

Suggestions

Add concrete trigger terms and synonyms such as 'type hints', 'type annotations', '.py files', 'mypy.ini', or 'pyproject.toml' to match how users actually request type checking.

Tighten the 'when' clause with specific scenarios, e.g. 'Use when adding or reviewing type annotations, configuring Mypy, or diagnosing Mypy errors'.

Sharpen distinctiveness by contrasting with adjacent skills, e.g. 'Focuses on static type checking; for style see python-style'.

Dimension	Reasoning	Score
Specificity	It names the domain (static type checking with Mypy) and lists several concrete actions — 'catch bugs early', 'ensure type safety', 'maintain code quality through proper type annotations and Mypy configuration' — which is solid coverage with only minor gaps versus the comprehensive anchor 5.	4 / 5
Completeness	It answers both 'what' (static type checking, type safety, catching bugs) and 'when' ('Use when writing or reviewing Python code'), but the 'when' clause is fairly generic and could name more specific trigger scenarios, keeping it below anchor 5.	4 / 5
Trigger Term Quality	Natural phrases like 'writing or reviewing Python code' and 'type annotations' align with what users say, but it omits common synonyms and explicit file/extension triggers (e.g. '.py', 'type hints', 'mypy.ini', 'pyproject'), so it sits just below the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	The Mypy niche is clear and largely distinct from sibling skills, though 'code quality through type annotations' overlaps somewhat with general Python style/review skills, leaving minor conflict risk versus anchor 5.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jpoutrin/product-forge
Path: plugins/python-experts/skills/python-mypy/SKILL.md
Commit: 0ebe7ae

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.