clay-common-errors
Diagnose and fix Clay common errors and exceptions. Use when encountering Clay errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "clay error", "fix clay", "clay not working", "debug clay".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-common-errors79
Quality
73%
Does it follow best practices?
Impact
91%
1.51xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/clay-pack/skills/clay-common-errors/SKILL.mdDiscovery
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 solid skill description with excellent trigger term coverage and completeness. The explicit 'Use when...' and 'Trigger with phrases like...' clauses make it highly actionable for skill selection. The main weakness is that the capabilities could be more specific about what concrete debugging actions the skill performs.
Suggestions
Add 2-3 specific concrete actions like 'parse Clay error logs', 'validate API authentication', or 'check webhook configurations' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clay errors/exceptions) and some actions (diagnose, fix, debug, troubleshoot), but doesn't list specific concrete actions like 'parse error logs', 'validate API responses', or 'check authentication tokens'. | 2 / 3 |
Completeness | Clearly answers both what (diagnose and fix Clay errors and exceptions) and when (explicit 'Use when...' clause with triggers, plus 'Trigger with phrases like...' providing additional explicit guidance). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'clay error', 'fix clay', 'clay not working', 'debug clay', plus 'failed requests' and 'integration issues'. Good coverage of common user phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to 'Clay' platform errors with distinct trigger terms. Unlikely to conflict with generic debugging skills due to the specific product name and error-focused scope. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has decent structure and progressive disclosure but underdelivers on its promise of covering 'top 10 most common errors' while only documenting 3. The boilerplate sections (Overview, Prerequisites, generic Instructions) consume tokens without adding value, and the actual error solutions lack verification steps to confirm fixes worked.
Suggestions
Remove the generic Instructions steps 1-3 and Output section - they describe obvious actions Claude already knows
Either document all 10 promised errors or change the title to accurately reflect the 3 errors covered
Add verification commands after each solution (e.g., 'Verify fix: curl -H "Authorization: Bearer $CLAY_API_KEY" https://api.clay.com/health')
Inline the rate limit solution with actual exponential backoff code instead of deferring to another skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary scaffolding (Overview, Prerequisites, Instructions steps 1-3, Output section) that adds little value. The actual error solutions are reasonably concise, but the framing could be tightened significantly. | 2 / 3 |
Actionability | Provides some executable commands (curl, env checks, TypeScript config), but only covers 3 errors despite claiming 'top 10'. The rate limit solution defers to another skill rather than providing inline guidance. Missing concrete code for several error types. | 2 / 3 |
Workflow Clarity | The escalation path provides a reasonable sequence, but the main 'Instructions' steps are generic and unhelpful. No validation checkpoints to confirm fixes worked. The 'Verified resolution' output is mentioned but no verification steps are provided. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections and appropriate references to external resources (clay-rate-limits skill, clay-debug-bundle, external docs). References are one level deep and well-signaled. | 3 / 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 | |
- 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.