clay-known-pitfalls

Identify and avoid the top Clay anti-patterns, gotchas, and integration mistakes. Use when reviewing Clay integrations for issues, onboarding new team members, or auditing existing Clay table configurations. Trigger with phrases like "clay mistakes", "clay anti-patterns", "clay pitfalls", "clay what not to do", "clay gotchas", "clay code review".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

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 content is highly actionable with concrete code, formulas, and exact thresholds, but it reads as a long inline catalog rather than an overview pointing to its own bundle files, and it lacks a sequenced audit workflow with verification checkpoints. A contradiction between the body and a reference file further weakens navigation.

Suggestions

Move detailed inline code examples (e.g., the TypeScript filter and CSV normalization snippets) into the existing references/ files and link to them from SKILL.md to reduce inline token load and improve conciseness.

Surface the bundle files in the body and reconcile the contradiction: references/implementation-guide.md lowercases CSV headers while Pitfall 5 explicitly warns against changing case — pick one guidance and align both files.

Add a sequenced audit workflow with verification checkpoints (e.g., 1. Check webhook submission count, 2. Verify waterfall 'stop on first result', 3. Confirm own API keys, 4. Validate conditional run rules) so reviewers can systematically validate a Clay configuration instead of browsing isolated pitfalls.

Dimension	Reasoning	Score
Conciseness	Per-pitfall sections are lean, but the full 10-pitfall catalog plus a partially redundant Quick Reference table and meta-prose ('learned from production experience', 'Each pitfall includes the exact symptom, root cause, and fix') could be tightened by offloading detail to the existing reference files.	2 / 3
Actionability	Provides executable TypeScript (filterBeforeEnrichment, normalizeCSVHeaders), concrete Clay formula conditions ('ICP Score >= 60 AND ISNOTEMPTY(Company Name)'), exact thresholds (50K/45K/40K), and specific UI paths (Settings > Connections) — copy-paste ready.	3 / 3
Workflow Clarity	Pitfalls are consistently structured as symptom/root cause/fix, but presented as an isolated catalog with no sequenced audit workflow or validation checkpoints for the overall review task; several pitfalls involve batch/credit operations that lack verification steps, capping this at 2.	2 / 3
Progressive Disclosure	The body is well-sectioned but never links the two existing bundle files in references/, and detailed code that could live in references is inline; additionally references/implementation-guide.md's CSV header advice (lowercasing) directly contradicts Pitfall 5.	2 / 3
	Total	9 / 12 Passed

Description

90%

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 clearly answers what the skill does and when to use it, with a strong set of natural Clay-specific trigger phrases and a distinct niche. The only weakness is specificity: the actions are limited to 'identify and avoid' rather than a richer set of concrete operations.

Dimension	Reasoning	Score
Specificity	Names the Clay domain and the actions 'identify' and 'avoid' ('Identify and avoid the top Clay anti-patterns, gotchas, and integration mistakes'), but lists only two verbs rather than multiple distinct concrete actions, falling short of the level-3 anchor.	2 / 3
Completeness	Explicitly states both what the skill does and when to use it via an explicit 'Use when reviewing Clay integrations...' clause plus trigger phrases, satisfying both the what and the when.	3 / 3
Trigger Term Quality	Provides six natural trigger phrases a user would plausibly say ('clay mistakes', 'clay anti-patterns', 'clay pitfalls', 'clay what not to do', 'clay gotchas', 'clay code review'), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to Clay with Clay-specific trigger phrases, making it unlikely to fire for unrelated skills and clearly occupying a distinct niche.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.