LA

langfuse-common-errors

Provides diagnostic steps to resolve Langfuse authentication issues and missing trace data.

Install

mkdir -p .claude/skills/langfuse-common-errors && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5422" && unzip -o skill.zip -d .claude/skills/langfuse-common-errors && rm skill.zip

Installs to .claude/skills/langfuse-common-errors

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.

Diagnose and fix common Langfuse errors and exceptions.
55 charsno explicit “when” trigger
Beginner

Key capabilities

  • →Diagnose 401 authentication errors
  • →Troubleshoot missing dashboard traces
  • →Verify SDK configuration and API connectivity
  • →Fix span flushing and timeout issues
  • →Resolve duplicate trace generation

How it works

The skill provides a reference of common error messages and symptoms, mapping them to specific root causes and providing code-level fixes or CLI diagnostic commands.

Inputs & outputs

You give it
Error message or symptom
You get back
Diagnostic steps and code fixes

When to use langfuse-common-errors

  • →Debug missing traces in dashboard
  • →Fix 401 authentication errors
  • →Verify Langfuse SDK configuration
  • →Troubleshoot trace flushing issues

About langfuse-common-errors

Includes troubleshooting instructions for common errors like unauthorized access (401) and missing dashboard traces. It provides commands to verify API health and SDK configuration.

Diagnose and fix common Langfuse errors and exceptions. Use when encountering Langfuse errors, debugging missing traces, or troubleshooting integration issues. Trigger with phrases like "langfuse error", "fix langfuse", "langfuse not working", "debug langfuse", "traces not appearing".

When not to use it

  • →Debugging non-Langfuse infrastructure issues
  • →Resolving network issues unrelated to Langfuse endpoints

Prerequisites

Langfuse SDK installedAPI credentialsAccess to application logs

Limitations

  • →Requires access to application logs or console output
  • →Diagnostic script requires Node.js or Python environment

How it compares

It centralizes troubleshooting for specific Langfuse error patterns, whereas manual debugging requires searching through general SDK documentation.

Compared to similar skills

langfuse-common-errors side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
langfuse-common-errors (this skill)14moCautionBeginner
langsmith-fetch610moReviewIntermediate
autotel05moReviewIntermediate
backend-telemetry-hardening06moNo flagsAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore →

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

You might also like

langsmith-fetch

ComposioHQ

Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.

67

autotel

jagreehal

Use when instrumenting with trace/span/track, reviewing code for logging and observability patterns, converting console.log to wide events, adding structured errors, setting up canonical log lines, configuring init(), adding subscribers, or working in the autotel monorepo.

00

backend-telemetry-hardening

MrPatt025

Harden backend telemetry ingestion under load (MQTT spikes, DB pool pressure, validation failures).

00

ai-debug-harness

DeandreFu

Self-driving Electron + Node debug harness with NDJSON logs, Playwright E2E, doctor preflight, and a YAML-frontmatter cookbook of known causes. Use when a voice-chat E2E flow misbehaves locally, audio publish silently fails, the agent worker emits warnings, or any LiveKit/Electron/Fastify error appe

00

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

00

chrome-devtools

mrgoonie

Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.

41157

Search skills

Search the agent skills registry