retry-logic-helper
Retry Logic Helper - Auto-activating skill for API Integration. Triggers on: retry logic helper, retry logic helper Part of the API Integration skill category.
36
Quality
3%
Does it follow best practices?
Impact
98%
1.06xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/16-api-integration/retry-logic-helper/SKILL.mdQuality
Discovery
7%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 description is essentially a placeholder that provides almost no useful information for skill selection. It names the skill and category but fails to describe any concrete capabilities, use cases, or natural trigger terms. Claude would have difficulty knowing when to select this skill over others without understanding what retry logic operations it actually performs.
Suggestions
Add specific actions the skill performs, e.g., 'Implements retry patterns with exponential backoff, configures maximum retry attempts, handles transient API failures and rate limit responses.'
Replace the duplicate trigger term with natural user phrases: 'Use when handling API failures, implementing exponential backoff, dealing with rate limits, connection timeouts, or transient errors.'
Add a 'Use when...' clause that explicitly describes scenarios: 'Use when the user needs to handle failed API calls, implement resilient request patterns, or configure retry behavior for unreliable endpoints.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Retry Logic Helper') and mentions 'API Integration' but provides no concrete actions. There's no explanation of what the skill actually does - no verbs describing capabilities like 'implements exponential backoff', 'handles failed requests', or 'configures retry attempts'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name rather than describing actual use cases or scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('retry logic helper, retry logic helper'). Missing natural user phrases like 'retry failed requests', 'exponential backoff', 'handle API errors', 'rate limiting', or 'connection timeout'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'retry logic' is somewhat specific to error handling patterns, the lack of detail means it could overlap with general API error handling, rate limiting, or resilience pattern skills. The 'API Integration' category provides some context but is still broad. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual content about retry logic. It contains only meta-descriptions of what a skill should do without any concrete implementation guidance, code examples, or retry patterns (exponential backoff, jitter, circuit breakers, etc.). The skill provides zero value as it teaches Claude nothing it doesn't already know.
Suggestions
Add concrete retry logic code examples with exponential backoff, jitter, and maximum retry limits
Include specific patterns for different failure types (network errors, rate limits, transient vs permanent failures)
Provide a clear workflow: detect failure -> classify error -> apply retry strategy -> validate success or escalate
Add examples for common libraries/frameworks (e.g., tenacity for Python, axios-retry for JavaScript)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no actual technical substance. It explains what the skill does in abstract terms without providing any concrete retry logic implementation, patterns, or code examples. | 1 / 3 |
Actionability | No executable code, no specific commands, no concrete examples of retry logic patterns. The content only describes what it could do rather than providing actual guidance on implementing retry logic. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but contains zero actual steps. No validation checkpoints, no error handling patterns, no retry strategies explained. | 1 / 3 |
Progressive Disclosure | No structure beyond boilerplate sections. No references to detailed documentation, no examples file, no API reference. The content is a template shell with no actual information to organize. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.