clay-common-errors

Diagnose and fix the most common Clay errors and integration issues. Use when encountering Clay errors, debugging failed enrichments, or troubleshooting webhook delivery problems. Trigger with phrases like "clay error", "fix clay", "clay not working", "debug clay", "clay enrichment failed", "clay webhook error".

Quality

85%

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

80%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 content is a lean, actionable error catalog with executable code and precise UI navigation. Its gaps are workflow validation for batch operations and progressive disclosure: the entire reference is inline and its one external pointer (clay-debug-bundle) is a dead link.

Suggestions

Add a validation/verification step to batch operations (e.g., after webhook submissions or CRM sync, confirm row counts or check for duplicates) and fix the restarted numbering in Error 6's step list.

Either create the referenced clay-debug-bundle file or remove the dead 'Next Steps' pointer so the only external reference is real.

Consider moving the per-error detail (or the code-heavy entries like the throttle and validation scripts) into a references/ file, keeping SKILL.md as an overview with one-level-deep links to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body uses a tight symptom/cause/fix format with no preamble explaining what Clay, webhooks, or enrichment are, assuming Claude's competence and earning every token like the score-3 anchor; it avoids the verbose concept-explanation of score 1 and the padded commentary of score 2.	3 / 3
Actionability	Entries provide fully executable curl commands and TypeScript functions (isEnrichable, sendWithThrottle) plus exact UI paths like '+ Add > Webhooks > Monitor webhook' and 'Settings > Plans & Billing', matching the score-3 copy-paste-ready anchor; it is above 2 because the code is real and complete, not pseudocode.	3 / 3
Workflow Clarity	The Error Handling table gives a triage sequence and Error 6 lists steps, but batch/destructive operations (webhook submissions, CRM sync) lack validation checkpoints and Error 6's numbered list restarts at 1, so it is capped at 2 per the batch-operations guideline rather than reaching the explicit-validation score 3.	2 / 3
Progressive Disclosure	The 234-line reference is a monolithic inline block that could be split, and the 'Next Steps' pointer to clay-debug-bundle references a bundle that does not exist on disk, matching the score-2 anchor of structure present but references not clearly signaled and content that should be separate kept inline; it is not the deeply-nested dead-ends of score 1 nor the cleanly split one-level-deep references of score 3.	2 / 3
	Total	10 / 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.

The description is strong: it states a clear what and an explicit when, with a rich set of natural trigger phrases and a distinct Clay niche. Its only weakness is that the capability verbs ('diagnose and fix') are generic rather than enumerating concrete operations.

Dimension	Reasoning	Score
Specificity	Quotes 'Diagnose and fix the most common Clay errors and integration issues' name the Clay domain and two actions (diagnose, fix), but do not enumerate multiple distinct concrete actions like the score-3 anchor; it is comprehensive in scope yet generic in verbs, so it sits at 2 rather than 1 (which would be vague/abstract) or 3 (which would list several specific operations).	2 / 3
Completeness	It explicitly states what ('Diagnose and fix the most common Clay errors and integration issues') and when ('Use when encountering Clay errors, debugging failed enrichments, or troubleshooting webhook delivery problems'), satisfying both halves like the score-3 anchor; it is above 2 because the 'when' is explicit rather than implied.	3 / 3
Trigger Term Quality	Quotes 'clay error', 'fix clay', 'clay not working', 'debug clay', 'clay enrichment failed', 'clay webhook error' are natural phrases a user would actually say when needing this skill, giving good coverage matching the score-3 anchor; it is not jargon-only (score 1) nor missing common variations (score 2).	3 / 3
Distinctiveness Conflict Risk	The Clay-specific niche and Clay-prefixed trigger phrases ('clay webhook error', 'clay enrichment failed') make it unlikely to fire for an unrelated skill, matching the score-3 anchor; it is not generic enough to risk conflict (score 1) or only somewhat specific (score 2).	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-common-errors/SKILL.md
Commit: 0540a62

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.