Agent skill · software engineering · jeremylongshore
juicebox-debug-bundle
Collect Juicebox debug evidence.
Why this skill is useful
Adds an executable script for collecting and analyzing Juicebox API diagnostics, which isn't available in public documentation.
What it needs
Requires jq installed locally. Requires juicebox account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Juicebox Debug Bundle Overview Collect Juicebox API connectivity status, dataset health, analysis quota usage, and rate limit state into a single diagnostic archive. This bundle helps troubleshoot failed dataset uploads, stalled AI analysis runs, quota exhaustion, and API authentication problems. Debug Collection Script Analyzing the Bundle Common Issues Symptom Check in Bundle Fix --------- ---------------- ----- API returns 401 summary.txt shows HTTP 401 Regenerate API key in Juicebox Settings > API Keys Dataset upload stuck datasets.json shows processing status for >10 min Check file format (CSV/JSON required); reduce file size below 100MB Analysis quota exhausted quota.json shows remaining at 0 Upgrade plan or wait for monthly quota reset Analysis run failed recent-analyses.json shows error status Check dataset has required columns; verify data types match analysis type Rate limited (429) rate-headers.txt shows Retry-After Implement exponential backoff; batch dataset queries Automated Health Check Prerequisites A sandbox workspace, synthetic fixture, approved diagnostic scope, redaction rules, secret references, source/destination allowlists, and an incident owner with a cleanup path. Instructions 1. Collect diagnostics from a sandbox fixture only; reject literal credentials, contact-level payloads, and unapproved sources or destinations. 2. Capture aggregate health, quota, and error signals, then verify suppression, log redaction, and contactsexported=0. 3. Stop collection on policy, scope, or retention drift; revoke temporary access and restore the known-good configuration if required. 4. Store only the redacted bundle for the approved retention window, then delete staged artifacts. Output Produce a debug receipt with environment, fixture type, aggregate health/error/quota signals, suppression/no-export/redaction checks, incident owner, retention/deletion proof, and rollback reference. Exclude request payloads, identities, contact data, and secrets. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/juicebox-debug-bundle--d0d89b