CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable code and exact UI steps, but leans on redundancy and inlines material that overlaps with unreferenced bundle files. Workflow sequencing is clear but lacks explicit validation feedback loops for batch/retry operations.

Suggestions

Link the reference files (implementation-guide.md, implementation.md) from the body instead of duplicating their signature-verification and idempotency code inline, reducing redundancy and improving progressive disclosure.

Add an explicit validate-then-proceed checkpoint to the inbound sendBatch and outbound callback workflows (e.g., verify response status, retry or log on failure before continuing).

Fix or remove the dangling "Next Steps" pointer to clay-performance-tuning, which is not an available file.

DimensionReasoningScore

Conciseness

The body is mostly code-driven and assumes competence, but contains redundancy — signature verification and idempotency logic appear both inline and again in the reference files, and Step 4's processEnrichedLead duplicates Step 2's routing logic.

2 / 3

Actionability

Provides fully executable TypeScript handlers, exact Clay UI steps ("+ Add Column > HTTP API", mapped JSON body), and copy-paste-ready fetch/Express code with concrete env-var usage.

3 / 3

Workflow Clarity

A clear five-step sequence exists with some checkpoints (signature verification, idempotency), but batch operations like sendBatch and the retry-prone HTTP API column lack an explicit validate-then-proceed or fix-and-retry feedback loop, capping clarity at 2.

2 / 3

Progressive Disclosure

The body is organized into clear sections and bundle files exist in references/, but neither reference file is linked or signaled from the body, and the "Next Steps" pointer to clay-performance-tuning is not a present file; detailed handler code that could live in references is inlined.

2 / 3

Total

9

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-crafted: it lists concrete actions, includes natural trigger phrases, answers both what and when explicitly, and occupies a distinct Clay-specific niche. It uses third-person voice throughout with no fluff.

DimensionReasoningScore

Specificity

"Implement Clay webhook receivers and HTTP API column callbacks for real-time data flow" names multiple concrete actions (webhook receivers, HTTP API column callbacks, real-time data flow) rather than vague language.

3 / 3

Completeness

It explicitly states what ("Implement Clay webhook receivers and HTTP API column callbacks") and when ("Use when setting up webhook endpoints, handling enrichment callbacks... or building event-driven integrations"), with explicit trigger guidance.

3 / 3

Trigger Term Quality

Trigger phrases like "clay webhook", "clay events", "clay callback", "clay notifications", and "clay HTTP API column" are natural terms a user setting up Clay integrations would actually say, with good coverage.

3 / 3

Distinctiveness Conflict Risk

The Clay-specific niche and branded trigger terms ("clay webhook", "clay HTTP API column") make it clearly distinguishable and unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.