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 is somewhat general ('most common Clay errors') rather than listing specific concrete actions or error types it can resolve. The explicit trigger phrases are a notable strength for skill selection.
Suggestions
Add more specific concrete actions, e.g., 'resolve HTTP timeout errors, fix API key authentication failures, repair broken enrichment column mappings, debug webhook payload formatting issues' 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 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 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 |
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 strong actionability — each error has concrete symptoms, causes, and executable fixes. The main weaknesses are its length as a single document (could benefit from grouping/splitting) and the lack of post-fix verification steps. Some entries cover things Claude could figure out on its own (CSV header matching, formula column references), slightly reducing conciseness.
Suggestions
Add a brief verification step after each fix (e.g., 'Verify: re-send a test payload and confirm a new row appears') to improve workflow clarity.
Consider splitting errors into grouped sub-files (e.g., webhook-errors.md, enrichment-errors.md, crm-errors.md) and keeping SKILL.md as a concise index with the summary table.
Remove or compress the simpler errors (#11, #12) that describe concepts Claude already understands — a single line each in the summary table would suffice.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but could be tightened. Some errors (e.g., #11 CSV mapping, #12 formula errors) explain things Claude already knows. The prerequisites section adds little value. However, most entries are direct and avoid excessive preamble. | 2 / 3 |
Actionability | Each error includes a specific symptom, root cause, and concrete fix with executable code examples (curl commands, TypeScript functions) or precise UI navigation steps. The guidance is copy-paste ready and specific enough to act on immediately. | 3 / 3 |
Workflow Clarity | Each error is a standalone fix rather than a multi-step workflow, which is appropriate for a troubleshooting reference. However, Error 6 has a clear sequence with steps, and the overall structure is logical. The skill lacks explicit validation/verification steps after applying fixes (e.g., 'verify the webhook now accepts data' or 'confirm credits are no longer being consumed'), which would strengthen it. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headings and a summary table, but it's a long monolithic document (~180 lines of error entries). Some errors could be grouped or split into separate files (webhook errors, enrichment errors, CRM errors). The reference to 'clay-debug-bundle' in Next Steps is good but the bundle doesn't exist, and the Resources section provides useful external links. | 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
3a2d27d
- 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.