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.
34
0%
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
0%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 with no substantive content. It repeats the skill name as its own trigger term, provides no concrete actions or capabilities, and lacks any 'Use when...' guidance. It would be nearly impossible for Claude to correctly select this skill from a pool of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates webhook sender configurations, constructs HTTP POST requests with custom payloads, sets up authentication headers, and tests webhook delivery to endpoints.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user wants to send webhooks, create HTTP callbacks, configure outgoing API notifications, or set up POST request integrations.'
Include natural keyword variations users might say, such as 'webhook', 'HTTP callback', 'POST request', 'API notification', 'payload delivery', 'endpoint integration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Webhook Sender Creator') and its category ('API Integration') but provides no concrete actions like 'creates webhook endpoints', 'sends HTTP POST requests', or 'configures payload formats'. It is entirely vague about what the skill actually does. | 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 '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 keywords like 'webhook', 'HTTP callback', 'send payload', 'POST request', 'API endpoint', or 'notification URL' that a user would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'API Integration' is extremely generic and could overlap with dozens of other API-related skills. Without specific actions or distinct triggers, this skill would easily conflict with any other API or webhook-related skill. | 1 / 3 |
Total | 4 / 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 a hollow placeholder that provides no actual value. It contains no executable code, no concrete instructions, no webhook-specific technical content, and no workflow guidance. It merely repeats the phrase 'webhook sender creator' in various contexts without teaching Claude anything it doesn't already know.
Suggestions
Add concrete, executable code examples showing how to create a webhook sender (e.g., Python/Node.js HTTP POST with payload, headers, retry logic, and signature verification).
Define a clear multi-step workflow: 1) Configure endpoint URL, 2) Define payload schema, 3) Implement sending logic with retries, 4) Validate delivery with status code checks and error handling.
Remove all the meta-description sections (Purpose, When to Use, Example Triggers) that explain what the skill is rather than providing actionable instructions—replace with actual technical content.
Include specific examples of webhook payloads, authentication patterns (HMAC signatures, OAuth), and common pitfalls (timeout handling, idempotency keys, retry backoff strategies).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It repeats 'webhook sender creator' numerous times without providing any actual technical guidance, code, or specific instructions. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete, executable guidance—no code, no commands, no specific steps, no examples of webhook payloads, HTTP methods, or configuration. The content only describes what the skill theoretically does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The 'Capabilities' section mentions 'step-by-step guidance' but none is actually provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. There are no references to detailed files, no layered content organization, and the sections are superficial headers over vacuous content. | 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
c8a915c
- 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.