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

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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, copy-paste-ready TypeScript for both webhook patterns, but it is held back by duplicated logic that should live in the unreferenced bundle files and by missing validation checkpoints for batch/callback operations. Progressive disclosure is undermined because the existing reference files are never signaled from the body.

Suggestions

Link the existing references/implementation.md and references/implementation-guide.md from the body (e.g., in a '## Advanced' section) and move the duplicated signature-verification and event-router code out of SKILL.md into them.

Add an explicit validate→fix→retry feedback loop around sendBatch and async callback processing (verify submission success, retry failures with backoff) to lift workflow clarity above 2.

Resolve the 'Next Steps' pointer to clay-performance-tuning — either link the real skill/file or remove the dangling reference.

DimensionReasoningScore

Conciseness

The body is code-heavy and lean in prose, but at ~240 lines it duplicates signature-verification logic (Step 2) that also appears in both reference files, so it could be tightened by deferring to references rather than fully score 3.

2 / 3

Actionability

Provides fully executable TypeScript (Express handler, fetch POST, crypto HMAC verification, idempotency set) that is copy-paste ready with specific examples, matching the score-3 anchor rather than the pseudocode score-2.

3 / 3

Workflow Clarity

Steps 1–5 are sequenced with an error-handling table, but the batch sendBatch operation and callback processing lack an explicit validate→fix→retry checkpoint; the rubric caps batch operations without validation at 2.

2 / 3

Progressive Disclosure

Two reference files (implementation.md, implementation-guide.md) exist but are never linked or signaled from the body, and content that belongs in them is inline; 'Next Steps' also points to an absent clay-performance-tuning skill, matching the not-clearly-signaled score-2 anchor rather than well-signaled score-3.

2 / 3

Total

9

/

12

Passed

Description

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.

The description is specific, complete, and well-triggered, naming concrete inbound/outbound webhook actions and providing natural trigger phrases. It uses imperative voice consistent with the rubric's score-3 examples (no first/second person), so no voice penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Implement Clay webhook receivers and HTTP API column callbacks for real-time data flow' — matching the multi-action score-3 anchor rather than a single-action score-2.

3 / 3

Completeness

Explicitly answers both what ('Implement Clay webhook receivers and HTTP API column callbacks') and when ('Use when setting up webhook endpoints, handling enrichment callbacks from Clay, or building event-driven integrations'), matching the score-3 anchor; not capped at 2 because an explicit 'Use when' clause is present.

3 / 3

Trigger Term Quality

Provides good natural-term coverage via 'Trigger with phrases like "clay webhook", "clay events", "clay callback", "handle clay data", "clay notifications", "clay HTTP API column"', all terms a user would naturally say.

3 / 3

Distinctiveness Conflict Risk

Targets a clear Clay-specific webhook/callback niche with distinct triggers unlikely to fire for unrelated skills; not generic enough to score 2.

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.