CtrlK
BlogDocsLog inGet started
Tessl Logo

clay-hello-world

Send your first record to Clay and get enriched data back. Use when starting a new Clay integration, testing webhook setup, or verifying that enrichment columns are working. Trigger with phrases like "clay hello world", "clay example", "clay quick start", "first clay enrichment", "test clay webhook".

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

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 copy-paste code and a useful error table, but it trades some conciseness for redundant language variants and omits explicit validation checkpoints in the batch workflow. Organization is clean yet inline-only, missing a progressive file split.

Suggestions

Add an explicit validation step after sending (e.g., poll the row or check the webhook response) before relying on enrichment, especially for the batch loop.

Consolidate the Node.js and Python examples or move one to a reference file to remove the duplicated webhook POST and improve token efficiency.

Consider splitting the per-language code samples into a references/ bundle so the main SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient with executable code and a tight error table, but the Node.js and Python examples duplicate the same webhook POST and could be tightened; not every token earns its place.

2 / 3

Actionability

Provides fully executable curl, Node, and Python snippets with concrete webhook URLs plus a cause/solution error table — copy-paste ready and specific.

3 / 3

Workflow Clarity

Steps are clearly sequenced, but the batch send loop and the send→enrich→retrieve flow lack an explicit validation checkpoint (e.g., verifying the row was created), which caps workflow clarity at 2 for batch operations.

2 / 3

Progressive Disclosure

Well-organized single-file sections with no nested references, but the body (~135 lines, two languages) keeps content inline that could be split out, and References point to external URLs rather than bundle files.

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: it states concrete Clay webhook/enrichment actions, gives explicit 'Use when' guidance, and lists natural trigger phrases. It cleanly hits the top anchor on every dimension with no fluff or over-claims.

DimensionReasoningScore

Specificity

Names the Clay domain and multiple concrete actions ('Send your first record to Clay and get enriched data back', 'testing webhook setup', 'verifying that enrichment columns are working'), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers what ('Send your first record to Clay and get enriched data back') and when via an explicit 'Use when starting a new Clay integration...' clause, hitting the top anchor.

3 / 3

Trigger Term Quality

Explicit 'Trigger with phrases like "clay hello world", "clay example", "clay quick start", "first clay enrichment", "test clay webhook"' gives good coverage of natural terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

A clear niche (Clay hello-world / first-enrichment onboarding) with distinct Clay-specific triggers makes it unlikely to fire for an unrelated skill.

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.