Agent skill · data analytics · jeremylongshore
hex-debug-bundle
Collect Hex debug evidence for support tickets and troubleshooting.
Why this skill is useful
Adds a comprehensive diagnostic script for Hex API connectivity and troubleshooting that the AI wouldn't reliably generate on its own.
What it needs
Requires jq installed locally. Requires hex account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Hex Debug Bundle Overview Collect Hex API connectivity status, project listing, run history, data connection health, and rate limit state into a single diagnostic archive. This bundle helps troubleshoot failed notebook runs, stale data connections, scheduled run failures, and API authentication issues. Debug Collection Script Analyzing the Bundle Common Issues Symptom Check in Bundle Fix --------- ---------------- ----- API returns 401 summary.txt shows HTTP 401 Regenerate API token in Hex workspace Settings > API Run stuck in pending recent-runs.json shows pending status for >5 min Check compute quota; cancel and re-trigger the run Data connection failed connections.json shows error on a source Re-authenticate the connection; verify DB credentials haven't expired Scheduled run not firing recent-runs.json missing expected scheduled entries Check project schedule in Hex UI; verify project is published Rate limited (429) rate-headers.txt shows Retry-After Reduce API polling; batch project queries where possible Automated Health Check Prerequisites An incident ID, bounded collection window, approved restricted destination, and sandbox project with safe probe parameters. A redaction policy excluding API tokens, SQL, cell output, dataset values, user identities, and connection metadata before evidence leaves the runtime. Instructions 1. Collect only status, latency bands, run state, configuration revision, quota headers, and opaque project/run correlation IDs from the safe probe. 2. Run a redaction check before packaging and stop if output-bearing fields cannot be proven absent. 3. Compare aggregate results with the last known-good baseline, encrypt the bundle in the approved location, and grant minimum access. 4. Record owner and deletion date, then remove temporary artifacts after the incident window. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/hex-debug-bundle--75f08c