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.mdDebug bundle collection script
Bundle subdirectory structure
66%
100%
Timestamped bundle name
100%
100%
kubectl pod log collection
20%
100%
journalctl system log collection
25%
100%
Prometheus requests metric
37%
100%
Prometheus errors metric
0%
100%
tcpdump network capture
66%
100%
Jaeger trace collection
100%
100%
kubectl configmap collection
62%
100%
tar.gz archive creation
100%
100%
kubectl secret collection
62%
100%
Without context: $0.2535 · 1m 26s · 12 turns · 12 in / 5,694 out tokens
With context: $0.4876 · 1m 37s · 27 turns · 27 in / 4,860 out tokens
Layer-by-layer isolation and minimal repro
Six-layer test order
33%
100%
api.clay.com in DNS/TLS layers
75%
100%
First failure identification
100%
100%
Fresh ClayClient minimal config
0%
70%
Ping as simplest call
0%
62%
Error detail logging
12%
100%
performance.now() timing
0%
100%
p95 statistic in timing report
0%
100%
60-second heap sampling interval
0%
100%
100MB growth alert threshold
100%
100%
1-hour sample window
0%
100%
Without context: $0.4987 · 2m 40s · 18 turns · 19 in / 10,159 out tokens
With context: $0.5144 · 2m 18s · 21 turns · 286 in / 7,955 out tokens
Support escalation document
Severity P-level
0%
100%
Request ID field
100%
100%
ISO 8601 timestamp
100%
100%
Issue Summary paragraph
100%
100%
Steps to Reproduce
37%
25%
Expected vs Actual behavior
0%
50%
Debug bundle evidence item
60%
100%
Minimal repro evidence item
100%
100%
Timing analysis evidence item
100%
100%
Network capture evidence item
62%
100%
Workarounds Attempted section
16%
100%
Without context: $0.4230 · 2m 13s · 19 turns · 20 in / 7,014 out tokens
With context: $0.3516 · 1m 48s · 15 turns · 47 in / 5,333 out tokens
Table of Contents
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.