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

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%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.

A well-organized, actionable pitfall catalog with executable code and concrete fixes. Its main weakness is progressive disclosure: the monolithic inline body does not surface the existing reference bundle files.

Suggestions

Link the existing references/implementation.md and references/implementation-guide.md from the body (e.g., a '## Deeper implementation guide' section pointing to them) so the bundle is discoverable and one level deep.

Consider moving the per-pitfall detail into reference files and keeping SKILL.md as a concise overview + the Quick Reference Anti-Pattern Checklist to reduce the inline ~200-line wall of text.

Trim or repurpose the Prerequisites section, which describes user readiness rather than actionable guidance for Claude.

Dimension	Reasoning	Score
Conciseness	The body uses a tight symptom/root-cause/fix template with no padding about what Clay or enrichment libraries are; every section adds domain knowledge Claude would not already have, though the brief Prerequisites list is mildly non-actionable.	3 / 3
Actionability	Fixes include two executable TypeScript blocks, concrete formulas ("ICP Score >= 60 AND ISNOTEMPTY(Company Name)", "ISEMPTY(Work Email)"), specific UI paths ("Settings > Connections"), and numeric thresholds (40K/45K), giving copy-paste-ready guidance.	3 / 3
Workflow Clarity	Each pitfall follows a consistent Symptom/Root cause/Fix diagnostic pattern and a Quick Reference Anti-Pattern Checklist aids lookup; as an advisory reference skill it has no destructive/batch operations that would require validation feedback loops.	3 / 3
Progressive Disclosure	The ~200-line body keeps all ten pitfalls inline, and the existing bundle files (references/implementation-guide.md, references/implementation.md) are never linked from the body, so structure exists but references are not signaled and content that could be split stays inline.	2 / 3
	Total	11 / 12 Passed

Description

90%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.

A strong, well-targeted description that clearly answers both what and when with a rich set of natural trigger phrases. The only weak spot is that the action verbs (identify/avoid) are abstract rather than concrete operations.

Dimension	Reasoning	Score
Specificity	The description names the Clay domain and three target categories ("anti-patterns, gotchas, and integration mistakes"), but the verbs "Identify and avoid" are generic rather than concrete operations like extract/fill/merge, so it stops short of the level-3 anchor.	2 / 3
Completeness	It explicitly states what the skill does ("Identify and avoid the top Clay anti-patterns, gotchas, and integration mistakes") and when to use it ("Use when reviewing Clay integrations for issues, onboarding new team members, or auditing existing Clay table configurations") with explicit trigger phrases.	3 / 3
Trigger Term Quality	It lists five natural phrases a user would actually say ("clay mistakes", "clay anti-patterns", "clay pitfalls", "clay what not to do", "clay gotchas", "clay code review") plus use-when contexts, giving strong keyword coverage.	3 / 3
Distinctiveness Conflict Risk	It carves out a narrow Clay-audit niche with highly specific triggers ("clay pitfalls", "clay code review") that are unlikely to fire for unrelated skills.	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
Path: plugins/saas-packs/clay-pack/skills/clay-known-pitfalls/SKILL.md
Commit: 4c47e33

Reviewed: 2 days 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.