Juicebox Debug Bundle

Overview

Collect comprehensive diagnostic information for Juicebox support tickets.

Prerequisites

• Access to application logs
• Juicebox API key configured
• Terminal access

Instructions

1. Step 1: Collect Environment Info
2. Step 2: Test API Connectivity
3. Step 3: Gather Error Logs
4. Step 4: Create Support Bundle

For full implementation details and code examples, load: Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)

Output

• debug-bundle.txt - Text summary
• debug-bundle-*.json - Structured data
• Filtered error logs
• API connectivity results

Resources

• Support Portal
• Community Forum

Next Steps

After collecting debug info, check juicebox-rate-limits for quota issues.

Error Handling

Error	Cause	Resolution
Authentication failure	Invalid or expired credentials	Refresh tokens or re-authenticate with debugging
Configuration conflict	Incompatible settings detected	Review and resolve conflicting parameters
Resource not found	Referenced resource missing	Verify resource exists and permissions are correct

Examples

Basic usage: Apply juicebox debug bundle to a standard project setup with default configuration options.

Advanced scenario: Customize juicebox debug bundle for production environments with multiple constraints and team-specific requirements.