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 defines its scope around Python resilience patterns, lists concrete capabilities, and includes an explicit 'Use when' clause with natural trigger terms. It follows third-person voice, is concise without being vague, and carves out a distinct niche that minimizes conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: automatic retries, exponential backoff, timeouts, and fault-tolerant decorators. These are well-defined, concrete patterns rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both 'what' (Python resilience patterns including retries, backoff, timeouts, decorators) and 'when' (explicit 'Use when' clause covering retry logic, timeouts, fault-tolerant services, transient failures). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'retry logic', 'timeouts', 'fault-tolerant', 'transient failures', 'exponential backoff', 'retries'. These cover the common terms developers use when seeking resilience patterns. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around resilience/fault-tolerance patterns in Python. The specific trigger terms like 'retry logic', 'exponential backoff', and 'transient failures' are unlikely to conflict with other skills such as general error handling or networking 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 excellent code examples covering a comprehensive range of resilience patterns. Its main weaknesses are verbosity (explaining concepts Claude already knows, like what exponential backoff and jitter are) and the monolithic structure that could benefit from splitting advanced patterns into a referenced file. The lack of testing/validation guidance for the patterns is a notable gap.
Suggestions
Remove the 'Core Concepts' section entirely - Claude already understands transient failures, exponential backoff, jitter, and bounded retries. The code examples demonstrate these concepts more effectively.
Split Patterns 5-9 into a separate ADVANCED_PATTERNS.md and reference it from the main skill to improve progressive disclosure and reduce token usage.
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, jitter - concepts Claude already knows). The 'When to Use This Skill' section is also somewhat redundant. However, the code examples themselves are lean and well-structured. | 2 / 3 |
Actionability | All patterns include fully executable, copy-paste ready code examples 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 for ensuring resilience is properly configured. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections (Quick Start → Fundamental → Advanced → Best Practices), but at ~250 lines it's quite long and monolithic. Patterns 5-9 could be split into a separate ADVANCED_PATTERNS.md file with references from the main skill. No external file references are used. | 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
03d0b4b
- 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.