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

82%

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

71%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-structured patterns skill with mostly executable, concrete code and excellent progressive disclosure (a real, one-level-deep, clearly signaled reference). Its main weakness is token efficiency: Core Concepts, the built-in exception table, and the Best Practices Summary largely restate knowledge Claude already has or duplicate each other, and a few code examples have small gaps (missing ValidationError import, undefined Page type).

Suggestions

Remove the 'Core Concepts' section and the built-in exception mapping table — Claude already knows fail-fast, exception chaining, and which built-in exceptions mean what; the Best Practices Summary already condenses the same guidance.

Fix Pattern 3: import ValidationError ("from pydantic import ValidationError") and remove or complete the export_data example so it matches its declared '-> bytes' return type.

Merge 'Best Practices Summary' with 'Quick Start' (or keep only one) to eliminate the near-duplicate coverage of the same ten points currently spread across three sections.

DimensionReasoningScore

Conciseness

The body re-teaches concepts Claude already knows ("Validate inputs early, before expensive operations", "Chain exceptions to maintain the full error trail") in Core Concepts, and the built-in exception table ("Invalid input | ValueError", "Wrong type | TypeError") restates standard Python knowledge; the 10-item Best Practices Summary then duplicates Core Concepts almost verbatim. The code patterns themselves are on-point, so this is mostly efficient but could be tightened rather than noticeably verbose.

3 / 5

Actionability

Patterns 1, 2, and 4 are fully executable (e.g., "raise ValueError(f"'page_size' must be 1-100, got {page_size}")"), but Pattern 3 catches ValidationError without importing it, export_data declares "-> bytes" yet returns only "...", and Quick Start references an undefined Page type. These minor gaps keep it below fully copy-paste ready.

4 / 5

Workflow Clarity

This is a patterns-reference skill, not a sequential workflow, and its organization (When to Use → Quick Start → numbered Patterns 1–4 → Best Practices) is unambiguous with no risky multi-step process needing checkpoints. Clear structure with minor gaps — e.g., the pointer section "Detailed worked examples and patterns" is an awkward heading — fits 4.

4 / 5

Progressive Disclosure

Scored against the actual bundle: references/details.md exists, is one level deep, and genuinely contains "## Advanced Patterns" as the body states; the pointer ("Read that file when the navigation summary above is insufficient") is clearly signaled with a read condition, and advanced patterns are appropriately split out of the overview.

5 / 5

Total

16

/

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: third-person voice, concrete capabilities, and an explicit multi-trigger 'Use when' clause that together answer both what and when. The only room for improvement is broader natural trigger phrasing (try/except, raising exceptions) and slightly tighter scoping of the broadest triggers.

DimensionReasoningScore

Specificity

"Python error handling patterns including input validation, exception hierarchies, and partial failure handling" names the domain plus three concrete actions, matching the several-specific-actions anchor. Not 5: it omits capabilities the body covers (exception chaining, custom exception classes), leaving minor gaps in coverage.

4 / 5

Completeness

It explicitly answers both parts: the "what" ("Python error handling patterns including input validation, exception hierarchies, and partial failure handling") and a concrete "when" ("Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs"). This matches the anchor for clearly and explicitly answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural terms users would say are present — "error handling", "input validation", "exception hierarchies", "batch processing failures" — but common phrasings like "try/except", "raising exceptions", or "error messages" are missing. Good coverage with a few natural terms missing fits 4 rather than the comprehensive synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

"Python error handling" carves a clear niche with Python-specific triggers, but "implementing validation logic" and "building robust APIs" are broad enough to overlap with validation-library or API-framework skills. Minor overlap risk with closely related skills fits 4, not 5's minimal-conflict bar.

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

wshobson/agents

Path

plugins/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.