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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

80%

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 error catalog with executable fixes and no concept-explanation fluff. Its weaknesses are the absence of a top-level diagnostic/triage workflow with validation checkpoints and a monolithic inline structure with a dangling bundle reference.

Suggestions

Add a top-level diagnostic decision tree (e.g., 'if webhook symptom → check errors 1/2/5/9; if enrichment symptom → check 3/4/8') with explicit validation checkpoints to raise workflow clarity.

Split the 12-error catalog into a references file (e.g. references/clay-errors.md) and have SKILL.md point to it one level deep, so the main file stays an overview.

Either create the referenced 'clay-debug-bundle' or remove the dangling Next Steps reference, since no references/scripts/assets bundle currently exists.

Dimension	Reasoning	Score
Conciseness	Each error entry is a tight symptom/cause/fix triplet with executable snippets and no padding explaining what Clay is, so every line earns its place.	3 / 3
Actionability	Fixes are concrete and copy-paste ready—curl commands, TypeScript snippets, exact UI paths ('Settings > Plans & Billing'), and specific config instructions—rather than abstract direction.	3 / 3
Workflow Clarity	Per-error entries have a clear symptom→cause→fix sequence, but the skill lacks a global diagnostic triage flow with validation checkpoints; the small Error Handling table is the only routing aid.	2 / 3
Progressive Disclosure	Sections are organized, but the entire 210-line error catalog is inline and the only external reference ('clay-debug-bundle' in Next Steps) does not exist as a bundle file.	2 / 3
	Total	10 / 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.

A strong, third-person description that names concrete capabilities, provides explicit 'Use when' triggers, and lists natural trigger phrases. It cleanly answers both what the skill does and when to invoke it within a distinct Clay niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Diagnose and fix', 'debugging failed enrichments', 'troubleshooting webhook delivery problems') across named Clay subsystems, matching the multiple-specific-actions anchor.	3 / 3
Completeness	Clearly answers both 'what' (diagnose and fix common Clay errors) and 'when' via an explicit 'Use when encountering Clay errors...' clause with concrete triggers.	3 / 3
Trigger Term Quality	Explicit natural trigger phrases ('clay error', 'fix clay', 'clay not working', 'debug clay', 'clay enrichment failed', 'clay webhook error') are exactly what a user would say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to the Clay platform with distinct, Clay-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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: 3022dd3

Reviewed: about 13 hours 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.