Agent skill · data analytics · jeremylongshore
langfuse-debug-bundle
Collect Langfuse debug evidence for support tickets and troubleshooting.
Why this skill is useful
Provides a comprehensive script for collecting diagnostic information specific to Langfuse that the AI wouldn't reliably generate on its own.
What it needs
Requires bash installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Langfuse Debug Bundle Current State !node --version 2>/dev/null echo 'N/A' !python3 --version 2>/dev/null echo 'N/A' !npm list langfuse @langfuse/client @langfuse/tracing 2>/dev/null head -5 echo 'No langfuse packages' Overview Collect all diagnostic information needed for Langfuse support tickets: environment versions, SDK config, API connectivity, redacted logs, and a reproduction template. Prerequisites Langfuse SDK installed Access to application logs Bash shell available Instructions Step 1: Run the Full Debug Bundle Script Save this as langfuse-debug.sh and run it: Paste error output here typescript // Paste minimal reproduction here Step 2: Review Before Sharing Always redact before submitting: Include Redact --------- -------- Error messages and stack traces API keys (pk-lf-, sk-lf-) SDK versions and config structure Secret keys and passwords HTTP status codes PII (emails, user IDs) Timing and latency data Internal URLs and IPs OS and runtime versions Database connection strings Step 3: Submit to Support 1. Run: bash langfuse-debug.sh 2. Review bundle contents for leaked secrets 3. Fill in reproduction-steps.md 4. Submit via: GitHub Issues (public) Discord (community) Email support (enterprise customers) Step 4: Quick Inline Diagnostic (No File) For a fast check without creating files: Error Handling Collected Item Why It Matters ---------------- --------------- SDK version Version-specific bugs, breaking changes between v3/v4/v5 Environment versions Node 18+ required, Python 3.9+ Network test Firewall, DNS, self-hosted connectivity Auth test Key validity, project mismatch Redacted logs Trace errors, flush failures, rate limits Package deps Conflicting versions, missing peer deps Output Produce a sanitized archive and a short reproduction report containing the SDK/runtime versions, affected deployment environment, health-check result, and exact reproduction steps. The bundle must exclude keys, authorization headers, customer inputs, and unredacted logs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/langfuse-debug-bundle