python-typing-patterns

Python type hints and type safety patterns. Triggers on: type hints, typing, TypeVar, Generic, Protocol, mypy, pyright, type annotation, overload, TypedDict.

1.06x

Quality

65%

Does it follow best practices?

Impact

92%

1.06x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xdarkmatter/claude-mods/python-typing-patterns/SKILL.md

Quality

Content

65%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 content is a clean, executable typing reference that respects the token budget and points advanced topics to separate files. Its main weaknesses are the missing validate-fix-retry loop around type checking and the fact that all referenced bundle files are absent from the skill directory.

Suggestions

Add the referenced bundle files (references/*.md, scripts/check-types.sh, assets/pyproject-typing.toml) or remove the broken links.

Add a short validate->fix->retry loop after the mypy/pyright commands so type-checking errors are handled explicitly.

Ensure every code snippet includes the imports it depends on (e.g. json, io, db stub) so examples are fully runnable.

Dimension	Reasoning	Score
Conciseness	The body is lean and mostly executable code with no padding of basic concepts, retaining only a few inline comments and short intros that could be trimmed, matching the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	Each section provides concrete, copy-paste-ready code plus a quick-reference table and real commands (mypy/pyright), but a few snippets rely on undefined names (db, json, io) or omitted imports, leaving minor gaps below fully executable.	4 / 5
Workflow Clarity	As a reference skill it is well structured, but the type-checker section runs batch validation (mypy/pyright) with no validate->fix->retry feedback loop, capping it at the 'validation gaps / checkpoints implicit' anchor.	3 / 5
Progressive Disclosure	Sections are well organized and advanced topics are correctly pushed to reference files with clear descriptions, but the six referenced files (plus one script and one asset) do not exist in the bundle, leaving the disclosure partly broken rather than a minor gap.	3 / 5
	Total	14 / 20 Passed

Description

65%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 pairs an explicit trigger list with a clear domain, giving strong discoverability and distinctiveness, but it states capabilities at a topic level rather than naming concrete actions. Tightening the 'what' clause into specific verbs would push specificity and completeness higher.

Suggestions

Replace the topic-level 'what' with concrete verbs, e.g. 'Add and validate Python type hints for safe, documented code.'

Add a few common trigger synonyms to the list (type checking, static types, Optional, Union) for fuller coverage.

Consider an explicit 'Use when...' phrasing instead of 'Triggers on:' to mirror the anchor's ideal form.

Dimension	Reasoning	Score
Specificity	The phrase 'Python type hints and type safety patterns' names the domain and concept but lists no concrete actions (no verbs like add/annotate/validate), matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	Both a 'what' (type hints and type safety patterns) and an explicit 'when' ('Triggers on: ...') are present, but the 'what' is topic-level rather than a concrete capability description, so it falls just below the top anchor.	4 / 5
Trigger Term Quality	The 'Triggers on:' list covers highly natural technical terms (type hints, typing, mypy, pyright, Protocol, TypedDict, overload) including synonyms and tool names, but omits a few common variations (type checking, static types, Optional, Union).	4 / 5
Distinctiveness Conflict Risk	Typing-specific triggers (TypeVar, Protocol, mypy, pyright, TypedDict) carve a clear niche with low conflict risk, with only minor overlap against related typing-adjacent skills (Pydantic/Pytest types).	4 / 5
	Total	14 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: NeverSight/skills_feed
Path: data/skills-md/0xdarkmatter/claude-mods/python-typing-patterns/SKILL.md
Commit: 2f57aec

Reviewed: about 22 hours 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.