webhook-receiver-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill webhook-receiver-generatorWebhook Receiver Generator - Auto-activating skill for API Integration. Triggers on: webhook receiver generator, webhook receiver generator Part of the API Integration skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It repeats the skill name as trigger terms, lacks any concrete capability descriptions, and provides no guidance on when Claude should select this skill. The description would be indistinguishable from dozens of potential API-related skills.
Suggestions
Add specific capabilities: describe what the generator creates (e.g., 'Generates webhook receiver endpoints with authentication, payload validation, and event routing')
Include a 'Use when...' clause with natural trigger scenarios (e.g., 'Use when user needs to receive webhooks, create callback URLs, handle incoming API events, or set up event listeners')
Add natural keyword variations users might say: 'webhook', 'callback URL', 'receive events', 'incoming API calls', 'event listener', 'HTTP callback'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Webhook Receiver Generator') without describing any concrete actions. There are no specific capabilities listed like 'creates endpoints', 'handles authentication', or 'parses payloads'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than describing usage scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundantly listed as 'webhook receiver generator' twice, which is technical jargon. Missing natural user phrases like 'create webhook', 'receive webhooks', 'webhook endpoint', 'listen for events', or 'API callback'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'webhook receiver' is somewhat specific, the vague 'API Integration' category and lack of concrete details could cause overlap with other API-related skills. The term 'generator' provides some distinction but is not well-defined. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder with no substantive information about webhook receivers. It contains only meta-descriptions of what the skill claims to do without any actual implementation guidance, code examples, or concrete instructions. The content would be completely unhelpful for generating webhook receivers.
Suggestions
Add executable code examples showing how to create webhook receivers in at least one language (e.g., Express.js endpoint, Flask route, or similar)
Include a concrete workflow: 1) Define endpoint, 2) Validate incoming payload signature, 3) Parse webhook data, 4) Return appropriate status codes, 5) Handle retries
Provide specific guidance on webhook security (signature verification, HTTPS requirements, IP whitelisting) with actual implementation code
Add example webhook payloads and expected response formats for common providers (Stripe, GitHub, Slack, etc.)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual webhook-specific information. | 1 / 3 |
Actionability | Contains zero concrete guidance - no code examples, no specific commands, no actual webhook receiver implementation details. The entire content describes what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, no sequence, and no validation checkpoints for webhook receiver implementation. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure pointing to detailed materials, no references to implementation guides, and no organized navigation to actual webhook receiver documentation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.