clay-advanced-troubleshooting
Apply Clay advanced debugging techniques for hard-to-diagnose issues. Use when standard troubleshooting fails, investigating complex race conditions, or preparing evidence bundles for Clay support escalation. Trigger with phrases like "clay hard bug", "clay mystery error", "clay impossible to debug", "difficult clay issue", "clay deep debug".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-advanced-troubleshooting82
Quality
77%
Does it follow best practices?
Impact
94%
1.91xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/clay-pack/skills/clay-advanced-troubleshooting/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 well-structured skill description with excellent trigger terms and clear when-to-use guidance. The main weakness is the somewhat vague specification of what concrete debugging techniques or actions are actually performed - it tells you when to use it better than what it actually does.
Suggestions
Add 2-3 specific concrete actions the skill performs, such as 'analyzes stack traces', 'captures timing logs', 'generates reproduction steps', or 'creates diagnostic reports'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clay debugging) and mentions some actions like 'investigating complex race conditions' and 'preparing evidence bundles for Clay support escalation', but lacks comprehensive concrete actions - doesn't specify what debugging techniques are applied or what outputs are produced. | 2 / 3 |
Completeness | Clearly answers both what ('Apply Clay advanced debugging techniques') and when ('Use when standard troubleshooting fails, investigating complex race conditions, or preparing evidence bundles'). Includes explicit trigger guidance with specific phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases users would say: 'clay hard bug', 'clay mystery error', 'clay impossible to debug', 'difficult clay issue', 'clay deep debug'. These are realistic phrases a frustrated user would type when standard debugging fails. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - specifically targets advanced/hard Clay debugging scenarios that standard troubleshooting can't solve. The 'hard bug', 'mystery error', 'impossible to debug' triggers clearly differentiate from basic Clay troubleshooting 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 advanced troubleshooting skill with highly actionable, executable code examples and a comprehensive approach to debugging. The main weaknesses are the length (could benefit from splitting detailed code into reference files) and the lack of explicit validation checkpoints in the workflow steps. The support escalation template and error handling table are valuable additions.
Suggestions
Add explicit validation checkpoints in the Instructions section (e.g., 'Verify bundle contains all expected files before proceeding to Step 2')
Consider moving detailed code examples (TimingAnalyzer, memory analysis, race condition detection) to a separate ADVANCED-DEBUGGING-CODE.md reference file
Add a verification step after the debug bundle collection to confirm all components were captured successfully
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elements like the full TimingAnalyzer class with percentile method and memory monitoring code that could be condensed. The bash script and TypeScript examples are thorough but could be tightened. | 2 / 3 |
Actionability | Provides fully executable bash scripts, TypeScript code, and curl commands that are copy-paste ready. The debug bundle script, layer testing functions, and support template are all concrete and immediately usable. | 3 / 3 |
Workflow Clarity | The Instructions section provides a clear 4-step sequence, but lacks explicit validation checkpoints between steps. For complex debugging involving destructive operations like network captures, there should be verification steps confirming each phase completed successfully before proceeding. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the skill is quite long with detailed code that could be split into separate reference files. The reference to 'clay-load-scale' at the end is good, but inline code blocks for timing analysis and memory profiling could be externalized. | 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 | |
- 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.