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.
86
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 well-crafted skill description that excels across all dimensions. It uses third-person voice, lists specific concrete capabilities, includes natural trigger terms developers would use, and has an explicit 'Use when...' clause with clear activation scenarios. The resilience/fault-tolerance focus creates a distinct niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'automatic retries, exponential backoff, timeouts, and fault-tolerant decorators'. These are precise technical capabilities, not vague abstractions. | 3 / 3 |
Completeness | Clearly answers both what ('Python resilience patterns including automatic retries, exponential backoff, timeouts, and fault-tolerant decorators') and when ('Use when adding retry logic, implementing timeouts, building fault-tolerant services, or handling transient failures'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'retry logic', 'timeouts', 'fault-tolerant', 'transient failures', 'backoff'. These cover common variations of how developers describe resilience needs. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on resilience/fault-tolerance patterns with distinct triggers like 'retry', 'backoff', 'transient failures'. Unlikely to conflict with general Python skills or other domains. | 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 that are production-ready. The main weaknesses are unnecessary conceptual explanations that Claude doesn't need, and the lack of workflow guidance for choosing between patterns or validating implementations. The content would benefit from trimming the Core Concepts section and adding decision criteria or a testing/validation workflow.
Suggestions
Remove or significantly condense the 'Core Concepts' section - Claude understands exponential backoff, jitter, and transient vs permanent failures without explanation
Add a decision flowchart or criteria table for choosing which pattern to apply (e.g., 'Use Pattern 3 when you need to retry based on HTTP status codes, Pattern 4 when you need both exception and status handling')
Include a brief validation/testing section showing how to verify retry behavior works correctly (e.g., using tenacity's statistics or mocking failures in tests)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary conceptual explanations (Core Concepts section explaining transient vs permanent failures, exponential backoff, jitter) that Claude already understands. The content is generally well-organized but could be tightened by removing these explanations and focusing purely on implementation patterns. | 2 / 3 |
Actionability | Excellent executable code examples throughout. Every pattern includes complete, copy-paste ready Python code with proper imports, type hints, and realistic usage. The examples are production-quality using tenacity library with proper configuration. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, there's no explicit workflow for when to apply which pattern or how to validate that retry logic is working correctly. Missing guidance on testing retry behavior or verifying backoff timing. The patterns are presented as independent options without clear decision criteria. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections (Quick Start, Fundamental Patterns, Advanced Patterns), but it's a monolithic document with no references to external files for detailed topics. The 200+ lines could benefit from splitting advanced patterns into separate files with clear navigation. | 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.
- 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.