webhook-sender-creator
Webhook Sender Creator - Auto-activating skill for API Integration. Triggers on: webhook sender creator, webhook sender creator Part of the API Integration skill category.
36
3%
Does it follow best practices?
Impact
99%
1.04xAverage 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/webhook-sender-creator/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 extremely weak across all dimensions. It reads as an auto-generated template with no substantive content—just the skill name repeated as trigger terms and a category label. It provides no concrete actions, no natural trigger terms, and no guidance on when Claude should select this skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates webhook sender endpoints, configures HTTP POST callbacks, sets up payload templates, and tests webhook delivery to external services.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to send webhooks, set up HTTP callbacks, create webhook integrations, POST notifications to external URLs, or configure event-driven API calls.'
Replace the duplicated trigger term with diverse natural language variations users might say, such as 'webhook', 'HTTP callback', 'event notification', 'POST to URL', 'webhook integration', 'outgoing webhook'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Webhook Sender Creator') and its category ('API Integration') but provides no concrete actions. There is no indication of what the skill actually does—no verbs like 'creates', 'sends', 'configures', etc. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('webhook sender creator, webhook sender creator'). There are no natural user phrases like 'send webhook', 'create webhook endpoint', 'HTTP callback', 'POST request', or other variations a user might naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'webhook' provides some domain specificity that distinguishes it from generic API skills, but the lack of concrete actions and the broad 'API Integration' category label could cause overlap with other API-related skills. | 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 placeholder with no real content. It contains only generic boilerplate descriptions of what the skill supposedly does without any actual instructions, code examples, webhook patterns, or actionable guidance. It would provide zero value to Claude when attempting to help a user create a webhook sender.
Suggestions
Add concrete, executable code examples showing how to create a webhook sender (e.g., Python/Node.js HTTP endpoint that sends webhook payloads with retry logic and signature verification).
Define a clear workflow: 1) Configure webhook endpoint URL, 2) Define payload schema, 3) Implement sending logic with retries, 4) Validate delivery with test endpoints, 5) Handle failures and logging.
Remove all generic filler text ('Provides step-by-step guidance', 'Follows industry best practices') and replace with specific patterns like payload signing (HMAC-SHA256), retry strategies (exponential backoff), and content-type headers.
Include a concrete example showing a complete webhook sender implementation with request/response examples and error handling patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no concrete information about webhook senders, and pads with generic phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' without any actual substance. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no concrete steps, no examples of webhook payloads, no API patterns, no configuration snippets. The skill describes what it could do rather than instructing Claude how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely lists vague capabilities without any process for accomplishing webhook sender creation. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no separation of overview from detail. There are no bundle files to reference either, but the content itself lacks any organizational depth. | 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
3a2d27d
- 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.