New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Langfuse Incident Runbook

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Troubleshoot and respond to Langfuse-related incidents and outages.

MITAuto-check passedDevOps & Cloud

Install Langfuse Incident Runbook

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill langfuse-incident-runbook -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace langfuse-incident-runbook --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/langfuse-incident-runbook .claude/skills/langfuse-incident-runbook && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
langfuse-incident-runbook
GitHub stars
2.8k
Token cost
~2k tokens
SKILL.md length
486 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Troubleshoot and respond to Langfuse-related incidents and outages.

  • Works in 6 steps: Initial Assessment (2 Minutes) → Determine Incident Type and Response → Fallback Mode (P1 -- App Impacted) → …
  • Experiencing Langfuse outages
  • SKILL.md covers Prerequisites, Overview, Severity Classification and Instructions, plus 5 more sections
  • Calls curl, docker and python3; reaches status.langfuse.com; needs LANGFUSE_PUBLIC_KEY and LANGFUSE_SECRET_KEY

What it does

Langfuse Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Troubleshoot and respond to Langfuse-related incidents and outages. Use when experiencing Langfuse outages, debugging production issues, or responding to LLM observability incidents. Trigger with phrases like "langfuse incident", "langfuse outage", "langfuse down", "langfuse production issue", "langfuse troubleshoot".

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/implementation.md`). Compatibility notes: Designed for Claude Code

It sits in DevOps & Cloud, covering LLM observability, Incident response and Runbooks and postmortems. It works with Langfuse. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Experiencing Langfuse outages
  • Debugging production issues
  • Responding to LLM observability incidents
  • With phrases like langfuse incident

Example prompts

  • “langfuse incident”
  • “langfuse outage”
  • “langfuse down”
  • “/langfuse-incident-runbook”

Requirements

  • Python 3
  • Docker
  • A credential in LANGFUSE_PUBLIC_KEY
  • A credential in LANGFUSE_SECRET_KEY
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(curl:*)

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Initial Assessment (2 Minutes)
  2. Determine Incident Type and Response
  3. Fallback Mode (P1 -- App Impacted)
  4. Common Resolution Procedures
  5. Post-Incident Verification
  6. Post-Incident Review (P1/P2)

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(curl:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • docker
    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • status.langfuse.com

    Also links to:

    • langfuse.com
    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • LANGFUSE_PUBLIC_KEY
    • LANGFUSE_SECRET_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Langfuse Incident Runbook loads about 2k tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 486 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 486 words, ~1,998 tokens.

Download SKILL.mdSave it as .claude/skills/langfuse-incident-runbook/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
langfuse-incident-runbook
description
Troubleshoot and respond to Langfuse-related incidents and outages. Use when experiencing Langfuse outages, debugging production issues, or responding to LLM observability incidents. Trigger with phrases like "langfuse incident", "langfuse outage", "langfuse down", "langfuse production issue", "langfuse troubleshoot".
allowed-tools
Read, Write, Edit, Bash(curl:*)
compatibility
Designed for Claude Code
version
1.17.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, langfuse, observability, llm, debugging

Langfuse Incident Runbook

Prerequisites

  • Access to the affected Langfuse project, deployment logs, and the service status page.
  • An on-call contact and a change path for disabling or reconfiguring telemetry safely.
  • A redaction-safe incident record; do not paste API keys, authorization headers, or prompts into it.

Overview

Step-by-step procedures for Langfuse-related incidents, from initial triage (2 min) through resolution and post-incident review. Your application should work without Langfuse -- these procedures focus on restoring observability.

Severity Classification

SeverityDescriptionResponse TimeExample
P1Application impacted by tracing15 minSDK throwing unhandled errors, blocking requests
P2Traces not appearing, no app impact1 hourMissing observability data
P3Degraded performance from tracing4 hoursHigh latency from flush backlog
P4Minor issues24 hoursOccasional missing traces

Instructions

Step 1: Initial Assessment (2 Minutes)
bash
set -euo pipefail
echo "=== Langfuse Incident Triage ==="
echo "Time: $(date -u)"

# 1. Check Langfuse cloud status
echo -n "Status page: "
curl -s -o /dev/null -w "%{http_code}" https://status.langfuse.com || echo "UNREACHABLE"
echo ""

# 2. Test API connectivity
HOST="${LANGFUSE_BASE_URL:-${LANGFUSE_HOST:-https://cloud.langfuse.com}}"
echo -n "API health: "
curl -s -o /dev/null -w "%{http_code} (%{time_total}s)" "$HOST/api/public/health" || echo "FAILED"
echo ""

# 3. Test auth
if [ -n "${LANGFUSE_PUBLIC_KEY:-}" ] && [ -n "${LANGFUSE_SECRET_KEY:-}" ]; then
  AUTH=$(echo -n "$LANGFUSE_PUBLIC_KEY:$LANGFUSE_SECRET_KEY" | base64)
  echo -n "Auth test: "
  curl -s -o /dev/null -w "%{http_code}" \
    -H "Authorization: Basic $AUTH" "$HOST/api/public/traces?limit=1" || echo "FAILED"
  echo ""
fi

# 4. Check app error logs
echo ""
echo "--- Recent errors ---"
grep -i "langfuse\|trace.*error\|flush.*fail" /var/log/app/*.log 2>/dev/null | tail -10 || echo "No log files found"
Step 2: Determine Incident Type and Response
SymptomLikely CauseImmediate Action
No traces appearingSDK not flushingCheck shutdown handlers; set flushAt: 1 temporarily
401 UnauthorizedKey rotation or mismatchVerify keys match the correct project
429 Too Many RequestsRate limitedIncrease batch size, reduce flush frequency
SDK throwing errorsUnhandled exceptionWrap in try/catch; check SDK version
High request latencySync flush in hot pathSwitch to async; increase requestTimeout
Complete Langfuse outageService-side issueEnable fallback mode
Step 3: Fallback Mode (P1 -- App Impacted)

If Langfuse is causing application issues, disable tracing immediately:

typescript
// Emergency disable via environment variable
// Set LANGFUSE_ENABLED=false in your deployment

// In your tracing initialization:
if (process.env.LANGFUSE_ENABLED === "false") {
  console.warn("Langfuse tracing DISABLED (emergency fallback)");
  // Don't initialize SDK -- all observe/startActiveObservation calls
  // will still work but produce no-op spans
}

For v3, use the enabled flag:

typescript
const langfuse = new Langfuse({
  enabled: process.env.LANGFUSE_ENABLED !== "false",
});
Step 4: Common Resolution Procedures

Procedure A: Missing Traces

typescript
// 1. Verify SDK is initialized
console.log("Langfuse configured:", !!process.env.LANGFUSE_PUBLIC_KEY);

// 2. Check flush is happening
// v4+: Verify NodeSDK is started and shutdown is registered
// v3: Verify flushAsync() or shutdownAsync() is called

// 3. Temporarily set aggressive flush for debugging
const processor = new LangfuseSpanProcessor({
  exportIntervalMillis: 1000,
  maxExportBatchSize: 1,
});

Procedure B: Rate Limit (429) Recovery

typescript
// Increase batching to reduce API calls
const processor = new LangfuseSpanProcessor({
  exportIntervalMillis: 30000, // 30s flush
  maxExportBatchSize: 200,     // Large batches
});

// Or temporarily enable sampling
const EMERGENCY_SAMPLE_RATE = 0.1; // Only trace 10%

Procedure C: Self-Hosted Instance Down

bash
set -euo pipefail
# Check container status
docker ps -a | grep langfuse

# Check logs
docker logs langfuse-langfuse-1 --tail 50

# Check database
docker exec langfuse-postgres-1 pg_isready -U langfuse

# Restart if needed
docker compose restart langfuse
Step 5: Post-Incident Verification
bash
set -euo pipefail
# Verify traces are flowing again
echo "=== Post-Incident Check ==="

HOST="${LANGFUSE_BASE_URL:-https://cloud.langfuse.com}"
AUTH=$(echo -n "$LANGFUSE_PUBLIC_KEY:$LANGFUSE_SECRET_KEY" | base64)

# Check recent trace count
TRACE_COUNT=$(curl -s \
  -H "Authorization: Basic $AUTH" \
  "$HOST/api/public/traces?limit=5" | python3 -c "import sys,json; print(len(json.load(sys.stdin).get('data',[])))" 2>/dev/null || echo "ERROR")

echo "Recent traces: $TRACE_COUNT"

if [ "$TRACE_COUNT" = "0" ] || [ "$TRACE_COUNT" = "ERROR" ]; then
  echo "WARNING: Traces may not be flowing yet"
else
  echo "OK: Traces are appearing"
fi
Step 6: Post-Incident Review (P1/P2)

Document for post-mortem:

  1. Timeline: When detected, when resolved, total duration
  2. Impact: Traces lost, application impact, user impact
  3. Root cause: Why did the incident occur?
  4. Resolution: What fixed it?
  5. Prevention: What changes prevent recurrence?
  6. Action items: Improvements to implement
Show full SKILL.md (178 more words)Show less

Escalation Path

LevelWhoWhen
L1On-call engineerAll incidents -- run triage
L2Platform team leadP1/P2 unresolved after 30 min
L3Langfuse supportConfirmed service-side issue

Langfuse support channels:

Error Handling

IssueImmediate FixPermanent Fix
SDK crashes appSet LANGFUSE_ENABLED=falseWrap all tracing in try/catch
Lost tracesIncrease batch sizeAdd shutdown handlers
High latencyDisable sync flushUse async-only patterns
Auth failuresRotate and redeploy keysAdd key validation at startup

Output

Produce an incident record with severity, start/end time, customer impact, affected project, mitigation, and post-incident owner. Include a sanitized trace-flow result and the rollback decision; exclude raw credentials and customer payloads.

Examples

For missing traces, first check the status page and deployment revision, then perform a single synthetic trace check after restoring connectivity. For a P1 self-hosted outage, capture the database health result, apply the approved rollback or restart, and create a post-incident review with a named prevention action.

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/langfuse-incident-runbook of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/implementation.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Langfuse Incident Runbook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Langfuse Incident Runbook compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Langfuse Incident Runbook this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2kAutomated safety check: PassMIT
Infra Scalinglangfuse/langfuse36k—~4.4kAutomated safety check: PassCustom licence
Create Repo Agentlangfuse/langfuse36k—~730Automated safety check: PassCustom licence
Ak Dev New Tracing Provideryaalalabs/agent-kernel192—~3.5kAutomated safety check: PassApache-2.0
Langfuselangfuse/skills301—~2.1kAutomated safety check: NotesMIT
Oncallpigweed-project/pigweed548—~963Automated safety check: PassApache-2.0

Similar skills

  • Infra Scaling

    langfuse/langfuse

    Tune and review Langfuse autoscaling for web, web-iso, and web-ingestion.

    36k GitHub stars~4.4k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Create Repo Agent

    langfuse/langfuse

    Design, implement, review, or harden Langfuse repo-owned autonomous agents.

    36k GitHub stars~730 tokensUpdated today
    DevOps & CloudAuto-check passed

  • Ak Dev New Tracing Provider

    yaalalabs/agent-kernel

    Step-by-step guide for adding a new observability/tracing provider to Agent Kernel.

    192 GitHub stars~3.5k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

  • Langfuse

    langfuse/skills

    Interact with Langfuse and access its documentation: tracing, monitoring, creating datasets, running experiments, and evaluating AI applications.

    301 GitHub stars~2.1k tokensUpdated 10 days ago
    AI & LLM EngineeringAuto-check: notes

  • Oncall

    pigweed-project/pigweed

    Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).

    548 GitHub stars~963 tokensUpdated today
    DevOps & CloudAuto-check passed

  • Activation Governance Chaos Rollout

    Ali-Marandi/DataSense

    Design, validate, and govern fail-closed customer-activation automations that use an Outbox/worker pattern.

    107 GitHub stars~1.9k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Langfuse Incident Runbook

What does Langfuse Incident Runbook do?

Troubleshoot and respond to Langfuse-related incidents and outages. Langfuse Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Troubleshoot and respond to Langfuse-related incidents and outages.

When should I use Langfuse Incident Runbook?

Langfuse Incident Runbook fits situations like: experiencing Langfuse outages; debugging production issues; responding to LLM observability incidents; with phrases like langfuse incident.

How do I install Langfuse Incident Runbook in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill langfuse-incident-runbook -a claude-code`. Or copy the skill folder (skills/.curated/langfuse-incident-runbook in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/langfuse-incident-runbook in your project. Claude Code loads it when a task matches its description.

How do I install Langfuse Incident Runbook in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill langfuse-incident-runbook -a codex`. Or copy the skill folder (skills/.curated/langfuse-incident-runbook in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/langfuse-incident-runbook in your project. Codex loads it when a task matches its description.

Can I use Langfuse Incident Runbook in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill langfuse-incident-runbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/langfuse-incident-runbook, .gemini/skills/langfuse-incident-runbook, .github/skills/langfuse-incident-runbook and .opencode/skills/langfuse-incident-runbook in your project.

What does Langfuse Incident Runbook need to run?

Going by SKILL.md and its folder, Langfuse Incident Runbook needs the command-line tools its instructions call (curl, docker and python3) and credentials named LANGFUSE_PUBLIC_KEY and LANGFUSE_SECRET_KEY. Our summary lists: Python 3; Docker; A credential in LANGFUSE_PUBLIC_KEY; A credential in LANGFUSE_SECRET_KEY. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(curl:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Langfuse Incident Runbook access the network?

SKILL.md names 3 domains. In commands or code: status.langfuse.com; the agent is likely to contact it when it follows the instructions. As links in the text: langfuse.com and github.com. This is read from the text; nothing was executed.

Is Langfuse Incident Runbook safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Langfuse Incident Runbook use?

Langfuse Incident Runbook is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Langfuse Incident Runbook use?

About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 937 tokens, read only when the agent opens those files.

What are the alternatives to Langfuse Incident Runbook?

Skills that share tags, products or a category with Langfuse Incident Runbook: Infra Scaling (langfuse/langfuse, 36k stars), Create Repo Agent (langfuse/langfuse, 36k stars), Ak Dev New Tracing Provider (yaalalabs/agent-kernel, 192 stars) and Langfuse (langfuse/skills, 301 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Langfuse Incident Runbook?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.