CtrlK
BlogDocsLog inGet started
Tessl Logo

python-typing-patterns

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

86

1.06x
Quality

Does it follow best practices?

Impact

92%

1.06x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an excellent, concise, executable pattern catalog with clear sections and concrete validation commands. The one weakness is progressive disclosure: every referenced bundle file is a dangling link because the references/, scripts/, and assets/ directories are missing.

Suggestions

Create the referenced bundle files (generics-advanced.md, protocols-patterns.md, type-narrowing.md, mypy-config.md, runtime-validation.md, overloads.md, scripts/check-types.sh, assets/pyproject-typing.toml) or remove the broken references.

If keeping the references, ensure each one-line description matches the file's actual scope so navigation delivers on its promise.

DimensionReasoningScore

Conciseness

The body is lean and code-forward with minimal prose, showing patterns directly rather than explaining what typing constructs are; every comment earns its place (e.g. noting the 3.10+ requirement is actionable).

3 / 3

Actionability

Examples are executable Python with real imports and complete signatures, plus runnable mypy/pyright commands and a copy-paste pyproject snippet, making the guidance concrete and ready to use.

3 / 3

Workflow Clarity

As a single-purpose pattern reference the action is unambiguous (apply these patterns, then validate with mypy/pyright), and there are no destructive or batch operations that would require validation checkpoints.

3 / 3

Progressive Disclosure

The SKILL.md is a well-signaled overview pointing to one-level-deep references, but the referenced ./references/*.md, ./scripts/check-types.sh, and ./assets/*.toml files do not exist, so navigation is broken despite good structural intent.

2 / 3

Total

11

/

12

Passed

Description

72%

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 has strong, explicit trigger guidance and a distinctive typing niche, but its capability statement is a topic description rather than a list of concrete actions. Tightening the 'what' into specific verbs would raise specificity and completeness.

Suggestions

Replace the topic phrase with concrete actions, e.g. 'Annotate functions and data structures, define generic and Protocol types, configure mypy/pyright, and apply type-narrowing patterns.'

Keep the explicit 'Triggers on:' clause but consider framing the opening as 'Use when...' to match the rubric's preferred trigger-guidance phrasing.

DimensionReasoningScore

Specificity

Names the domain ('Python type hints and type safety patterns') and key mechanisms, but describes topics rather than listing concrete actions a user would invoke; actions are implied rather than stated.

2 / 3

Completeness

The 'when' is answered explicitly via the 'Triggers on:' clause, but the 'what' is only a topic phrase ('type hints and type safety patterns') rather than a concrete capability statement, so it does not fully answer both.

2 / 3

Trigger Term Quality

The 'Triggers on:' clause lists natural terms users would say (type hints, typing, type annotation, mypy, pyright) plus specific library terms, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Typing-specific triggers (TypeVar, Protocol, TypedDict, mypy, pyright) carve a clear niche that is unlikely to fire for unrelated Python skills.

3 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
NeverSight/skills_feed
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.