langfuse-trace-list
List Langfuse traces with filtering options. Use when checking recent LLM calls, debugging issues, or monitoring costs.
Works with
--- name: langfuse-trace-list description: List Langfuse traces with filtering options. Use when checking recent LLM calls, debugging issues, or monitoring costs. license: MIT --- # Langfuse Trace List Display the latest traces with filtering options. ## Setup Set the following environment variables before use: | Variable | Required | Description | |----------|----------|-------------| | `LANGFUSE_PUBLIC_KEY` | Yes | Langfuse public key | | `LANGFUSE_SECRET_KEY` | Yes | Langfuse secret key | | `LANGFUSE_HOST` or `LANGFUSE_BASE_URL` | No | Langfuse host URL (default: `https://us.cloud.langfuse.com`) | ## When to Use - Checking the trace list - Debugging LLM calls - "Show me recent traces" - "Check traces for a specific user" ## Commands ### 1. Get Trace List Get the latest 20 traces: ```bash npx tsx scripts/langfuse-trace-list.ts ``` Specify the number of traces: ```bash npx tsx scripts/langfuse-trace-list.ts --limit=50 ``` ### 2. Filter Options ```bash # Filter by trace name npx tsx scripts/langfuse-trace-list.ts --name=librarian/chat # Filter by user ID npx tsx scripts/langfuse-trace-list.ts --user=user-123 # Filter by session ID npx tsx scripts/langfuse-trace-list.ts --session=session-abc # Filter by environment npx tsx scripts/langfuse-trace-list.ts --env=production # Combine multiple filters npx tsx scripts/langfuse-trace-list.ts --name=chat --env=production --limit=100 ``` ## Output Example ``` Langfuse Traces =============== Timestamp Name User Session Cost ID ---------------------------------------------------------------------------------------------------------------------------------- 2025-01-15 10:30:45 librarian/chat user-123 session-abc $0.0150 abc123... 2025-01-15 10:28:12 knowledge-builder/extract user-456 session-def $0.0080 def456... 2025-01-15 10:25:33 chat/respond user-789 - $0.0045 ghi789... Showing 3 of 1234 traces ``` ## Fields | Field | Description | |-------|-------------| | Timestamp | Trace creation timestamp | | Name | Trace name (feature/action format) | | User | User ID | | Session | Session ID | | Cost | Estimated cost | | ID | Trace ID (for viewing details) |
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
