ClaudeSuperPower

langfuse

Skill

Interact with Langfuse and access its documentation. Use when needing to (1) query or modify Langfuse data programmatically via the CLI — traces, prompts, datasets, scores, sessions, and any other API resource, (2) look up Langfuse documentation, concepts, integration guides, or SDK usage, or (3) un

Install

git clone https://github.com/langfuse/skills.git ~/.claude/skills/langfuse

What is langfuse?

Interact with Langfuse and access its documentation. Use when needing to (1) query or modify Langfuse data programmatically via the CLI — traces, prompts, datasets, scores, sessions, and any other API resource, (2) look up Langfuse documentation, concepts, integration guides, or SDK usage, or (3) understand how any Langfuse feature works. This skill covers CLI-based API access (via npx) and multiple documentation retrieval methods.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Run shell commands

Declares Bash

Access the network

Declares WebFetch or WebSearch

~109 tokens of context used while enabled, before you invoke anything

All declared tools (2)
BashWebFetch

Documentation

README · ~5 min read

Langfuse

This skill helps you use Langfuse effectively across all common workflows: instrumenting applications, migrating prompts, debugging traces, and accessing data programmatically.

Core Principles

Follow these principles for ALL Langfuse work:

  1. Documentation First: NEVER implement based on memory. Always fetch current docs before writing code (Langfuse updates frequently) See the section below on how to access documentation.
  2. CLI for Data Access: Use langfuse-cli when querying/modifying Langfuse data. See the section below on how to use the CLI.
  3. Best Practices by Use Case: Check the relevant reference file below for use-case-specific guidelines before implementing
  4. Use latest Langfuse versions: Unless the user specified otherwise or there's a good reason, always use the latest version of Langfuse SDKs/APIs. Even if you're only creating a plan for another agent to execute, be explicit about the exact version to use.
  5. If you guide the user through UI and are unsure about a label or location, inspect the user’s screenshots or ask to see the relevant screen. Do not assume UI labels have the exact same names as API, SDK, or CLI fields.

Use case specific references

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.