AgentSkillsCN

firecrawl-debug-bundle

收集FireCrawl调试证据，用于支持工单和故障排除。 在遇到持续问题、准备支持工单或收集FireCrawl问题的诊断信息时使用。 可通过“firecrawl debug”、“firecrawl support bundle”、“collect firecrawl logs”、“firecrawl diagnostic”等短语触发。

SKILL.md
--- frontmatter
name: firecrawl-debug-bundle
description: |
  Collect FireCrawl debug evidence for support tickets and troubleshooting.
  Use when encountering persistent issues, preparing support tickets,
  or collecting diagnostic information for FireCrawl problems.
  Trigger with phrases like "firecrawl debug", "firecrawl support bundle",
  "collect firecrawl logs", "firecrawl diagnostic".
allowed-tools: Read, Bash(grep:*), Bash(curl:*), Bash(tar:*), Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>

FireCrawl Debug Bundle

Overview

Collect all necessary diagnostic information for FireCrawl support tickets.

Prerequisites

  • •FireCrawl SDK installed
  • •Access to application logs
  • •Permission to collect environment info

Instructions

Step 1: Create Debug Bundle Script

bash
#!/bin/bash
# firecrawl-debug-bundle.sh

BUNDLE_DIR="firecrawl-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE_DIR"

echo "=== FireCrawl Debug Bundle ===" > "$BUNDLE_DIR/summary.txt"
echo "Generated: $(date)" >> "$BUNDLE_DIR/summary.txt"

Step 2: Collect Environment Info

bash
# 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 "FIRECRAWL_API_KEY: ${FIRECRAWL_API_KEY:+[SET]}" >> "$BUNDLE_DIR/summary.txt"

Step 3: Gather SDK and Logs

bash
# SDK version
npm list @firecrawl/sdk 2>/dev/null >> "$BUNDLE_DIR/summary.txt"

# Recent logs (redacted)
grep -i "firecrawl" ~/.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.firecrawl.com/health >> "$BUNDLE_DIR/summary.txt"
echo "" >> "$BUNDLE_DIR/summary.txt"

Step 4: Package Bundle

bash
tar -czf "$BUNDLE_DIR.tar.gz" "$BUNDLE_DIR"
echo "Bundle created: $BUNDLE_DIR.tar.gz"

Output

  • •firecrawl-debug-YYYYMMDD-HHMMSS.tar.gz archive containing:
    • •summary.txt - Environment and SDK info
    • •logs.txt - Recent redacted logs
    • •config-redacted.txt - Configuration (secrets removed)

Error Handling

ItemPurposeIncluded
Environment versionsCompatibility check✓
SDK versionVersion-specific bugs✓
Error logs (redacted)Root cause analysis✓
Config (redacted)Configuration issues✓
Network testConnectivity 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

  1. •Create bundle: bash firecrawl-debug-bundle.sh
  2. •Review for sensitive data
  3. •Upload to FireCrawl support portal

Resources

Next Steps

For rate limit issues, see firecrawl-rate-limits.