webhook-sender-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill webhook-sender-creatorWebhook Sender Creator - Auto-activating skill for API Integration. Triggers on: webhook sender creator, webhook sender creator Part of the API Integration skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, consisting mainly of the skill name and category without any substantive content. It lacks concrete actions, meaningful trigger terms (the same phrase is duplicated), and provides no guidance on when to use the skill. This would be nearly useless for Claude to distinguish from other API-related skills.
Suggestions
Add specific actions the skill performs, e.g., 'Creates webhook senders that POST JSON payloads to specified URLs, configure headers, handle authentication, and manage retry logic.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user wants to send webhooks, create HTTP callbacks, notify external services, or POST data to APIs.'
Remove the duplicate trigger term and expand with variations users might say: 'webhook', 'HTTP POST', 'callback URL', 'notify endpoint', 'send to API'.
| 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 specific capabilities listed like 'create webhooks', 'configure endpoints', or 'send HTTP requests'. | 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. Both what and when are essentially missing. | 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 misses natural user phrases like 'send webhook', 'HTTP callback', 'notify endpoint', or 'POST to URL'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'webhook' is somewhat specific terminology that wouldn't conflict with most skills, the vague 'API Integration' category and lack of specific triggers could cause overlap with other API-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It describes what a webhook sender creator skill should do but provides zero concrete implementation guidance, code examples, or actionable steps. Claude already knows what webhooks are - this skill adds nothing useful.
Suggestions
Add executable code examples showing how to create a webhook sender (e.g., Python requests library with proper headers, payload structure, and error handling)
Include a clear workflow: 1) Configure endpoint URL, 2) Define payload schema, 3) Implement authentication, 4) Add retry logic with exponential backoff, 5) Validate delivery
Provide concrete examples of webhook payloads for common use cases (e.g., Stripe-style events, GitHub webhooks)
Remove all generic filler text ('provides automated assistance', 'follows best practices') and replace with specific, actionable content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler text that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless without specifics. The entire skill could be replaced with actual webhook sender implementation code. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific examples of webhook payloads, endpoints, or implementation patterns. The content only describes what the skill claims to do rather than actually instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. Creating a webhook sender involves multiple steps (endpoint configuration, payload formatting, authentication, retry logic, error handling) but none are mentioned or sequenced. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague marketing-style text with no structure for actual learning. No references to detailed documentation, examples, or related files are provided despite mentioning 'Related Skills'. | 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.