webhook-retry-handler
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill webhook-retry-handlerWebhook Retry Handler - Auto-activating skill for API Integration. Triggers on: webhook retry handler, webhook retry handler Part of the API Integration skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with no substantive content. It fails to explain what the skill does, provides no natural trigger terms beyond the skill name itself, and offers no guidance on when Claude should select it. The description would be nearly useless for skill selection among multiple options.
Suggestions
Add specific actions the skill performs, e.g., 'Handles failed webhook deliveries by implementing exponential backoff retry logic, tracking delivery attempts, and managing dead letter queues.'
Include a 'Use when...' clause with natural trigger terms: 'Use when webhooks fail to deliver, when implementing retry logic for HTTP callbacks, or when the user mentions webhook timeouts, delivery failures, or retry policies.'
Add common user phrases and variations: 'webhook failed', 'retry webhook', 'webhook not delivered', 'callback retry', 'HTTP callback failure'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Webhook Retry Handler') and category ('API Integration') without describing any concrete actions. No specific capabilities like 'retry failed webhooks', 'configure retry intervals', or 'log delivery attempts' are mentioned. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. There's no explanation of functionality and no 'Use when...' clause or equivalent guidance for when to select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('webhook retry handler, webhook retry handler'). Missing natural user terms like 'webhook failed', 'retry delivery', 'webhook timeout', 'resend webhook', or 'delivery failure'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'webhook retry' is somewhat specific to a particular domain, which provides some distinctiveness. However, without concrete actions described, it could still overlap with general API error handling or webhook management skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual webhook retry handler implementation guidance. It contains zero executable code, no retry patterns (exponential backoff, jitter, max attempts), no webhook signature validation, and no error handling strategies. The content tells Claude what the skill supposedly does rather than teaching Claude how to do it.
Suggestions
Add concrete code examples showing webhook retry implementation with exponential backoff, including specific retry intervals and max attempt configurations
Include a clear workflow for handling webhook failures: receive -> validate signature -> process -> respond with appropriate status codes -> retry logic on failure
Provide specific patterns for idempotency keys, dead letter queues, and logging failed webhook attempts
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about webhook retry handling. Every section describes what the skill does abstractly rather than providing actual guidance Claude could use. | 1 / 3 |
Actionability | No concrete code, commands, or specific implementation details are provided. The content only describes that it 'provides step-by-step guidance' and 'generates production-ready code' without actually including any such guidance or code. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for implementing webhook retry logic, no validation checkpoints, and no error handling patterns despite this being a domain where retry logic and failure handling are critical. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no examples, and no links to related documentation. It's neither a useful overview nor does it point to deeper content. | 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.