clay-advanced-troubleshooting
Deep-debug complex Clay enrichment failures, provider degradation, and data flow issues. Use when standard troubleshooting fails, investigating intermittent enrichment failures, or preparing detailed evidence for Clay support escalation. Trigger with phrases like "clay hard bug", "clay mystery error", "clay impossible to debug", "difficult clay issue", "clay deep debug".
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-advanced-troubleshooting/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-crafted description that clearly defines its niche as an advanced debugging skill for Clay enrichment issues. It excels at completeness and distinctiveness by explicitly stating when to use it (when standard troubleshooting fails) and providing natural trigger phrases. The main weakness is that the specific capabilities could be more concrete—listing particular debugging actions rather than broad categories like 'data flow issues.'
Suggestions
Add more concrete actions to improve specificity, e.g., 'Traces waterfall execution logs, analyzes provider API response patterns, identifies rate-limiting and timeout root causes, and compiles diagnostic evidence for Clay support tickets.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clay enrichment) and some actions (debug enrichment failures, provider degradation, data flow issues, support escalation), but doesn't list multiple concrete step-by-step actions like 'analyze waterfall logs, trace API call chains, compare provider response schemas.' | 2 / 3 |
Completeness | Clearly answers both 'what' (deep-debug complex Clay enrichment failures, provider degradation, data flow issues) and 'when' (when standard troubleshooting fails, investigating intermittent enrichment failures, preparing evidence for support escalation), with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases users would naturally say ('clay hard bug', 'clay mystery error', 'clay deep debug', 'difficult clay issue') plus natural keywords like 'enrichment failures', 'provider degradation', and 'support escalation'. Good coverage of how users would describe the situation. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche: specifically targets *deep/complex* Clay debugging scenarios that go beyond standard troubleshooting. The explicit trigger phrases and the escalation-level framing make it highly distinct from a general Clay troubleshooting skill. | 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 advanced troubleshooting skill with genuinely useful executable code and structured diagnostic patterns. Its main weaknesses are the length (some content could be split into reference files) and the lack of explicit validation/feedback loops between debugging steps. The actionability is strong with real scripts and templates, but the workflow could better guide Claude through conditional branching based on findings.
Suggestions
Add explicit decision points between steps, e.g., 'If Layer 1 fails → focus on webhook config (skip to Step 5 for escalation). If Layer 2 fails → check API key and proceed to Step 2.'
Split the detailed error pattern YAML blocks and the support escalation template into separate reference files (e.g., ENRICHMENT_ERRORS.md, ESCALATION_TEMPLATE.md) and link from the main skill.
Add a verification step after applying fixes: 'After applying the fix, re-run the failing rows and confirm the error is resolved before proceeding.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary verbosity. The prerequisites section explains things Claude would know, and some YAML blocks are more explanatory than needed (e.g., explaining what 'No data found' means). The support escalation template is useful but lengthy. | 2 / 3 |
Actionability | Provides fully executable bash scripts, TypeScript code, and concrete YAML-structured diagnostic patterns. The layer isolation test script is copy-paste ready, the HTTP API column debugger is executable TypeScript, and the support escalation template is immediately usable. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-5) with a logical progression from isolation to escalation. However, there are no explicit validation checkpoints or feedback loops between steps — for instance, no 'if Step 1 identifies Layer X, skip to Step Y' guidance, and no verification that fixes actually resolved the issue before moving on. | 2 / 3 |
Progressive Disclosure | Content is organized into clear sections with a logical flow, and references clay-load-scale for next steps. However, the skill is quite long (~200 lines of substantive content) and could benefit from splitting detailed diagnostic patterns (YAML blocks) and the support template into separate reference files rather than inlining everything. | 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
70e9fa4
- 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.