Token导航 LogoToken导航TokenDH.com
研究检索external-servicegithub未标认证来源可访问许可证需确认审计异常

langfuselangfuse 测试

Agent Skill

langfuse 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

321

周安装

13

GitHub Stars

公开资料未说明

下载量

101
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:langfuse(langfuse 测试)
来源仓库:https://github.com/efoo-team/skills
仓库路径:skills/langfuse
安装命令:
npx skills add https://github.com/efoo-team/skills --skill langfuse
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/efoo-team/skills --skill langfuse

简介

用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 可结合来源仓库、安装命令和原始 README 继续核验具体用法。
  • 安装方式:github,安装命令:npx skills add https://github.com/efoo-team/skills --skill langfuse。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • langfuse 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Langfuse Observability Skill

Query Langfuse observability data via REST API to debug agent runs, analyze LLM costs, and inspect prompt versions. This skill complements the Langfuse Prompt MCP (built-in) which handles prompt CRUD — this skill covers everything else.

Prerequisites

Authentication: All API calls require HTTP Basic Auth.

  • Username: LANGFUSE_PUBLIC_KEY (e.g., pk-lf-...)
  • Password: LANGFUSE_SECRET_KEY (e.g., sk-lf-...)

Base URL: Read from .env:

grep LANGFUSE_BASE_URL .env  # e.g., http://localhost:4300

Quick connectivity check:

curl -s -u "pk-lf-...:sk-lf-..." "${LANGFUSE_BASE_URL:-http://localhost:4300}/api/public/projects" | jq '.'

Self-Hosted vs Cloud API Differences

FeatureSelf-HostedCloud
Traces (v1)
Observations (v1)
Observations (v2, cursor-based)❌ Cloud-only beta
Metrics (v2, aggregated analytics)❌ Limited/unsupported
Scores
Sessions
Prompts
Datasets
Comments
Annotation Queues
Score Configs

Always use v1 endpoints for self-hosted. V2 endpoints return NotImplementedError on local instances.

Core API Endpoints

Setup (run once per session)

# Read credentials from .env
LANGFUSE_BASE_URL=$(grep LANGFUSE_BASE_URL .env | cut -d'"' -f2)
LANGFUSE_PK=$(grep LANGFUSE_PUBLIC_KEY .env | cut -d'"' -f2)
LANGFUSE_SK=$(grep LANGFUSE_SECRET_KEY .env | cut -d'"' -f2)
AUTH="-u ${LANGFUSE_PK}:${LANGFUSE_SK}"
BASE="${LANGFUSE_BASE_URL}/api/public"

1. Traces — Agent run overviews

List traces with pagination and filters:

# Recent traces (default: 10 per page)
curl -s $AUTH "$BASE/traces?limit=10" | jq '.data[] | {id, name, timestamp, totalCost, latency, userId}'

# Filter by user, tags, time range
curl -s $AUTH "$BASE/traces?limit=10&userId=<user-id>&fromTimestamp=2026-03-20T00:00:00Z&toTimestamp=2026-03-21T23:59:59Z"

# Single trace detail (includes full input/output/metadata)
curl -s $AUTH "$BASE/traces/<trace-id>" | jq '.'

Key fields: name (agent/workflow name), input/output, metadata (agent config, instructions), totalCost, latency, observations (child IDs), scores, sessionId, userId

2. Observations — Spans, Generations, Events

# Observations for a specific trace
curl -s $AUTH "$BASE/observations?traceId=<trace-id>&limit=50" | jq '.data[] | {id, type, name, model, startTime, endTime, latency, calculatedTotalCost, usage}'

# Filter by type (SPAN, GENERATION, EVENT)
curl -s $AUTH "$BASE/observations?traceId=<trace-id>&type=GENERATION&limit=20"

# Single observation detail
curl -s $AUTH "$BASE/observations/<observation-id>" | jq '.'

Key fields: type (SPAN/GENERATION/EVENT), name, model, input/output, usage (promptTokens, completionTokens), calculatedTotalCost, latency, parentObservationId, metadata, level (DEFAULT/WARNING/ERROR)

3. Sessions — Conversation threads

# List sessions
curl -s $AUTH "$BASE/sessions?limit=20" | jq '.data[] | {id, createdAt, projectId, environment}'

# Get traces for a session (via trace filter)
curl -s $AUTH "$BASE/traces?sessionId=<session-id>&limit=20" | jq '.data[] | {id, name, timestamp, totalCost}'

4. Scores — Evaluations

# List scores
curl -s $AUTH "$BASE/scores?limit=20" | jq '.data[]'

# Score configs (templates)
curl -s $AUTH "$BASE/score-configs?limit=20" | jq '.data[]'

5. Projects

curl -s $AUTH "$BASE/projects" | jq '.data[] | {id, name, organization}'

6. Datasets & Dataset Items

