retry-logic-helper
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill retry-logic-helperRetry Logic Helper - Auto-activating skill for API Integration. Triggers on: retry logic helper, retry logic helper Part of the API Integration skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, appearing to be auto-generated boilerplate rather than a thoughtful skill description. It lacks any concrete actions, meaningful trigger terms, or usage guidance. The skill name is simply repeated as the trigger, providing no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Implements exponential backoff, configures retry attempts, handles rate limiting and timeout errors for API calls'
Add a 'Use when...' clause with natural trigger terms like 'Use when implementing retry logic, handling API failures, rate limits, timeouts, or when requests need automatic retry with backoff'
Include common user phrases and file/code patterns that would indicate this skill is needed, such as 'failed request', 'connection error', 'retry mechanism', '429 error', 'exponential backoff'
| 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 has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Both the what and when are essentially missing. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('retry logic helper, retry logic helper'). Missing natural user terms like 'retry', 'backoff', 'failed request', 'API error', 'timeout', 'rate limit', or 'connection retry'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'retry logic' is somewhat specific to error handling patterns, the vague 'API Integration' category and lack of concrete details means it could overlap with other API-related skills. The repeated trigger term doesn't help differentiate it. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no substantive content. It describes what a retry logic helper skill should do but provides absolutely no actual guidance, code, patterns, or implementation details. The entire content could be replaced with actual retry logic examples (exponential backoff, jitter, circuit breakers) in fewer tokens.
Suggestions
Add concrete, executable code examples showing retry patterns (e.g., exponential backoff with jitter implementation in Python/JavaScript)
Include specific guidance on retry configuration: max attempts, base delay, backoff multiplier, timeout handling
Provide examples of when to retry vs. when to fail (idempotent operations, transient vs. permanent errors, HTTP status codes)
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual implementation details
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific retry patterns, no actual implementation details. The content only describes what the skill claims to do without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The skill mentions 'step-by-step guidance' but provides none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure pointing to detailed materials. No references to implementation guides, examples, or API documentation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.