webhook-signature-validator
Webhook Signature Validator - Auto-activating skill for API Integration. Triggers on: webhook signature validator, webhook signature validator Part of the API Integration skill category.
36
3%
Does it follow best practices?
Impact
100%
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-signature-validator/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 placeholder that repeats the skill name as both the description and trigger terms. It provides no concrete actions, no meaningful trigger terms beyond the title, and no explicit guidance on when Claude should select this skill. It would be nearly useless for skill selection in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Validates webhook signatures using HMAC-SHA256, verifies payload integrity, compares computed hashes against signature headers for providers like Stripe, GitHub, and Slack.'
Add an explicit 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user needs to verify webhook authenticity, validate HMAC signatures, check payload integrity, or implement webhook security for API integrations.'
Include natural keyword variations users would actually say, such as 'verify webhook', 'HMAC signature', 'webhook secret', 'payload hash', 'signature header', and specific provider names.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Webhook Signature Validator') and its category ('API Integration') but does not describe any concrete actions like validating HMAC signatures, verifying payloads, comparing hashes, or handling specific webhook providers. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a duplicate of the skill name rather than meaningful trigger guidance. There is no explicit 'Use when...' clause with real scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('webhook signature validator, webhook signature validator'). It misses natural user terms like 'verify webhook', 'HMAC', 'webhook secret', 'signature verification', 'payload validation', or specific providers like Stripe/GitHub webhooks. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'webhook signature validator' is fairly niche and unlikely to conflict with many other skills, but the lack of specific actions or context means it could overlap with broader API integration or security-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 an empty template with no actual content about webhook signature validation. It contains only generic boilerplate text that provides no actionable guidance, no code examples, and no domain-specific knowledge. It fails on every dimension because it teaches Claude nothing it doesn't already know and provides no concrete instructions for the task.
Suggestions
Add concrete, executable code examples for validating webhook signatures (e.g., HMAC-SHA256 verification in Python/Node.js with specific libraries like `hmac`/`crypto`)
Define a clear workflow: extract signature header → compute expected signature → constant-time comparison → handle valid/invalid cases, with explicit validation checkpoints
Include provider-specific examples (Stripe, GitHub, Slack) showing their signature schemes, header names, and verification patterns
Remove all generic boilerplate ('This skill provides automated assistance...', 'Example Triggers', etc.) and replace with lean, actionable content that assumes Claude's competence
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, contains no domain-specific information about webhook signature validation, and every section is generic template text that could apply to any skill. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no specific algorithms (HMAC-SHA256, etc.), no commands, no library references, no actual instructions for validating webhook signatures. Every bullet is vague and abstract. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Webhook signature validation involves specific steps (extract header, compute HMAC, compare in constant time, handle failures) and none are mentioned. There are no validation checkpoints or error handling guidance. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic placeholder with no meaningful structure. There are no references to supporting files, no layered organization, and no navigation to deeper content. The sections that exist are empty of substance. | 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
3a2d27d
- 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.