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
Quality
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 severely underdeveloped, essentially just restating the skill name without explaining capabilities or usage triggers. It provides no actionable information for Claude to determine when to select this skill over others. The redundant trigger terms and missing 'Use when...' clause make this description ineffective for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates webhook sender configurations, generates HTTP POST requests to external endpoints, handles authentication headers and payload formatting.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user needs to send data to external services via webhooks, configure outbound HTTP callbacks, or integrate with third-party APIs that accept webhook notifications.'
Include natural keyword variations users might say: 'webhook', 'HTTP callback', 'POST to endpoint', 'notify external service', 'outbound API call', 'webhook payload'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Webhook Sender Creator') and category ('API Integration') without describing any concrete actions. There are no verbs or specific capabilities listed. | 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. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('webhook sender creator, webhook sender creator'). This is redundant and doesn't include natural variations users might say like 'send webhook', 'create webhook endpoint', 'HTTP callback', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'webhook' is somewhat specific terminology, the lack of detail about what this skill actually does (vs other API/webhook-related skills) creates potential overlap. The category 'API Integration' is broad. | 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 a placeholder template with no actual content. It describes what a webhook sender creator skill should do without providing any concrete implementation guidance, code examples, or actionable instructions. The entire content could be replaced with a single sentence: 'This skill helps with webhook senders' - it adds no value beyond that.
Suggestions
Add executable code examples showing how to create a webhook sender (e.g., Python/Node.js HTTP endpoint that sends webhook payloads)
Include concrete configuration examples: payload formats, authentication headers, retry logic, and error handling patterns
Define a clear workflow: 1) Configure endpoint URL, 2) Define payload schema, 3) Implement signing/authentication, 4) Add retry logic, 5) Test with validation
Remove all meta-description text ('This skill provides...', 'Capabilities include...') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no actual technical substance. It explains what the skill does in abstract terms without providing any concrete information Claude doesn't already know. Every section is padded boilerplate. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance whatsoever. The content only describes what the skill theoretically does ('provides step-by-step guidance', 'generates production-ready code') without actually providing any of it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for creating a webhook sender. | 1 / 3 |
Progressive Disclosure | No structure beyond empty section headers. No references to detailed materials, no examples, no navigation to related content. The 'Related Skills' section mentions a category but provides no actual links or references. | 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
0c08951
- 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.