clay-common-errors
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-common-errorsDiagnose 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".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
57%This skill has good structure and appropriate references to external resources, but suffers from incomplete content (claims 'top 10 errors' but only documents 3) and unnecessary boilerplate sections. The actual error solutions are too shallow - they identify problems but don't always provide complete fixes.
Suggestions
Remove the generic Instructions steps 1-3 and Output section - they add no value and waste tokens
Either document all 10 claimed errors or change the title to match actual content (3 errors)
Add verification commands after each solution to confirm the fix worked (e.g., 'Test with: curl -H "Authorization: Bearer $CLAY_API_KEY" https://api.clay.com/v1/test')
Complete the authentication solution - show how to regenerate or set a new API key, not just how to check if one exists
| 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, bash, typescript), but only covers 3 errors despite claiming 'top 10'. Solutions are incomplete - rate limiting just defers to another skill, and authentication fix only shows how to check the key, not how to fix it. | 2 / 3 |
Workflow Clarity | The escalation path provides a reasonable sequence, but the main 'Instructions' steps are generic and unhelpful. No validation steps to confirm fixes worked beyond vague 'Verified resolution' in Output section. | 2 / 3 |
Progressive Disclosure | Appropriately references external resources (clay-rate-limits skill, clay-debug-bundle, external docs) with clear one-level-deep navigation. Content is well-organized with clear section headers. | 3 / 3 |
Total | 9 / 12 Passed |
Activation
90%This is a well-structured skill description with excellent trigger term coverage and clear 'Use when' guidance. The main weakness is the lack of specific concrete actions - it describes general debugging activities rather than listing specific capabilities like parsing particular error types or checking specific Clay configurations.
Suggestions
Add 2-3 specific concrete actions such as 'parse Clay API error codes', 'validate webhook configurations', or 'diagnose rate limiting issues' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clay errors/exceptions) and general actions (diagnose, fix, debug, troubleshoot), but doesn't list specific concrete actions like 'parse error codes', 'validate API responses', or 'check authentication tokens'. | 2 / 3 |
Completeness | Clearly answers both what (diagnose and fix Clay common errors and exceptions) and when (explicit 'Use when...' clause with scenarios plus 'Trigger with phrases like...' providing concrete examples). | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural terms users would say: 'clay error', 'fix clay', 'clay not working', 'debug clay', plus 'debugging failed requests' and 'troubleshooting integration issues' - these match how users naturally describe problems. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to Clay platform errors with distinct triggers; unlikely to conflict with general debugging skills or other integration tools due to the explicit 'Clay' keyword throughout. | 3 / 3 |
Total | 11 / 12 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.