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".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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.mdQuality
Discovery
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 could be more specific about the concrete actions performed (e.g., listing specific error types or fix strategies). Overall, it would perform well in a multi-skill selection scenario due to its distinct product focus and explicit trigger phrases.
Suggestions
Add more specific concrete actions beyond 'diagnose and fix' — e.g., 'resolve API rate limits, fix authentication failures, repair broken enrichment columns, debug webhook payload formatting'.
| 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 are applied or what specific error types are handled 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 an explicit 'Use when' clause and trigger phrases. | 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 | Very distinct niche — Clay is a specific product, and the description focuses on Clay-specific errors, enrichments, and webhooks. Unlikely to conflict with other skills due to the product-specific terminology. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
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, specific fixes for each error. Its main weaknesses are length (could benefit from splitting into sub-files by category) and the lack of explicit verification steps after applying fixes. The content is practical and well-structured but could be more token-efficient by trimming some entries and leveraging progressive disclosure.
Suggestions
Split the 12 errors into category-specific files (e.g., clay-webhook-errors.md, clay-enrichment-errors.md) and make SKILL.md a concise index with the summary table pointing to each file.
Add a brief verification step to each fix (e.g., 'Confirm fix: re-send a test payload and verify a new row appears') — especially for webhook and CRM sync errors.
Trim the Error 3 TypeScript example to just the domain check logic, and remove the summary table's 'Quick Check' column which largely duplicates the per-error symptom descriptions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-structured and avoids explaining what Clay is, but some entries could be tighter. For instance, Error 3's TypeScript validation function is longer than needed, and some fixes include obvious context (e.g., explaining what a 404 is). The summary table at the end partially duplicates information already covered. | 2 / 3 |
Actionability | Each error includes exact symptoms, root causes, and concrete fixes with executable code (curl commands, TypeScript functions). The guidance is specific and copy-paste ready — e.g., the webhook curl command, the rate-limiting throttle function, and the JSON validation one-liner. | 3 / 3 |
Workflow Clarity | Error 6 has a clear multi-step debugging sequence, but most errors are single-step fixes without validation checkpoints. For destructive/batch operations like Error 9 (rate-limited webhook submissions) and Error 5 (webhook limit), there are no explicit verification steps to confirm the fix worked. The overall structure is a flat list rather than a guided diagnostic workflow. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear headers and a summary table, but at ~180 lines it's quite long for a single SKILL.md. The 12 errors could be split into category-specific files (webhooks, enrichments, CRM) with the SKILL.md serving as an index. The 'Next Steps' reference to clay-debug-bundle is good but the main content is monolithic. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%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 | |
- Commit
3e83543
- Reviewed
Table of Contents
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.