fireflies-debug-bundle
Collect Fireflies.ai debug evidence for support tickets and troubleshooting.Use when encountering persistent issues, preparing support tickets,or collecting diagnostic information for Fireflies.ai problems.Trigger with phrases like "fireflies debug", "fireflies support bundle","collect fireflies logs", "fireflies diagnostic".
When & Why to Use This Skill
The Fireflies.ai Debug Bundle skill automates the collection of essential diagnostic information required for troubleshooting and technical support. It streamlines the debugging process by gathering environment metadata, SDK versions, and redacted logs while performing network connectivity tests, ultimately packaging all data into a secure, ready-to-submit archive to accelerate issue resolution.
Use Cases
- Case 1: Preparing a comprehensive diagnostic package for Fireflies.ai support tickets to reduce back-and-forth communication.
- Case 2: Troubleshooting persistent SDK integration issues or API connectivity errors in local or production environments.
- Case 3: Auditing environment configurations and dependency versions to ensure compatibility with Fireflies.ai requirements.
- Case 4: Securely collecting and redacting error logs for internal debugging to identify root causes without exposing sensitive API keys or PII.
| name | fireflies-debug-bundle |
|---|---|
| description | | |
| allowed-tools | Read, Bash(grep:*), Bash(curl:*), Bash(tar:*), Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Fireflies.ai Debug Bundle
Overview
Collect all necessary diagnostic information for Fireflies.ai support tickets.
Prerequisites
- Fireflies.ai SDK installed
- Access to application logs
- Permission to collect environment info
Instructions
Step 1: Create Debug Bundle Script
#!/bin/bash
# fireflies-debug-bundle.sh
BUNDLE_DIR="fireflies-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE_DIR"
echo "=== Fireflies.ai Debug Bundle ===" > "$BUNDLE_DIR/summary.txt"
echo "Generated: $(date)" >> "$BUNDLE_DIR/summary.txt"
Step 2: Collect Environment Info
# Environment info
echo "--- Environment ---" >> "$BUNDLE_DIR/summary.txt"
node --version >> "$BUNDLE_DIR/summary.txt" 2>&1
npm --version >> "$BUNDLE_DIR/summary.txt" 2>&1
echo "FIREFLIES_API_KEY: ${FIREFLIES_API_KEY:+[SET]}" >> "$BUNDLE_DIR/summary.txt"
Step 3: Gather SDK and Logs
# SDK version
npm list @fireflies/sdk 2>/dev/null >> "$BUNDLE_DIR/summary.txt"
# Recent logs (redacted)
grep -i "fireflies" ~/.npm/_logs/*.log 2>/dev/null | tail -50 >> "$BUNDLE_DIR/logs.txt"
# Configuration (redacted - secrets masked)
echo "--- Config (redacted) ---" >> "$BUNDLE_DIR/summary.txt"
cat .env 2>/dev/null | sed 's/=.*/=***REDACTED***/' >> "$BUNDLE_DIR/config-redacted.txt"
# Network connectivity test
echo "--- Network Test ---" >> "$BUNDLE_DIR/summary.txt"
echo -n "API Health: " >> "$BUNDLE_DIR/summary.txt"
curl -s -o /dev/null -w "%{http_code}" https://api.fireflies.com/health >> "$BUNDLE_DIR/summary.txt"
echo "" >> "$BUNDLE_DIR/summary.txt"
Step 4: Package Bundle
tar -czf "$BUNDLE_DIR.tar.gz" "$BUNDLE_DIR"
echo "Bundle created: $BUNDLE_DIR.tar.gz"
Output
fireflies-debug-YYYYMMDD-HHMMSS.tar.gzarchive containing:summary.txt- Environment and SDK infologs.txt- Recent redacted logsconfig-redacted.txt- Configuration (secrets removed)
Error Handling
| Item | Purpose | Included |
|---|---|---|
| Environment versions | Compatibility check | ✓ |
| SDK version | Version-specific bugs | ✓ |
| Error logs (redacted) | Root cause analysis | ✓ |
| Config (redacted) | Configuration issues | ✓ |
| Network test | Connectivity issues | ✓ |
Examples
Sensitive Data Handling
ALWAYS REDACT:
- API keys and tokens
- Passwords and secrets
- PII (emails, names, IDs)
Safe to Include:
- Error messages
- Stack traces (redacted)
- SDK/runtime versions
Submit to Support
- Create bundle:
bash fireflies-debug-bundle.sh - Review for sensitive data
- Upload to Fireflies.ai support portal
Resources
Next Steps
For rate limit issues, see fireflies-rate-limits.