fireflies-debug-bundle
Generate a redacted debug bundle to resolve Fireflies.ai integration issues.
Install
mkdir -p .claude/skills/fireflies-debug-bundle && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5425" && unzip -o skill.zip -d .claude/skills/fireflies-debug-bundle && rm skill.zipInstalls to .claude/skills/fireflies-debug-bundle
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Collect Fireflies.ai debug evidence for support tickets and troubleshooting.Key capabilities
- →Collect environment information like Node and Python versions.
- →Check Fireflies.ai API connectivity and account info.
- →Retrieve metadata for recent transcripts.
- →List GraphQL package versions.
- →Redact sensitive configuration data.
How it works
This skill executes a bash script to gather system environment details, query the Fireflies.ai API for account and transcript metadata, and list relevant package versions. It then bundles this information into a redacted archive for support.
Inputs & outputs
When to use fireflies-debug-bundle
- →Creating a support ticket
- →Troubleshooting integration failures
- →Diagnosing environment issues
About this skill
Fireflies.ai Debug Bundle
Current State
!node --version 2>/dev/null || echo 'N/A'
!python3 --version 2>/dev/null || echo 'N/A'
Overview
Collect all diagnostic information needed to resolve Fireflies.ai integration issues. Generates a redacted bundle safe for sharing with support.
Prerequisites
FIREFLIES_API_KEYenvironment variable setcurlandjqavailable- Permission to collect environment info
Instructions
Step 1: Create Debug Bundle Script
#!/bin/bash
set -euo pipefail
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 -u +%Y-%m-%dT%H:%M:%SZ)" >> "$BUNDLE_DIR/summary.txt"
echo "" >> "$BUNDLE_DIR/summary.txt"
# 1. Environment
echo "--- Environment ---" >> "$BUNDLE_DIR/summary.txt"
echo "Node: $(node --version 2>/dev/null || echo 'N/A')" >> "$BUNDLE_DIR/summary.txt"
echo "Python: $(python3 --version 2>/dev/null || echo 'N/A')" >> "$BUNDLE_DIR/summary.txt"
echo "OS: $(uname -s) $(uname -r)" >> "$BUNDLE_DIR/summary.txt"
echo "API Key: ${FIREFLIES_API_KEY:+SET (${#FIREFLIES_API_KEY} chars)}" >> "$BUNDLE_DIR/summary.txt"
echo "" >> "$BUNDLE_DIR/summary.txt"
# 2. API Connectivity
echo "--- API Connectivity ---" >> "$BUNDLE_DIR/summary.txt"
curl -s -o "$BUNDLE_DIR/api-response.json" -w "HTTP %{http_code} | %{time_total}s\n" \
-X POST https://api.fireflies.ai/graphql \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $FIREFLIES_API_KEY" \
-d '{"query": "{ user { name email is_admin } }"}' \
>> "$BUNDLE_DIR/summary.txt" 2>&1
# 3. User & Plan Info
echo "" >> "$BUNDLE_DIR/summary.txt"
echo "--- Account Info ---" >> "$BUNDLE_DIR/summary.txt"
curl -s -X POST https://api.fireflies.ai/graphql \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $FIREFLIES_API_KEY" \
-d '{"query": "{ user { name email is_admin num_transcripts minutes_consumed is_calendar_in_sync integrations } }"}' \
| jq '.data.user | {name, is_admin, transcripts: .num_transcripts, minutes: .minutes_consumed, calendar_sync: .is_calendar_in_sync}' \
>> "$BUNDLE_DIR/summary.txt" 2>/dev/null
# 4. Recent Transcripts (metadata only)
echo "" >> "$BUNDLE_DIR/summary.txt"
echo "--- Recent Transcripts (last 5) ---" >> "$BUNDLE_DIR/summary.txt"
curl -s -X POST https://api.fireflies.ai/graphql \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $FIREFLIES_API_KEY" \
-d '{"query": "{ transcripts(limit: 5) { id title date duration organizer_email } }"}' \
| jq '.data.transcripts[]? | {id, title, date, duration}' \
>> "$BUNDLE_DIR/summary.txt" 2>/dev/null
# 5. GraphQL package versions
echo "" >> "$BUNDLE_DIR/summary.txt"
echo "--- Dependencies ---" >> "$BUNDLE_DIR/summary.txt"
npm list graphql graphql-request 2>/dev/null >> "$BUNDLE_DIR/summary.txt" || echo "No npm packages found" >> "$BUNDLE_DIR/summary.txt"
pip freeze 2>/dev/null | grep -i "request\|graphql" >> "$BUNDLE_DIR/summary.txt" || true
# 6. Config (redacted)
echo "" >> "$BUNDLE_DIR/summary.txt"
echo "--- Config (redacted) ---" >> "$BUNDLE_DIR/summary.txt"
if [ -f .env ]; then
cat .env | sed 's/=.*/=***REDACTED***/' >> "$BUNDLE_DIR/config-redacted.txt"
fi
# Package
tar -czf "$BUNDLE_DIR.tar.gz" "$BUNDLE_DIR"
rm -rf "$BUNDLE_DIR"
echo "Bundle created: $BUNDLE_DIR.tar.gz"
Step 2: Quick Health Check
set -euo pipefail
echo "=== Fireflies Quick Health Check ==="
# Auth
echo -n "Auth: "
curl -s -X POST https://api.fireflies.ai/graphql \
-H "Authorization: Bearer $FIREFLIES_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "{ user { email } }"}' | jq -r '.data.user.email // .errors[0].message'
# Calendar sync
echo -n "Calendar: "
curl -s -X POST https://api.fireflies.ai/graphql \
-H "Authorization: Bearer $FIREFLIES_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "{ user { is_calendar_in_sync } }"}' | jq -r '.data.user.is_calendar_in_sync'
# Recent meeting
echo -n "Last meeting: "
curl -s -X POST https://api.fireflies.ai/graphql \
-H "Authorization: Bearer $FIREFLIES_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "{ transcripts(limit: 1) { title date } }"}' | jq -r '.data.transcripts[0] | "\(.title) (\(.date))"'
Sensitive Data Handling
ALWAYS REDACT before sharing:
- API keys and tokens
- Meeting content and transcripts
- Attendee emails and names
- PII in action items
Safe to include:
- Error codes and messages
- HTTP status codes and latency
- Package versions
- Account metadata (admin status, transcript count)
Error Handling
| Item | Purpose | Included |
|---|---|---|
| API connectivity | Is the endpoint reachable? | HTTP status + latency |
| Auth check | Is the API key valid? | User email or error code |
| Calendar sync | Is the bot getting invites? | Boolean sync status |
| Recent transcripts | Is processing working? | Metadata only (no content) |
| Dependencies | Version conflicts? | Package versions |
Output
fireflies-debug-YYYYMMDD-HHMMSS.tar.gzarchive with:summary.txt-- environment, connectivity, account infoapi-response.json-- raw API responseconfig-redacted.txt-- configuration with secrets masked
Resources
Next Steps
For rate limit issues, see fireflies-rate-limits.
Prerequisites
Limitations
- →API keys and tokens must be redacted before sharing.
- →Meeting content and transcripts must be redacted.
- →Attendee emails and names must be redacted.
How it compares
This skill automates the collection of specific diagnostic information for Fireflies.ai, unlike manually gathering logs and system details.
Compared to similar skills
fireflies-debug-bundle side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| fireflies-debug-bundle (this skill) | 1 | 27d | Caution | Beginner |
| optimizing-performance | 1 | 2mo | Review | Intermediate |
| sentry-debug-bundle | 1 | 27d | Caution | Intermediate |
| sentry-error-capture | 1 | 27d | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
optimizing-performance
CloudAI-X
Analyzes and optimizes application performance across frontend, backend, and database layers. Use when diagnosing slowness, improving load times, optimizing queries, reducing bundle size, or when asked about performance issues.
sentry-debug-bundle
jeremylongshore
Execute collect debug information for Sentry support tickets. Use when preparing support requests, debugging complex issues, or gathering diagnostic information. Trigger with phrases like "sentry debug info", "sentry support ticket", "gather sentry diagnostics", "sentry debug bundle".
sentry-error-capture
jeremylongshore
Execute advanced error capture and context enrichment with Sentry. Use when implementing detailed error tracking, adding context, or customizing error capture behavior. Trigger with phrases like "sentry error capture", "sentry context", "enrich sentry errors", "sentry exception handling".
logging-monitoring
jnPiyush
Implement observability patterns including structured logging, log levels, correlation IDs, metrics, and distributed tracing. Use when adding structured logging, implementing correlation IDs for request tracing, configuring metrics collection, setting up distributed tracing, or designing alerting ru
langfuse
davila7
Expert in Langfuse - the open-source LLM observability platform. Covers tracing, prompt management, evaluation, datasets, and integration with LangChain, LlamaIndex, and OpenAI. Essential for debugging, monitoring, and improving LLM applications in production. Use when: langfuse, llm observability, llm tracing, prompt management, llm evaluation.
sentry-rate-limits
jeremylongshore
Manage Sentry rate limits and quota optimization. Use when hitting rate limits, optimizing event volume, or managing Sentry costs. Trigger with phrases like "sentry rate limit", "sentry quota", "reduce sentry events", "sentry 429".