creating-webhook-handlers
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill creating-webhook-handlersCreate webhook endpoints with signature verification, retry logic, and payload validation. Use when receiving and processing webhook events. Trigger with phrases like "create webhook", "handle webhook events", or "setup webhook handler".
Validation
81%| Criteria | Description | Result |
|---|---|---|
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 |
Total | 13 / 16 Passed | |
Implementation
7%This skill fails to deliver on its stated purpose of creating webhook handlers with signature verification, retry logic, and payload validation. It contains no concrete code examples, no webhook-specific implementation details, and relies entirely on external references without providing actionable guidance in the main file. The content reads as generic API boilerplate rather than webhook-specific instruction.
Suggestions
Add executable code examples showing webhook signature verification (e.g., HMAC validation for common providers like Stripe, GitHub)
Include concrete retry logic implementation with exponential backoff and idempotency handling
Provide a clear workflow with validation checkpoints: receive -> verify signature -> validate payload -> process -> acknowledge
Remove generic boilerplate text and prerequisites that don't add webhook-specific value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains significant padding with generic boilerplate text ('This skill provides automated assistance for...'), redundant overview statements, and prerequisites that explain concepts Claude already knows. The content is verbose without adding webhook-specific value. | 1 / 3 |
Actionability | No concrete code examples for webhook signature verification, retry logic, or payload validation despite these being core to the skill's stated purpose. Instructions are vague ('Add input validation', 'Implement endpoint handlers') without executable guidance. | 1 / 3 |
Workflow Clarity | Steps are poorly organized with duplicate numbered lists (two separate '1.' sequences), no validation checkpoints for webhook signature verification, and no feedback loops for handling failed webhook deliveries or retries. | 1 / 3 |
Progressive Disclosure | References external files (implementation.md, errors.md, examples.md) which is appropriate structure, but the main content is too thin to serve as a useful overview. The skill defers almost everything to external files without providing actionable quick-start content. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes natural trigger terms users would actually say, explicitly states both what it does and when to use it, and maintains a clear niche that distinguishes it from related skills. The third-person voice is used correctly throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create webhook endpoints', 'signature verification', 'retry logic', and 'payload validation' - all distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (create webhook endpoints with verification, retry logic, validation) AND when (explicit 'Use when' clause plus 'Trigger with phrases' providing concrete examples). | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'create webhook', 'handle webhook events', 'setup webhook handler', plus terms like 'webhook endpoints' and 'webhook events' that match common user language. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on webhooks with distinct triggers; unlikely to conflict with general API skills or other integration tools due to specific webhook terminology throughout. | 3 / 3 |
Total | 12 / 12 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.