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

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/saas-packs/clay-pack/skills/clay-common-errors/SKILL.md

Quality

Content

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid troubleshooting reference with highly actionable fixes including executable code and specific UI paths. Its main weaknesses are the monolithic structure (all 12 errors inline rather than categorized/split) and the lack of a systematic triage workflow to help Claude identify which error applies. Some entries cover trivially simple issues that don't need detailed explanation.

Suggestions

Add a diagnostic triage workflow at the top (e.g., 'If red cell → check Error 6/3/12; if 4xx from webhook → check Error 1/2/5/9') to help Claude quickly identify the relevant error.

Fix the numbering bug in Error 6 (steps go 1, 2, 1 instead of 1, 2, 3).

Consider splitting errors by category (Webhooks, Enrichment, CRM, Formulas) into separate files or at minimum clearly delineated sections, with the SKILL.md serving as a quick-lookup index.

Remove or compress the simpler errors (#11 CSV headers, #12 formula references) to 1-2 lines each since they don't require detailed explanation.

Dimension	Reasoning	Score
Conciseness	The content is generally efficient but could be tightened. Some errors (like #11 CSV mapping, #12 formula errors) explain things Claude would already know. The overview and prerequisites sections add little value. However, most entries are reasonably lean with clear symptom/cause/fix structure.	2 / 3
Actionability	The skill provides concrete, executable code examples (curl commands, TypeScript functions), specific UI navigation paths (e.g., 'Settings > Plans & Billing', 'Table Settings'), and precise fixes for each error. The guidance is copy-paste ready and specific rather than abstract.	3 / 3
Workflow Clarity	Each error follows a clear symptom → cause → fix pattern, which is good. However, there's no overall diagnostic workflow for triaging which error applies, and Error 6's numbered steps have a numbering bug (1, 2, 1 instead of 1, 2, 3). The summary table at the end helps but lacks a systematic debugging sequence.	2 / 3
Progressive Disclosure	The content is a long monolithic list of 12 errors inline with no separation into files by category (webhooks, enrichment, CRM, etc.). The reference to 'clay-debug-bundle' in Next Steps is good but the bundle doesn't exist. The summary table and resources section provide some structure, but the 12 errors could benefit from being split by category with the SKILL.md serving as an index.	2 / 3
	Total	9 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-structured skill description with strong trigger terms and clear 'what/when' guidance. Its main weakness is that the capability description is somewhat general ('diagnose and fix the most common Clay errors') without listing the specific error types or concrete actions beyond enrichments and webhooks. The explicit trigger phrases are a notable strength for skill selection.

Suggestions

Add more specific concrete actions, e.g., 'resolve API rate limits, fix authentication failures, repair broken enrichment formulas, debug webhook payload formatting' to improve specificity.

Dimension	Reasoning	Score
Specificity	It names the domain (Clay) and some actions ('diagnose and fix errors', 'debugging failed enrichments', 'troubleshooting webhook delivery'), but doesn't list multiple specific concrete actions like what fixes it applies or what specific error types it handles beyond enrichments and webhooks.	2 / 3
Completeness	Clearly answers both 'what' (diagnose and fix common Clay errors and integration issues) and 'when' (encountering Clay errors, debugging failed enrichments, troubleshooting webhook delivery) with explicit trigger phrases provided.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would actually say: 'clay error', 'fix clay', 'clay not working', 'debug clay', 'clay enrichment failed', 'clay webhook error'. These are realistic phrases a user would type when encountering issues.	3 / 3
Distinctiveness Conflict Risk	Clay is a specific product/platform, and the description focuses on Clay-specific errors, enrichments, and webhooks. This creates a clear niche that is unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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 — 9 / 11 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	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 00c0702

Reviewed: 4 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.