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 skill description that clearly defines its niche as an advanced debugging tool for Clay enrichment issues. It effectively communicates both what it does and when to use it, with explicit trigger phrases that reduce ambiguity. The main weakness is that the specific capabilities could be more concrete — listing particular debugging actions or outputs rather than general categories of issues.
Suggestions
Add more concrete actions to improve specificity, e.g., 'Traces enrichment data flows across columns, analyzes provider API response patterns, correlates failure timing with rate limits, and generates structured evidence reports for Clay support.'
| 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 actions like specific debugging steps or outputs. | 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 natural trigger phrases users would actually say ('clay hard bug', 'clay mystery error', 'clay deep debug', 'difficult clay issue') plus domain-specific terms like 'enrichment failures', 'provider degradation', and 'support escalation'. Good coverage of natural language variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — specifically targets deep/complex Clay debugging scenarios that go beyond standard troubleshooting. The explicit trigger phrases and the 'when standard troubleshooting fails' qualifier clearly distinguish it 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, actionable troubleshooting skill with excellent concrete examples including executable scripts and structured diagnostic patterns. Its main weaknesses are the monolithic structure (everything inline rather than split across files) and the lack of explicit validation checkpoints between debugging steps. The content could be tightened by removing some explanatory text that Claude wouldn't need.
Suggestions
Add explicit validation checkpoints between steps, e.g., 'Confirm the failing layer before proceeding to Step 2' and 'If Step 2 resolves the issue, skip to Step 5 for documentation'
Split the error pattern catalogs (Step 2 enrichment errors, Step 4 Claygent issues) and the support template (Step 5) into separate referenced files to reduce the main skill's token footprint
Remove the Prerequisites section's explanatory items like 'Understanding of Clay's enrichment architecture' — Claude either has this context or doesn't need to be told to have it
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some unnecessary verbosity. The YAML error pattern blocks are useful but could be tighter. The prerequisites section explains things Claude would know (what curl/jq are). The support escalation template, while useful, is lengthy. Some sections like Claygent debugging explain concepts that could be more concise. | 2 / 3 |
Actionability | The skill 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 a complete function with a working example call, and the error patterns map directly to specific fixes with exact UI navigation paths. | 3 / 3 |
Workflow Clarity | The 5-step sequence is logical and well-ordered (isolate layer → diagnose columns → debug HTTP API → debug Claygent → escalate). However, there are no explicit validation checkpoints or feedback loops between steps. For a debugging workflow involving potentially destructive retries and credit-consuming operations, there should be explicit 'verify before proceeding' gates between steps. | 2 / 3 |
Progressive Disclosure | The content is a single monolithic file with substantial inline detail (200+ lines). The error patterns, Claygent debugging, and support template could each be separate referenced files. The only external reference is to 'clay-load-scale' at the end. For a skill of this complexity, more content splitting would improve navigability. | 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.