python-resilience
Python resilience patterns including automatic retries, exponential backoff, timeouts, and fault-tolerant decorators. Use when adding retry logic, implementing timeouts, building fault-tolerant services, or handling transient failures.
88
82%
Does it follow best practices?
Impact
100%
1.16xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies the domain (Python resilience patterns), lists specific capabilities (retries, exponential backoff, timeouts, fault-tolerant decorators), and provides explicit trigger guidance via a 'Use when...' clause. It uses proper third-person voice and includes natural keywords that users would actually use when seeking this functionality.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'automatic retries, exponential backoff, timeouts, and fault-tolerant decorators' — these are all distinct, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (resilience patterns including retries, backoff, timeouts, decorators) and 'when' with an explicit 'Use when...' clause listing four trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'retry logic', 'timeouts', 'fault-tolerant', 'transient failures', 'exponential backoff', 'retries'. These cover common variations of how users would describe these needs. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Python resilience/fault-tolerance patterns with distinct triggers like 'retry logic', 'exponential backoff', and 'transient failures' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with high-quality executable code examples covering a good range of resilience patterns. Its main weaknesses are verbosity in explanatory sections that Claude doesn't need (core concepts, when-to-use), and the monolithic structure that packs 9 detailed patterns into a single file without progressive disclosure. Adding validation/testing guidance and splitting advanced patterns into a separate file would improve it significantly.
Suggestions
Remove or drastically condense the 'Core Concepts' and 'When to Use This Skill' sections — Claude already understands these concepts and the description metadata covers the use cases.
Split advanced patterns (5-9) into a separate ADVANCED_PATTERNS.md file, keeping only the Quick Start and Fundamental Patterns (1-4) in SKILL.md with clear references.
Add a brief testing/validation section showing how to verify retry behavior works correctly (e.g., using tenacity's retry statistics or a simple test with mock failures).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory content (e.g., 'Core Concepts' section explaining transient vs permanent failures, exponential backoff, and jitter are concepts Claude already knows). The 'When to Use This Skill' section is also somewhat redundant given the description. However, the code examples themselves are lean and well-structured. | 2 / 3 |
Actionability | All patterns include fully executable, copy-paste ready Python code with proper imports, type hints, and realistic usage. The examples use real libraries (tenacity, httpx, structlog) with concrete configurations rather than pseudocode. | 3 / 3 |
Workflow Clarity | The patterns are presented as independent recipes rather than a sequenced workflow, which is appropriate for a patterns skill. However, there's no guidance on how to validate that retry logic is working correctly, no testing examples for the patterns, and no verification steps. The best practices summary is a flat list without prioritization or decision guidance for choosing between patterns. | 2 / 3 |
Progressive Disclosure | The content is organized with clear sections (Quick Start → Fundamental → Advanced → Best Practices), which is good structure. However, at ~250 lines with 9 patterns, much of the advanced content could be split into separate reference files. With no bundle files, everything is monolithic in a single SKILL.md. | 2 / 3 |
Total | 9 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
ece811f
- 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.