clay-webhooks-events
Implement Clay webhook receivers and HTTP API column callbacks for real-time data flow. Use when setting up webhook endpoints, handling enrichment callbacks from Clay, or building event-driven integrations with Clay tables. Trigger with phrases like "clay webhook", "clay events", "clay callback", "handle clay data", "clay notifications", "clay HTTP API column".
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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-crafted skill description that excels across all dimensions. It provides specific concrete actions, explicit 'Use when' and 'Trigger with' clauses, and is clearly scoped to Clay webhook/callback integrations, making it highly distinguishable from other skills. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Implement Clay webhook receivers', 'HTTP API column callbacks', 'real-time data flow', 'setting up webhook endpoints', 'handling enrichment callbacks', 'building event-driven integrations with Clay tables'. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement webhook receivers and HTTP API column callbacks for real-time data flow) and 'when' (explicit 'Use when' clause with specific scenarios plus a 'Trigger with phrases' section listing exact terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'clay webhook', 'clay events', 'clay callback', 'handle clay data', 'clay notifications', 'clay HTTP API column'. These are terms users would naturally use when needing this specific integration. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche focused specifically on Clay platform webhooks and HTTP API columns. The Clay-specific terminology and integration patterns make it very unlikely to conflict with generic webhook or API skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%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, actionable skill with production-ready code examples covering both Clay webhook patterns comprehensively. The workflow is well-sequenced with important safety measures (signature verification, idempotency, async processing). Main weaknesses are moderate verbosity—the integrations section and some explanatory text could be trimmed or moved to supplementary files.
Suggestions
Move Step 5 (Integration with External Services) to a separate file like `clay-integrations.md` and reference it from the main skill to reduce length.
Trim the prerequisites section—Claude doesn't need to be told about HTTPS or Express.js familiarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary content like the prerequisites section (Claude knows what HTTPS and Express are), the integrations step (Zapier/Slack examples are tangential), and the EnrichedLead interface could be more compact. The error handling table is useful but some entries are obvious. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for both inbound and outbound webhook patterns, complete with signature verification, idempotency handling, and concrete Clay UI configuration steps with specific field mappings. Code is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence covering both webhook directions with explicit validation concerns: signature verification middleware, idempotency handling for retries, immediate 200 response pattern, and an error handling table that maps issues to solutions. The workflow includes feedback loops for duplicate detection. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is quite long (~180 lines of content) with Step 5 (integrations) being tangential material that could be in a separate file. The references to external resources and next steps are good, but the main body could benefit from splitting advanced patterns out. | 2 / 3 |
Total | 10 / 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
c8a915c
- 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.