webhook-receiver-generator
Webhook Receiver Generator - Auto-activating skill for API Integration. Triggers on: webhook receiver generator, webhook receiver generator Part of the API Integration skill category.
35
3%
Does it follow best practices?
Impact
91%
1.00xAverage 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-receiver-generator/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 essentially a title and category label with no substantive content. It fails to describe what the skill actually does, provides no natural trigger terms beyond the skill name repeated, and lacks any explicit guidance on when Claude should select it. It would be nearly indistinguishable from other API integration skills in a large skill library.
Suggestions
Add concrete actions the skill performs, e.g., 'Generates webhook receiver endpoints, parses incoming payloads, validates webhook signatures, and handles retry logic.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to receive webhooks, create a webhook endpoint, handle incoming HTTP callbacks, or set up a webhook listener.'
Include common keyword variations users might say: 'webhook handler', 'webhook endpoint', 'receive webhooks', 'HTTP callback', 'webhook listener', 'incoming webhook'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Webhook Receiver Generator') and its category ('API Integration') but does not describe any concrete actions like generating endpoint code, parsing payloads, validating signatures, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a redundant repetition of the skill name rather than meaningful trigger guidance. There is no explicit 'Use when...' clause. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'webhook receiver generator' repeated twice. It misses natural variations users would say like 'webhook endpoint', 'receive webhooks', 'webhook handler', 'listen for webhooks', or 'webhook URL'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'webhook receiver' is somewhat specific and narrows the domain compared to 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 a hollow placeholder with no actual content. It contains no executable code, no concrete instructions, no webhook-specific patterns, and no actionable guidance whatsoever. Every section merely restates that the skill exists for 'webhook receiver generator' without teaching Claude anything about how to actually generate webhook receivers.
Suggestions
Add concrete, executable code examples showing how to create a webhook receiver (e.g., a Flask/Express endpoint that validates signatures, parses payloads, and returns appropriate status codes).
Define a clear multi-step workflow: 1) Set up endpoint, 2) Implement signature verification, 3) Parse and validate payload, 4) Process event, 5) Return response — with validation checkpoints at each step.
Remove all the meta-description sections (Purpose, When to Use, Example Triggers, Capabilities) and replace them with actual technical content covering common webhook patterns like retry handling, idempotency, and secret management.
Add references to supplementary files for advanced topics (e.g., SECURITY.md for signature verification patterns, EXAMPLES.md for provider-specific implementations like Stripe/GitHub/Slack webhooks).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It repeats 'webhook receiver generator' numerous times without providing any actual guidance, code, or technical content. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no commands, no specific steps, no API patterns, no webhook handling logic. The content only describes what the skill claims to do without actually doing any of it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The 'Capabilities' section vaguely mentions 'step-by-step guidance' and 'validates outputs' but provides neither. | 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 contain redundant information rather than progressively deeper 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
4dee593
- 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.