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 lacks concrete actions, meaningful trigger terms, and any explicit guidance on when Claude should use it. It reads as auto-generated boilerplate rather than a useful skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates webhook receiver endpoints, validates incoming payloads, handles signature verification, and sets up event routing logic.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks to create a webhook endpoint, set up a webhook listener, handle incoming webhook events, or build a webhook handler.'
Remove the duplicated trigger term and instead include varied natural language phrases users might say, such as 'webhook handler', 'receive webhook', 'webhook endpoint', 'listen for webhooks'.
| 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 trigger phrase rather than meaningful guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'webhook receiver generator' repeated twice. It misses natural user phrases like 'create a webhook endpoint', 'listen for webhooks', 'handle incoming webhooks', 'webhook handler', or 'receive webhook events'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'webhook receiver' is somewhat specific and unlikely to conflict with many other skills, but the lack of detail about what it actually generates (e.g., language, framework, scope) means it could overlap with general API or code generation 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 that provides no actual instruction on generating webhook receivers. It contains only meta-descriptions of what the skill would do, repeated references to 'webhook receiver generator' as a phrase, and zero actionable content. It fails on every dimension of the rubric.
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 meta-description sections (Purpose, When to Use, Example Triggers, Capabilities) and replace with actual technical content: supported frameworks, security patterns (HMAC verification), retry handling, and idempotency.
Add references to supplementary files for advanced topics like queue-based processing, specific provider integrations (Stripe, GitHub, etc.), and testing/debugging webhooks locally.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It repeatedly restates 'webhook receiver generator' without providing any actual guidance, code, or technical content. Every section describes the skill abstractly rather than teaching anything. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no commands, no specific steps for creating a webhook receiver. The content only describes what the skill theoretically does without actually doing 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' but none is actually provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive structure with no meaningful organization. There are no references to detailed files, no quick-start section, and no navigation to deeper content. The sections are boilerplate headers with no real content beneath them. | 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
b8a3b3e
- 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.