CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

python-error-handling

Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.

Quality

80%

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 ./tests/ext_conformance/artifacts/agents-wshobson/python-development/skills/python-error-handling/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 highly actionable skill with executable, idiomatic examples covering validation, domain types, custom exceptions, chaining, and partial-failure batch handling. Its main cost is redundancy: Core Concepts and the Best Practices Summary restate the patterns, and splitting advanced patterns into a reference file would improve both conciseness and progressive disclosure.

Suggestions

Collapse the 'Core Concepts' section into one-line intros to the corresponding patterns (or delete it) and trim the 10-item 'Best Practices Summary' to points not already shown in code — this removes the triple restatement that drives the conciseness score down.

Fix the small executability gaps: import ValidationError in Pattern 3 ('from pydantic import ValidationError') and show the logging import in Pattern 7's caller block so examples are copy-paste ready.

Move Patterns 5-8 (custom exceptions, chaining, batch partial failures, progress reporting) into a references/advanced-patterns.md linked one level deep from SKILL.md, keeping the main file as a lean overview plus quick start.

DimensionReasoningScore

Conciseness

The body recaps the same guidance three times: the four 'Core Concepts' bullets are restated by Patterns 1, 6, and 7, and the 10-item 'Best Practices Summary' repeats the patterns again, plus a padding intro sentence ('Good error handling makes debugging easier and systems more reliable'). This is more than minor trimming, matching anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') rather than anchor 4.

3 / 5

Actionability

Nearly all examples are executable, complete functions: validation with specific range checks, a Pydantic model with field_validator, custom exception classes with structured context, and a BatchResult with per-item failure tracking. Minor gaps keep it from anchor 5: Pattern 3 catches 'ValidationError' without importing it from pydantic, and Pattern 7's usage block references an unimported 'logger'.

4 / 5

Workflow Clarity

This is a pattern catalog rather than a multi-step process, and it is well organized: when-to-use, quick start, fundamental patterns, then advanced, with each pattern self-contained and the batch pattern (7) embedding per-item error capture and progress reporting. It sits at anchor 4 ('clear sequence with most checkpoints present; minor validation gaps') rather than 5 because no explicit validate-fix-retry loop is demonstrated, though the batch guidance itself is the failure-handling mechanism rather than an unchecked destructive operation.

4 / 5

Progressive Disclosure

No bundle files exist; all 8 patterns are inline in a single ~355-line file. Structure is good with clearly signaled sections (When to Use, Quick Start, Fundamental/Advanced Patterns, summary) and a coherent fundamental-to-advanced split, fitting anchor 4 ('good structure; most content is appropriately placed; minor organization gaps'). Not 5, because the advanced patterns (custom exceptions, chaining, batch, progress) are candidates for a one-level-deep reference file that would slim the main file.

4 / 5

Total

15

/

20

Passed

Description

83%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: concrete capabilities, an explicit and multi-trigger 'Use when' clause, and a clearly scoped Python error-handling niche. The only weaknesses are missing common trigger synonyms (try/except, raise, error messages) and one broad trigger ('building robust APIs') that risks overlap with general API skills.

DimensionReasoningScore

Specificity

The description names the domain ('Python error handling patterns') and three concrete capability areas ('input validation, exception hierarchies, and partial failure handling'). It lists several specific actions but omits other facets the skill covers (error messages, exception chaining, logging), so it fits anchor 4 rather than the comprehensive coverage of 5 or the 1-2 actions of 3.

4 / 5

Completeness

It explicitly answers both what ('Python error handling patterns including input validation, exception hierarchies, and partial failure handling') and when ('Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs') with concrete trigger phrases, matching the anchor 5 example structure. Not 4, because the 'when' clause is explicit and specific rather than improvable.

5 / 5

Trigger Term Quality

The 'Use when' clause supplies natural user phrases: 'implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs'. Coverage is good but misses common variations users would say, such as 'try/except', 'raise', or 'error messages', placing it at anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

A Python-scoped error-handling niche with distinct triggers (validation logic, exception strategies, batch failures) is mostly distinct, but 'building robust APIs' is a broad surface overlapping general API-building skills, fitting anchor 4 rather than the minimal-conflict niche of 5.

4 / 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

Dicklesworthstone/pi_agent_rust

Path

tests/ext_conformance/artifacts/agents-wshobson/python-development/skills/python-error-handling/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.