clay-webhooks-events
Implement Clay webhook signature validation and event handling. Use when setting up webhook endpoints, implementing signature verification, or handling Clay event notifications securely. Trigger with phrases like "clay webhook", "clay events", "clay webhook signature", "handle clay events", "clay notifications".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-webhooks-events81
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%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 is a well-structured skill description with explicit trigger guidance and clear 'Use when' clauses. The main weakness is that the specific capabilities could be more detailed - it mentions validation and event handling but doesn't enumerate specific actions like parsing payloads, verifying HMAC signatures, or handling specific event types.
Suggestions
Add more specific concrete actions such as 'verify HMAC signatures', 'parse webhook payloads', 'handle specific event types like record updates or enrichment completions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clay webhooks) and some actions (signature validation, event handling, signature verification), but lacks comprehensive concrete actions like specific verification methods, payload parsing, or error handling details. | 2 / 3 |
Completeness | Clearly answers both what (implement webhook signature validation and event handling) and when (setting up webhook endpoints, implementing signature verification, handling Clay event notifications) with explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'clay webhook', 'clay events', 'clay webhook signature', 'handle clay events', 'clay notifications'. Good coverage of variations users might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to Clay platform webhooks with distinct triggers. The 'Clay' prefix on all trigger terms makes it unlikely to conflict with generic webhook skills or other platform-specific webhook handlers. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid webhook implementation skill with excellent actionable code examples covering signature verification, event handling, and idempotency. The main weaknesses are some unnecessary explanatory content (Prerequisites, Output sections) and missing explicit validation checkpoints in the workflow for this security-critical operation.
Suggestions
Remove the Prerequisites section - Claude already understands HTTPS, cryptographic signatures, and Redis concepts
Add explicit validation checkpoint in workflow: 'Step 2.5: Test signature verification with a known-good payload before proceeding'
Consolidate the Output section into the workflow steps or remove it entirely as it restates what the code already demonstrates
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some unnecessary sections like the Prerequisites list (Claude knows what HTTPS and cryptographic signatures are) and the verbose Output section that restates what was already shown. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for Express.js webhook setup, signature verification with timing-safe comparison, event handling patterns, and Redis-based idempotency. All code is copy-paste ready with proper imports. | 3 / 3 |
Workflow Clarity | Steps are listed in the Instructions section but lack explicit validation checkpoints. For a security-critical operation like webhook handling, there should be explicit verification steps (e.g., 'test signature validation before deploying') rather than just sequential instructions. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from setup to verification to handling to testing. References to external resources and related skills are clearly signaled at the end without deep nesting. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 12 / 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.