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".
71
88%
Does it follow best practices?
Impact
—
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 platform integrations, making it highly distinguishable from other webhook or API-related skills.
| 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 the 'Clay' platform as a clear niche. The combination of Clay-specific terminology (HTTP API column, enrichment callbacks, Clay tables) makes 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. Its main weakness is length — the integrations section and some inline type definitions could be extracted to keep the core skill leaner. The workflow is well-sequenced with appropriate validation (signature verification, idempotency, async processing pattern) and a useful error handling table.
Suggestions
Extract Step 5 (Integration with External Services) into a separate reference file like INTEGRATIONS.md to reduce the main skill's token footprint.
Remove the Prerequisites section — Claude doesn't need to be told about Express.js familiarity or that HTTPS endpoints must be internet-accessible.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary elements: the `EnrichedLead` interface is defined inline when Claude could infer it, the integrations section (Step 5) with Zapier/Slack examples adds bulk without being core to the webhook skill, and the prerequisites section states obvious things like 'Familiarity with Express.js'. However, the code examples are generally purposeful. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code for both inbound and outbound webhook patterns, complete with imports, class definitions, and usage examples. The Clay UI configuration steps (Step 3) are specific with exact field names and JSON body templates. Code is copy-paste ready. | 3 / 3 |
Workflow Clarity | The five steps are clearly sequenced from inbound to outbound to configuration to idempotency to integrations. Validation is addressed through signature verification middleware, idempotency handling for retries, and the error handling table provides explicit feedback loops for common failure modes. The 'respond 200 immediately, process async' pattern is a critical checkpoint that's explicitly called out. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's quite long (~180 lines of content) and could benefit from splitting the integration examples and detailed code into separate files. The reference to `clay-performance-tuning` in Next Steps is good, but there are no bundle files to support progressive disclosure. Step 5 (integrations) feels like it belongs in a separate reference file. | 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
09b10d6
- 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.