# List datasets
curl -s $AUTH "$BASE/v2/datasets?limit=20" | jq '.data[]'

# Dataset items
curl -s $AUTH "$BASE/dataset-items?datasetName=<name>&limit=20" | jq '.data[]'

7. Comments

# List comments (filter by objectType: trace, observation, session, prompt)
curl -s $AUTH "$BASE/comments?limit=20" | jq '.data[]'

Common Investigation Workflows

Workflow A: Debug a failed agent run

  1. Find the trace: Search traces by time range or agent name curl -s $AUTH "$BASE/traces?limit=20" | jq '[.data[] | {id, name, timestamp, latency, totalCost, level:.metadata.level}]'
  2. Get trace detail: Inspect input/output for the failed trace curl -s $AUTH "$BASE/traces/<trace-id>" | jq '.'
  3. Find errors in observations: Look for level=WARNING or level=ERROR curl -s $AUTH "$BASE/observations?traceId=<trace-id>&limit=50" | jq '[.data[] | select(.level!= "DEFAULT") | {id, type, name, level, statusMessage, startTime}]'
  4. Inspect the failing generation: Get full model input/output curl -s $AUTH "$BASE/observations/<observation-id>" | jq '{type, name, model, input, output, usage, calculatedTotalCost, latency, statusMessage}'

Workflow B: Analyze costs and latency

  1. Cost overview: Summarize costs across recent traces curl -s $AUTH "$BASE/traces?limit=50" | jq '{totalCost: ([.data[].totalCost] | add), avgCost: ([.data[].totalCost] | add / length), avgLatency: ([.data[].latency] | add / length), traceCount:.meta.totalItems}'
  2. Per-model breakdown: Extract model costs from generations curl -s $AUTH "$BASE/observations?limit=100&type=GENERATION" | jq 'group_by(.model) | map({model:.[0].model, count: length, totalCost: (map(.calculatedTotalCost) | add), avgTokens: (map(.usage.total) | add / length)})'

Workflow C: Trace a conversation session

  1. List sessions: Find the target session curl -s $AUTH "$BASE/sessions?limit=20" | jq '.data[]'
  2. Get all traces for a session: Full conversation history curl -s $AUTH "$BASE/traces?sessionId=<session-id>&limit=50" | jq '[.data[] | {id, name, timestamp, input: (.input[0].content |.[0:100]), output: (.output.text //.output | tostring |.[0:100]), totalCost, latency}]'

Workflow D: Audit prompt versions

Use the built-in Langfuse Prompt MCP tools for prompt CRUD:

  • langfuse_listPrompts — list all prompts
  • langfuse_getPrompt — get compiled prompt with dependencies resolved
  • langfuse_getPromptUnresolved — get raw prompt with dependency tags
  • langfuse_createTextPrompt / langfuse_createChatPrompt — create new versions
  • langfuse_updatePromptLabels — manage production/staging labels

Note: The REST API GET /api/public/prompts requires a name parameter. Use MCP tools for listing.

Pagination

All v1 endpoints use page-based pagination:

  • page (starts at 1), limit (default varies, typically 10)
  • Response includes meta.totalItems and meta.totalPages
# Page through results
curl -s $AUTH "$BASE/traces?limit=50&page=1" | jq '.meta'
curl -s $AUTH "$BASE/traces?limit=50&page=2" | jq '.meta'

v2 Cloud endpoints use cursor-based pagination (not available on self-hosted).

Output Truncation

For large responses, always truncate when scanning:

# Truncate long text fields
curl -s $AUTH "$BASE/traces/<id>" | jq '{id, name, input: (.input | tostring | .[0:300]), output: (.output | tostring | .[0:300])}'

# Select only needed fields
curl -s $AUTH "$BASE/observations?traceId=<id>&limit=50" | jq '.data[] | {id, type, name, model, latency, calculatedTotalCost}'

Important Notes

  • Data freshness: New data appears within 15-30 seconds of ingestion
  • Cost fields: calculatedTotalCost on observations, totalCost on traces
  • Latency: In seconds (e.g., 21.968 = ~22 seconds)
  • Usage: Token counts with unit: "TOKENS", fields: input, output, total
  • Observation types: SPAN (workflow step), GENERATION (LLM call), EVENT (log point)
  • Metadata fields vary by agent/workflow — inspect raw data to discover available keys

References

  • Full API reference: See REFERENCE.md
  • OpenAPI spec: https://cloud.langfuse.com/generated/api/openapi.yml
  • API docs: https://api.reference.langfuse.com
  • Langfuse docs MCP (unauthenticated): https://langfuse.com/api/mcp

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

31.92%
按下载量换算32

Claude

32.11%
按下载量换算32

Cursor

19.04%
按下载量换算19

Gemini CLI

8.42%
按下载量换算9

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

未通过

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills