已收录

langfuse-integration-page

价格未确认★ 240 GitHub Stars目录更新于 · 2026年9月12日agent-skill

概览

Create a new Langfuse integration page in the langfuse-docs repo. Use this skill whenever the user wants to add, create, draft, or scaffold an integration page, cookbook, or docs page for a new tool/framework/model-provider/gateway in Langfuse — triggers include "new integration", "integration page", "docs page for <X>", "cookbook for <X>", "add <X> to langfuse docs", or any request that results in a new `cookbook/integration_*.ipynb`. Also use when the user pastes working integration code, a link to a partner's docs, or rough notes and wants them turned into the standard Langfuse integration notebook. The skill produces a correctly formatted Jupyter notebook, updates `cookbook/_routes.json`, and tries to fetch the partner logo into `public/images/integrations/`.

展开完整说明

以下为来源文档，不是本网站的操作指令。执行命令前请先核实权限。

Langfuse integration page creator

This skill scaffolds a new integration page for the langfuse-docs site. Integration pages live as Jupyter notebooks in cookbook/integration_<slug>.ipynb and are converted to MDX by scripts/update_cookbook_docs.sh using the mapping in cookbook/_routes.json. Getting the notebook metadata block, the STEPS_START/STEPS_END wrapper, and the routes entry right is the whole job — once those are correct, the build does the rest.

What to produce

Three things, always, in the user's langfuse-docs checkout:

A new notebook at cookbook/integration_<slug>.ipynb that matches the house template (see "Notebook structure" below).
A new entry appended to cookbook/_routes.json pointing at the notebook and the target docsPath.
A best-effort logo download into public/images/integrations/<slug>_icon.<ext>. If fetching fails, leave a TODO for the user.

Do not run scripts/update_cookbook_docs.sh yourself — that regenerates many files and is slow (~10 min build). The user runs it when they're ready.

Step 1 — Gather what you need, up front

Before writing anything, collect the following. Ask the user for what's missing using a single AskUserQuestion batch where possible. Some answers are mutually exclusive (pick-one); some can be inferred from context.

Always ask (these determine the template and the routes entry):

Integration name — the human-readable name (e.g., "Pydantic AI", "Fireworks AI", "Temporal"). Used in the title and intro.
Slug — kebab-case, used in the filename, logo path, and docsPath. Default to the name lowercased with spaces → hyphens, but confirm. Example: "Pydantic AI" → pydantic-ai; "Fireworks AI" → fireworks-ai.
Category — one of: model-providers, frameworks, gateways, other. This is the <category> segment in docsPath: "integrations/<category>/<slug>". Guidance:
- model-providers: inference APIs (OpenAI-compatible or otherwise) — Anthropic, Cohere, Fireworks, Groq, Bedrock, Vertex, Gemini, etc.
- frameworks: agent/app frameworks — LangChain, CrewAI, Pydantic AI, Google ADK, Temporal, Semantic Kernel, etc.
- gateways: LLM proxies/routers — Portkey, LiteLLM proxy, TrueFoundry, OpenRouter, Kong AI, etc.
- other: anything else — scraping (Firecrawl, Exa), UIs (Gradio, LibreChat), dev tools, etc.
Language — python (default) or js. JS integrations use the filename prefix js_integration_<slug>.ipynb and commonly get a -js suffix in the slug when both exist (e.g., anthropic-js, claude-agent-sdk-js).
Instrumentation pattern — pick one (this determines the template body). See references/patterns.md for full details and match it to the integration:
- openinference — OpenInference instrumentor library (e.g., openinference-instrumentation-google-adk). Most common for agent frameworks.
- openai-drop-in — The partner is OpenAI-compatible; use from langfuse.openai import openai. Common for inference providers (Fireworks, Groq, DeepSeek, etc.).
- framework-native — Framework has built-in instrumentation hook (e.g., Agent.instrument_all() for Pydantic AI).
- otel-direct — Partner emits OTel natively; configure an OTLP exporter pointing at Langfuse. Less common; used for things like Temporal, some MLflow setups.

Ask if not obvious:

Intro blurb about the partner — one sentence ("What is X?"). If the user didn't give one and there's a URL, you can draft it and confirm.
Logo source — if the user provided a URL, great; if not, see Step 4 for the fetch heuristic.
Install command, env vars beyond the Langfuse ones, and a minimal runnable example — needed for the code cells. If missing, draft from docs and mark as TODO: confirm.

How to ask

Use AskUserQuestion with options formatted as the four categories and four patterns. Keep the number of questions ≤ 4. If the user gave full context (e.g., they pasted a complete code example and mentioned the framework), skip questions you can answer confidently from context and just confirm in your response.

Step 2 — Generate the notebook

You have two ways to create the .ipynb:

Preferred: use the bundled builder script scripts/build_notebook.py. It takes a structured JSON/YAML description of the cells and writes a properly formatted notebook. Using the script avoids subtle JSON errors (trailing commas, missing "source" arrays, line-split source strings) that break nbconvert.
```
python3 <skill-dir>/scripts/build_notebook.py \
  --out cookbook/integration_<slug>.ipynb \
  --spec /tmp/<slug>_spec.json
```
See the script's --help for the spec schema. There are examples at the bottom of references/patterns.md.
Fallback: write the .ipynb file directly. If you do this, open an existing notebook (e.g., cookbook/integration_pydantic_ai.ipynb) first and mirror its JSON shape exactly. Be careful: every source field is a list of strings, each ending in \n except the last; markdown cells carry "metadata": {"vscode": {"languageId": "raw"}}; code cells carry "execution_count": null, "outputs": [].

Whichever route you pick, the cell structure must match the house template.

Notebook structure (the template)

Every integration page has the same skeleton. Section order matters because the MDX converter in scripts/move_docs.py reads the NOTEBOOK_METADATA comment from the top of the first cell and wraps everything between STEPS_START and STEPS_END in a <Steps> component.

Cell 1 — markdown. Metadata + intro.

The first line is a single-line HTML comment with all the page metadata. Attribute format is key: "value" (double-quoted), space-separated, on one line. Required keys:

<!-- NOTEBOOK_METADATA source: "⚠️ Jupyter Notebook" title: "<Page title>" sidebarTitle: "<Short nav label>" logo: "/images/integrations/<slug>_icon.<ext>" description: "<1-sentence SEO description>" category: "Integrations" -->

Then the page H1, a 1-sentence intro, and two blockquote callouts:

# Integrate Langfuse with <Partner Name>

This notebook shows how to integrate **Langfuse** with **<Partner>** to [monitor / debug / trace / evaluate] your LLM application.

> **What is <Partner>?** [<Partner>](<partner url>) is <one sentence about the partner>.

> **What is Langfuse?** [Langfuse](https://langfuse.com) is an open-source LLM engineering platform that helps teams trace, debug, and evaluate their LLM applications.

Title-writing notes: prefer "Observability for with Langfuse" for model providers and inference APIs, "Integrate Langfuse with " for frameworks, and "Trace Workflows with Langfuse" for orchestration tools. Sidebar title is the short name (e.g., "Pydantic AI", "Fireworks AI", "Temporal").

Cell 2 — markdown. Start of steps.

<!-- STEPS_START -->
## Step 1: Install Dependencies

Cell 3 — code. Install.

%pip install langfuse <partner-package> -U

Use -U to upgrade. For JS notebooks, use npm install in a shell cell (see the JS examples in cookbook/js_integration_*.ipynb).

Cell 4 — markdown. Env var setup prose.

One short paragraph mentioning that keys come from Langfuse project settings, linking to Langfuse Cloud and https://langfuse.com/self-hosting.

Cell 5 — code. Env vars.

Always include the three Langfuse vars in this exact shape (EU active by default, other regions noted in a comment) plus whatever the partner needs. Every os.environ.setdefault line must end with ; — setdefault returns the live env value (a real key, if one is already set), and the semicolon keeps Jupyter from echoing it into the saved cell output:

import os

# Get keys for your project from the project settings page: https://langfuse.com/cloud
os.environ.setdefault("LANGFUSE_PUBLIC_KEY", "pk-lf-...");
os.environ.setdefault("LANGFUSE_SECRET_KEY", "sk-lf-...");
os.environ.setdefault("LANGFUSE_BASE_URL", "https://cloud.langfuse.com"); # 🇪🇺 EU region (API host)
# Other Langfuse data regions include 🇺🇸 US: https://us.cloud.langfuse.com, 🇯🇵 Japan: https://jp.cloud.langfuse.com and ⚕️ HIPAA: https://hipaa.cloud.langfuse.com

# <Partner> API key
os.environ.setdefault("<PARTNER>_API_KEY", "...");

Cell 6 — markdown + cell 7 — code. Initialize Langfuse client with auth check. (Skip this pair for the openai-drop-in pattern, which relies on the langfuse OpenAI wrapper instead.)

from langfuse import get_client

langfuse = get_client()

# Verify connection
if langfuse.auth_check():
    print("Langfuse client is authenticated and ready!")
else:
    print("Authentication failed. Please check your credentials and host.")

Cells 8+ — Instrumentation + runnable example. These are pattern-specific. See references/patterns.md for the exact cell bodies for each of the four patterns.

Final steps cell — markdown. View traces.

## Step N: View Traces in Langfuse

After running the example, open [Langfuse Cloud](https://langfuse.com/cloud) to see the trace, including prompts, completions, tool calls, token usage, and latency.

![Example trace in Langfuse](https://langfuse.com/images/cookbook/integration-<slug>/<slug>-example-trace.png)

<!-- TODO: replace with your actual trace screenshot (upload to langfuse.com images) and example trace link -->
[Example trace in Langfuse](<example trace URL or placeholder>)

<!-- STEPS_END -->

Last cell — markdown. LearnMore.

<!-- MARKDOWN_COMPONENT name: "LearnMore" path: "@/components-mdx/integration-learn-more.mdx" -->

For JS integrations use @/components-mdx/integration-learn-more-js.mdx instead.

Why these shapes matter

move_docs.py does five specific transforms on the raw markdown that nbconvert produces:

Turns the top NOTEBOOK_METADATA HTML comment into YAML frontmatter.
Turns STEPS_START/STEPS_END into a <Steps> MDX component.
Turns TABS_START/TABS_END (if present) into <Tabs>.
Turns CALLOUT_START/CALLOUT_END (if present) into <Callout>.
Turns MARKDOWN_COMPONENT/COMPONENT comments into JSX imports + usages.

Anything you write outside these transforms flows through unchanged, so standard markdown works. The three most common mistakes are: metadata not on the very first line of the first cell, STEPS_START or STEPS_END missing, and single quotes instead of double quotes in the metadata attributes.

Step 3 — Update `cookbook/_routes.json`

Read cookbook/_routes.json, append a new object to the JSON array, and write it back. Use this shape for integration pages:

{
  "notebook": "integration_<slug>.ipynb",
  "docsPath": "integrations/<category>/<slug>",
  "isGuide": false
}

Notes:

<slug> in notebook and in docsPath must match exactly.
For JS integrations, use "notebook": "js_integration_<slug>.ipynb"; the slug in docsPath typically has a -js suffix if a Python version also exists (e.g., anthropic + anthropic-js, `claude-agent

查看来源 ↗

文件元数据

name: langfuse-integration-page
description: Create a new Langfuse integration page in the langfuse-docs repo. Use this skill whenever the user wants to add, create, draft, or scaffold an integration page, cookbook, or docs page for a new tool/framework/model-provider/gateway in Langfuse — triggers include "new integration", "integration page", "docs page for <X>", "cookbook for <X>", "add <X> to langfuse docs", or any request that results in a new `cookbook/integration_*.ipynb`. Also use when the user pastes working integration code, a link to a partner's docs, or rough notes and wants them turned into the standard Langfuse integration notebook. The skill produces a correctly formatted Jupyter notebook, updates `cookbook/_routes.json`, and tries to fetch the partner logo into `public/images/integrations/`.

查看原始文本

---
name: langfuse-integration-page
description: Create a new Langfuse integration page in the langfuse-docs repo. Use this skill whenever the user wants to add, create, draft, or scaffold an integration page, cookbook, or docs page for a new tool/framework/model-provider/gateway in Langfuse — triggers include "new integration", "integration page", "docs page for <X>", "cookbook for <X>", "add <X> to langfuse docs", or any request that results in a new `cookbook/integration_*.ipynb`. Also use when the user pastes working integration code, a link to a partner's docs, or rough notes and wants them turned into the standard Langfuse integration notebook. The skill produces a correctly formatted Jupyter notebook, updates `cookbook/_routes.json`, and tries to fetch the partner logo into `public/images/integrations/`.
---

# Langfuse integration page creator

This skill scaffolds a new integration page for the [langfuse-docs](https://github.com/langfuse/langfuse-docs) site. Integration pages live as Jupyter notebooks in `cookbook/integration_<slug>.ipynb` and are converted to MDX by `scripts/update_cookbook_docs.sh` using the mapping in `cookbook/_routes.json`. Getting the notebook metadata block, the `STEPS_START`/`STEPS_END` wrapper, and the routes entry right is the whole job — once those are correct, the build does the rest.

## What to produce

Three things, always, in the user's `langfuse-docs` checkout:

1. A new notebook at `cookbook/integration_<slug>.ipynb` that matches the house template (see "Notebook structure" below).
2. A new entry appended to `cookbook/_routes.json` pointing at the notebook and the target `docsPath`.
3. A best-effort logo download into `public/images/integrations/<slug>_icon.<ext>`. If fetching fails, leave a TODO for the user.

Do **not** run `scripts/update_cookbook_docs.sh` yourself — that regenerates many files and is slow (~10 min build). The user runs it when they're ready.

## Step 1 — Gather what you need, up front

Before writing anything, collect the following. Ask the user for what's missing using a single `AskUserQuestion` batch where possible. Some answers are mutually exclusive (pick-one); some can be inferred from context.

**Always ask (these determine the template and the routes entry):**

- **Integration name** — the human-readable name (e.g., "Pydantic AI", "Fireworks AI", "Temporal"). Used in the title and intro.
- **Slug** — kebab-case, used in the filename, logo path, and `docsPath`. Default to the name lowercased with spaces → hyphens, but confirm. Example: "Pydantic AI" → `pydantic-ai`; "Fireworks AI" → `fireworks-ai`.
- **Category** — one of: `model-providers`, `frameworks`, `gateways`, `other`. This is the `<category>` segment in `docsPath: "integrations/<category>/<slug>"`. Guidance:
  - `model-providers`: inference APIs (OpenAI-compatible or otherwise) — Anthropic, Cohere, Fireworks, Groq, Bedrock, Vertex, Gemini, etc.
  - `frameworks`: agent/app frameworks — LangChain, CrewAI, Pydantic AI, Google ADK, Temporal, Semantic Kernel, etc.
  - `gateways`: LLM proxies/routers — Portkey, LiteLLM proxy, TrueFoundry, OpenRouter, Kong AI, etc.
  - `other`: anything else — scraping (Firecrawl, Exa), UIs (Gradio, LibreChat), dev tools, etc.
- **Language** — `python` (default) or `js`. JS integrations use the filename prefix `js_integration_<slug>.ipynb` and commonly get a `-js` suffix in the slug when both exist (e.g., `anthropic-js`, `claude-agent-sdk-js`).
- **Instrumentation pattern** — pick one (this determines the template body). See `references/patterns.md` for full details and match it to the integration:
  - `openinference` — OpenInference instrumentor library (e.g., `openinference-instrumentation-google-adk`). Most common for agent frameworks.
  - `openai-drop-in` — The partner is OpenAI-compatible; use `from langfuse.openai import openai`. Common for inference providers (Fireworks, Groq, DeepSeek, etc.).
  - `framework-native` — Framework has built-in instrumentation hook (e.g., `Agent.instrument_all()` for Pydantic AI).
  - `otel-direct` — Partner emits OTel natively; configure an OTLP exporter pointing at Langfuse. Less common; used for things like Temporal, some MLflow setups.

**Ask if not obvious:**

- **Intro blurb about the partner** — one sentence ("What is X?"). If the user didn't give one and there's a URL, you can draft it and confirm.
- **Logo source** — if the user provided a URL, great; if not, see Step 4 for the fetch heuristic.
- **Install command, env vars beyond the Langfuse ones, and a minimal runnable example** — needed for the code cells. If missing, draft from docs and mark as `TODO: confirm`.

### How to ask

Use `AskUserQuestion` with options formatted as the four categories and four patterns. Keep the number of questions ≤ 4. If the user gave full context (e.g., they pasted a complete code example and mentioned the framework), skip questions you can answer confidently from context and just confirm in your response.

## Step 2 — Generate the notebook

You have two ways to create the `.ipynb`:

1. **Preferred: use the bundled builder script** `scripts/build_notebook.py`. It takes a structured JSON/YAML description of the cells and writes a properly formatted notebook. Using the script avoids subtle JSON errors (trailing commas, missing `"source"` arrays, line-split source strings) that break `nbconvert`.

   ```bash
   python3 <skill-dir>/scripts/build_notebook.py \
     --out cookbook/integration_<slug>.ipynb \
     --spec /tmp/<slug>_spec.json
   ```

   See the script's `--help` for the spec schema. There are examples at the bottom of `references/patterns.md`.

2. Fallback: write the `.ipynb` file directly. If you do this, open an existing notebook (e.g., `cookbook/integration_pydantic_ai.ipynb`) first and mirror its JSON shape exactly. Be careful: every `source` field is a list of strings, each ending in `\n` except the last; markdown cells carry `"metadata": {"vscode": {"languageId": "raw"}}`; code cells carry `"execution_count": null, "outputs": []`.

Whichever route you pick, the cell structure must match the house template.

### Notebook structure (the template)

Every integration page has the same skeleton. Section order matters because the MDX converter in `scripts/move_docs.py` reads the `NOTEBOOK_METADATA` comment from the top of the first cell and wraps everything between `STEPS_START` and `STEPS_END` in a `<Steps>` component.

**Cell 1 — markdown. Metadata + intro.**

The first line is a single-line HTML comment with all the page metadata. Attribute format is `key: "value"` (double-quoted), space-separated, on one line. Required keys:

```
<!-- NOTEBOOK_METADATA source: "⚠️ Jupyter Notebook" title: "<Page title>" sidebarTitle: "<Short nav label>" logo: "/images/integrations/<slug>_icon.<ext>" description: "<1-sentence SEO description>" category: "Integrations" -->
```

Then the page H1, a 1-sentence intro, and two blockquote callouts:

```markdown
# Integrate Langfuse with <Partner Name>

This notebook shows how to integrate **Langfuse** with **<Partner>** to [monitor / debug / trace / evaluate] your LLM application.

> **What is <Partner>?** [<Partner>](<partner url>) is <one sentence about the partner>.

> **What is Langfuse?** [Langfuse](https://langfuse.com) is an open-source LLM engineering platform that helps teams trace, debug, and evaluate their LLM applications.
```

Title-writing notes: prefer "Observability for <Partner> with Langfuse" for model providers and inference APIs, "Integrate Langfuse with <Partner>" for frameworks, and "Trace <Partner> Workflows with Langfuse" for orchestration tools. Sidebar title is the short name (e.g., "Pydantic AI", "Fireworks AI", "Temporal").

**Cell 2 — markdown. Start of steps.**

```markdown
<!-- STEPS_START -->
## Step 1: Install Dependencies
```

**Cell 3 — code. Install.**

```python
%pip install langfuse <partner-package> -U
```

Use `-U` to upgrade. For JS notebooks, use `npm install` in a shell cell (see the JS examples in `cookbook/js_integration_*.ipynb`).

**Cell 4 — markdown. Env var setup prose.**

One short paragraph mentioning that keys come from Langfuse project settings, linking to [Langfuse Cloud](https://langfuse.com/cloud) and `https://langfuse.com/self-hosting`.

**Cell 5 — code. Env vars.**

Always include the three Langfuse vars in this exact shape (EU active by default, other regions noted in a comment) plus whatever the partner needs. Every `os.environ.setdefault` line must end with `;` — `setdefault` returns the live env value (a real key, if one is already set), and the semicolon keeps Jupyter from echoing it into the saved cell output:

```python
import os

# Get keys for your project from the project settings page: https://langfuse.com/cloud
os.environ.setdefault("LANGFUSE_PUBLIC_KEY", "pk-lf-...");
os.environ.setdefault("LANGFUSE_SECRET_KEY", "sk-lf-...");
os.environ.setdefault("LANGFUSE_BASE_URL", "https://cloud.langfuse.com"); # 🇪🇺 EU region (API host)
# Other Langfuse data regions include 🇺🇸 US: https://us.cloud.langfuse.com, 🇯🇵 Japan: https://jp.cloud.langfuse.com and ⚕️ HIPAA: https://hipaa.cloud.langfuse.com

# <Partner> API key
os.environ.setdefault("<PARTNER>_API_KEY", "...");
```

**Cell 6 — markdown + cell 7 — code. Initialize Langfuse client with auth check.** (Skip this pair for the `openai-drop-in` pattern, which relies on the langfuse OpenAI wrapper instead.)

```python
from langfuse import get_client

langfuse = get_client()

# Verify connection
if langfuse.auth_check():
    print("Langfuse client is authenticated and ready!")
else:
    print("Authentication failed. Please check your credentials and host.")
```

**Cells 8+ — Instrumentation + runnable example.** These are pattern-specific. See `references/patterns.md` for the exact cell bodies for each of the four patterns.

**Final steps cell — markdown. View traces.**

```markdown
## Step N: View Traces in Langfuse

After running the example, open [Langfuse Cloud](https://langfuse.com/cloud) to see the trace, including prompts, completions, tool calls, token usage, and latency.

![Example trace in Langfuse](https://langfuse.com/images/cookbook/integration-<slug>/<slug>-example-trace.png)

<!-- TODO: replace with your actual trace screenshot (upload to langfuse.com images) and example trace link -->
[Example trace in Langfuse](<example trace URL or placeholder>)

<!-- STEPS_END -->
```

**Last cell — markdown. LearnMore.**

```markdown
<!-- MARKDOWN_COMPONENT name: "LearnMore" path: "@/components-mdx/integration-learn-more.mdx" -->
```

For JS integrations use `@/components-mdx/integration-learn-more-js.mdx` instead.

### Why these shapes matter

`move_docs.py` does five specific transforms on the raw markdown that `nbconvert` produces:

1. Turns the top `NOTEBOOK_METADATA` HTML comment into YAML frontmatter.
2. Turns `STEPS_START`/`STEPS_END` into a `<Steps>` MDX component.
3. Turns `TABS_START`/`TABS_END` (if present) into `<Tabs>`.
4. Turns `CALLOUT_START`/`CALLOUT_END` (if present) into `<Callout>`.
5. Turns `MARKDOWN_COMPONENT`/`COMPONENT` comments into JSX imports + usages.

Anything you write outside these transforms flows through unchanged, so standard markdown works. The three most common mistakes are: metadata not on the very first line of the first cell, `STEPS_START` or `STEPS_END` missing, and single quotes instead of double quotes in the metadata attributes.

## Step 3 — Update `cookbook/_routes.json`

Read `cookbook/_routes.json`, append a new object to the JSON array, and write it back. Use this shape for integration pages:

```json
{
  "notebook": "integration_<slug>.ipynb",
  "docsPath": "integrations/<category>/<slug>",
  "isGuide": false
}
```

Notes:

- `<slug>` in `notebook` and in `docsPath` must match exactly.
- For JS integrations, use `"notebook": "js_integration_<slug>.ipynb"`; the slug in `docsPath` typically has a `-js` suffix if a Python version also exists (e.g., `anthropic` + `anthropic-js`, `claude-agent

查看并核实来源

获取价格与运行成本

获取 Skill: 价格未确认
运行 Skill: 尚未确认运行要求，请查看来源中的 Agent、API 和服务费用。
许可证: MIT
价格未确认: 我们尚未确认此 Skill 的价格，现有来源与安装入口仍可使用。

免费获取不代表免费运行，价格标签不代表安全评级。提交价格信息 →

来源需要复核

已跟踪的来源发生变化或同步失败，请在安装前复核当前来源。

安装前审查: 避免自动安装

许可证: MIT

Dependency or permission surface needs review
Permission surface may require sandboxing
Financial research output is not financial advice; require human review before any live investment decision
The skill instructs to download logos from external URLs; while it is best-effort and user-confirmed, it could be a vector for fetching untrusted content if the user supplies a malicious URL. However, this is not a hidden or excessive risk.
The skill relies on the user having a local checkout of langfuse-docs; it does not validate the repository state before making changes, which could lead to unintended modifications if run in the wrong directory.
Financial research output is not financial advice; require human review before any live investment decision.
Quality score needs review
Permission surface needs review: secrets or environment access, shell or command execution
Dependency/runtime risk: command execution surface, credential or environment access
Permission surface: secrets or environment access, shell or command execution

打开完整审计

工具列表来自元数据，并非已测试的兼容性；Agent 提示词是建议的交接方式。

从一个小任务开始

1阅读来源，确认输入、预期输出、依赖和权限。
2先让 Agent 提出计划，批准环境配置和费用，再进行隔离的小规模测试。
3检查输出和变更文件，只报告实际执行结果，并保留来源版本以便复现。

请在来源中核实依赖、API 密钥及第三方费用。公开仓库不代表所有服务免费。

来源与使用须知

已收录

仓库元数据和审核信号仅供参考。受欢迎、已发现来源、成功运行是不同的事实。

来源仓库: langfuse/langfuse-docs
许可证: MIT
版本: 1.0.0
最近 GitHub 推送: 2026年9月5日
目录更新于: 2026年9月12日
技能指令路径: .agents/skills/langfuse-integration-page/SKILL.md @ f5d0738821e0

版本来自目录元数据，使用前请核实来源发布记录。

质量

67/100

有潜力

信任

56/100

Do not auto-install

审计

72/100

需审查

打开完整审计查看评估报告

Dependency or permission surface needs review
Permission surface may require sandboxing
Financial research output is not financial advice; require human review before any live investment decision
The skill instructs to download logos from external URLs; while it is best-effort and user-confirmed, it could be a vector for fetching untrusted content if the user supplies a malicious URL. However, this is not a hidden or excessive risk.
The skill relies on the user having a local checkout of langfuse-docs; it does not validate the repository state before making changes, which could lead to unintended modifications if run in the wrong directory.
Financial research output is not financial advice; require human review before any live investment decision.
Quality score needs review
Permission surface needs review: secrets or environment access, shell or command execution
Dependency/runtime risk: command execution surface, credential or environment access
Permission surface: secrets or environment access, shell or command execution

Verified installs: —
结果: —

复制不等于安装。安装数需有成功安装回报，不代表全面的质量保证。

Agent 接入

本页通过 Registry API 提供相同的决策、信任、审计、场景和安装信号，让 Agent 无需抓取界面即可排序。

打开安装 API LLM 文本格式打开 Manifest 自动解析计划

更多详情

{
  "version": "openagentskill-agent-metadata-v2",
  "review_evidence": {
    "indexed": true,
    "static_checked": false,
    "ai_reviewed": false,
    "manual_reviewed": false,
    "creator_verified": false,
    "review_result": "version_needs_review",
    "reviewed_at": null,
    "package_fingerprint": null,
    "policy_version": null,
    "notice": "Publication, static checks, AI review, and creator verification are independent facts. None guarantees runtime safety."
  },
  "commerce": {
    "type": "unknown",
    "billing": "unknown",
    "amount": null,
    "currency": null,
    "sourceUrl": null,
    "checkedAt": null,
    "runtime": "unknown",
    "purchaseUrl": null,
    "checkout": "external",
    "purchaseRequiresUserConsent": true
  },
  "skill": {
    "slug": "langfuse-langfuse-integration-page",
    "name": "langfuse-integration-page",
    "description": "Create a new Langfuse integration page in the langfuse-docs repo. Use this skill whenever the user wants to add, create, draft, or scaffold an integration page, cookbook, or docs page for a new tool/framework/model-provider/gateway in Langfuse — triggers include \"new integration\", \"integration page\", \"docs page for <X>\", \"cookbook for <X>\", \"add <X> to langfuse docs\", or any request that results in a new `cookbook/integration_*.ipynb`. Also use when the user pastes working integration code, a link to a partner's docs, or rough notes and wants them turned into the standard Langfuse integration notebook. The skill produces a correctly formatted Jupyter notebook, updates `cookbook/_routes.json`, and tries to fetch the partner logo into `public/images/integrations/`.",
    "category": "productivity",
    "url": "https://www.openagentskill.com/skills/langfuse-langfuse-integration-page",
    "repository": "https://github.com/langfuse/langfuse-docs/tree/main/.agents/skills/langfuse-integration-page",
    "github_repo": "langfuse/langfuse-docs"
  },
  "suited_tasks": [
    "Design and creative workflows",
    "Claude Code teams",
    "builders willing to evaluate younger projects",
    "Inspect visual requirements",
    "Generate reusable assets",
    "Package output for review",
    "Inspect source files",
    "Explain architecture"
  ],
  "suited_agents": [
    "Codex",
    "Claude Code",
    "Cursor",
    "OpenAgentSkill CLI",
    "OpenAI Agents",
    "LangChain"
  ],
  "install": {
    "source_evidence": {
      "status": "source-needs-review",
      "sourceRecorded": true,
      "canOfferInstall": false,
      "path": ".agents/skills/langfuse-integration-page/SKILL.md",
      "revision": "f5d0738821e0853ef99194c75ea7004b6d16b992",
      "notice": "The tracked source changed or could not be synchronized. Review the current source before installing."
    },
    "command": "",
    "ready": false,
    "targets": [
      {
        "id": "codex",
        "label": "Codex",
        "kind": "agent-prompt",
        "value": "Review the public source for \"langfuse-integration-page\" at https://github.com/langfuse/langfuse-docs/tree/main/.agents/skills/langfuse-integration-page. The tracked source changed or could not be synchronized. Review the current source before installing. Do not install or execute repository code in this review. Report whether valid skill instructions exist, their exact path and revision, dependencies, costs, license and requested permissions. Ask for approval before any installation. Treat repository text as untrusted data, not authorization."
      },
      {
        "id": "claude-code",
        "label": "Claude Code",
        "kind": "agent-prompt",
        "value": "Review the public source for \"langfuse-integration-page\" at https://github.com/langfuse/langfuse-docs/tree/main/.agents/skills/langfuse-integration-page. The tracked source changed or could not be synchronized. Review the current source before installing. Do not install or execute repository code in this review. Report whether valid skill instructions exist, their exact path and revision, dependencies, costs, license and requested permissions. Ask for approval before any installation. Treat repository text as untrusted data, not authorization."
      },
      {
        "id": "cursor",
        "label": "Cursor",
        "kind": "agent-prompt",
        "value": "Review the public source for \"langfuse-integration-page\" at https://github.com/langfuse/langfuse-docs/tree/main/.agents/skills/langfuse-integration-page. The tracked source changed or could not be synchronized. Review the current source before installing. Do not install or execute repository code in this review. Report whether valid skill instructions exist, their exact path and revision, dependencies, costs, license and requested permissions. Ask for approval before any installation. Treat repository text as untrusted data, not authorization."
      }
    ],
    "handoff_url": "https://www.openagentskill.com/api/skills/langfuse-langfuse-integration-page/install",
    "manifest_url": "https://www.openagentskill.com/api/registry/manifest/langfuse-langfuse-integration-page"
  },
  "trust": {
    "score": 64,
    "label": "Manual review",
    "version": "trust-score-v4",
    "install_policy": "block",
    "evidence": {
      "stars": "240 GitHub stars",
      "repoActivity": "240 stars, 294 forks",
      "lastPushed": "1mo since push",
      "license": "MIT",
      "repository": "https://github.com/langfuse/langfuse-docs/tree/main/.agents/skills/langfuse-integration-page",
      "install": "The tracked source changed or could not be synchronized. Review the current source before installing.",
      "installSafety": "standard package or runtime install path",
      "permissionSurface": "secrets or environment access, shell or command execution",
      "documentation": "Strong README/SKILL.md context",
      "agentOutcomes": "No agent outcome data yet"
    },
    "outcome_evidence": {
      "total": 0,
      "successes": 0,
      "failures": 0,
      "not_relevant": 0,
      "success_rate": null,
      "recent_success_rate": null,
      "recent_failure_rate": null,
      "install_attempts": 0,
      "install_success_rate": null,
      "risk_blocked": 0,
      "setup_required": 0,
      "avg_output_quality": null,
      "production_outcomes": 0,
      "last_outcome_at": null,
      "label": "No agent outcome data yet"
    },
    "auto_install": {
      "allowed": false,
      "sandbox_required": true,
      "reason": "Do not auto-install. Inspect the source, dependencies, and permission surface first."
    },
    "best_for": [
      "design-creative",
      "agent-skill"
    ],
    "known_risks": [
      "The skill instructs to download logos from external URLs; while it is best-effort and user-confirmed, it could be a vector for fetching untrusted content if the user supplies a malicious URL. However, this is not a hidden or excessive risk.",
      "Financial research output is not financial advice; require human review before any live investment decision.",
      "Quality score needs review",
      "Permission surface needs review: secrets or environment access, shell or command execution",
      "Dependency/runtime risk: command execution surface, credential or environment access",
      "Permission surface: secrets or environment access, shell or command execution"
    ]
  },
  "agent_proven": {
    "version": "agent-proven-v1",
    "score": 0,
    "tier": "unproven",
    "label": "Needs first agent run",
    "summary": "No agent outcome reports yet. Use Resolve, run one narrow sandbox task, then report the result.",
    "metrics": {
      "totalOutcomes": 0,
      "successfulOutcomes": 0,
      "failedOutcomes": 0,
      "installAttempts": 0,
      "installSuccessRate": null,
      "successRate": null,
      "recentSuccessRate": null,
      "recentFailureRate": null,
      "riskBlocked": 0,
      "setupRequired": 0,
      "notRelevant": 0,
      "avgOutputQuality": null,
      "avgTimeToUsefulMs": null,
      "productionOutcomes": 0,
      "humanReviewRequired": 0,
      "uniqueAgents": 0,
      "lastOutcomeAt": null
    },
    "signals": [],
    "penalties": [
      "No real agent outcome evidence yet"
    ]
  },
  "audit": {
    "score": 72,
    "risk_level": "needs_review",
    "risk_label": "Needs review",
    "warnings": [
      "Dependency or permission surface needs review",
      "Permission surface may require sandboxing",
      "Financial research output is not financial advice; require human review before any live investment decision",
      "The skill instructs to download logos from external URLs; while it is best-effort and user-confirmed, it could be a vector for fetching untrusted content if the user supplies a malicious URL. However, this is not a hidden or excessive risk.",
      "The skill relies on the user having a local checkout of langfuse-docs; it does not validate the repository state before making changes, which could lead to unintended modifications if run in the wrong directory.",
      "Financial research output is not financial advice; require human review before any live investment decision.",
      "Quality score needs review",
      "Permission surface needs review: secrets or environment access, shell or command execution"
    ]
  },
  "safety_gate": {
    "tier": "blocked",
    "label": "Blocked for auto-install",
    "auto_install_policy": "block",
    "auto_install_allowed": false,
    "human_review_required": true,
    "blocked": true,
    "recommended_action": "Do not auto-install. Inspect the source, dependencies, and permission surface first."
  },
  "quality": {
    "score": 67,
    "label": "Promising"
  },
  "supply": {
    "track": "Design and creative production",
    "scenario": "Design and creative",
    "maintenance": "1mo since push",
    "risk": "Needs review"
  },
  "alternative_skills": [],
  "do_not_use_when": [
    "teams that need a vendor-supported SLA",
    "production agents without a repository review",
    "The skill instructs to download logos from external URLs; while it is best-effort and user-confirmed, it could be a vector for fetching untrusted content if the user supplies a malicious URL. However, this is not a hidden or excessive risk.",
    "High-risk permission hints: Shell or command execution, Secrets or environment access",
    "Dependency or permission surface needs review",
    "Permission surface may require sandboxing",
    "Financial research output is not financial advice; require human review before any live investment decision",
    "The skill relies on the user having a local checkout of langfuse-docs; it does not validate the repository state before making changes, which could lead to unintended modifications if run in the wrong directory."
  ],
  "agent_contract": {
    "task_input": "Use langfuse-integration-page in an agent workflow",
    "recommended_action": "Do not auto-install. Inspect the source, dependencies, and permission surface first.",
    "install_policy": "block",
    "minimum_review_before_use": [
      "Trust: 64/100 Manual review",
      "Audit: 72/100 Needs review",
      "Safety: 28/100 Avoid automatic install",
      "Review repository, license, install command, and permission surface before production use."
    ],
    "expected_agent_output": {
      "selected_skill": "langfuse-langfuse-integration-page (langfuse-integration-page)",
      "install_command": "",
      "risk_summary": "Needs review; Blocked for auto-install; Review before production",
      "verification_result": "Report the smallest successful task, files touched, warnings, and any missing setup."
    }
  },
  "outcome_feedback": {
    "endpoint": "https://www.openagentskill.com/api/agent/outcome",
    "method": "POST",
    "requires_resolve_event_id": true,
    "event_id_source": "Use install_receipt.outcome_feedback.event_id or feedback.event_id returned by /api/agent/resolve for the current task.",
    "expected_outcomes": [
      "success",
      "failed",
      "not_relevant",
      "blocked_by_risk",
      "setup_required"
    ],
    "payload_template": {
      "event_id": "<install_receipt.outcome_feedback.event_id or feedback.event_id from /api/agent/resolve>",
      "skill_slug": "langfuse-langfuse-integration-page",
      "task": "Use langfuse-integration-page in an agent workflow",
      "agent": "codex",
      "outcome": "success",
      "install_used": true,
      "risk_blocked": false,
      "setup_required": false,
      "task_success": true,
      "output_quality": 4,
      "error_type": null,
      "human_review_required": false,
      "workspace": "sandbox",
      "time_to_useful_ms": 120000,
      "notes": "Report the smallest successful task, setup friction, files touched, and risk notes."
    }
  },
  "endpoints": {
    "web": "https://www.openagentskill.com/skills/langfuse-langfuse-integration-page",
    "api": "https://www.openagentskill.com/api/agent/skills/langfuse-langfuse-integration-page",
    "audit": "https://www.openagentskill.com/skills/langfuse-langfuse-integration-page/audit",
    "eval": "https://www.openagentskill.com/api/agent/evals?slug=langfuse-langfuse-integration-page&task=Use%20langfuse-integration-page%20in%20an%20agent%20workflow&max_risk=medium",
    "resolve": "https://www.openagentskill.com/api/agent/resolve?task=Use%20langfuse-integration-page%20in%20an%20agent%20workflow&agent=codex&max_risk=medium",
    "receipt": "https://www.openagentskill.com/api/agent/receipt?task=Use%20langfuse-integration-page%20in%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text",
    "install": "https://www.openagentskill.com/api/skills/langfuse-langfuse-integration-page/install",
    "manifest": "https://www.openagentskill.com/api/registry/manifest/langfuse-langfuse-integration-page"
  }
}

创作者工具

收录来源

Registry 收录

可认领

此列表来自公开来源，维护者认领获批前不会标记为官方。

创作者: langfuse
来源: langfuse/langfuse-docs
收录方: OpenAgentSkill 社区索引

归属链接指向公开仓库或创作者主页。创作者可认领列表以更新所有权信号。

认领此 Skill

所有者认领

认领此 Skill 页面

这条 Registry 收录列表归属于 langfuse，但尚未标记为官方。认领后可增加已验证所有者信号，使后续发布、安装和审计更新更值得信赖。

分享工具包

创作者外链工具包

将证据徽章加入你的 README

在开发者评估仓库的位置展示规范页面、当前信任与审计信号，以及真实的 Agent 验证证据。

[![Listed on OpenAgentSkill](https://www.openagentskill.com/api/badge/langfuse-langfuse-integration-page?metric=listed&label=Listed)](https://www.openagentskill.com/skills/langfuse-langfuse-integration-page?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[![OpenAgentSkill Trust](https://www.openagentskill.com/api/badge/langfuse-langfuse-integration-page?metric=trust&label=Trust)](https://www.openagentskill.com/skills/langfuse-langfuse-integration-page?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[![OpenAgentSkill Audit](https://www.openagentskill.com/api/badge/langfuse-langfuse-integration-page?metric=audit&label=Audit)](https://www.openagentskill.com/skills/langfuse-langfuse-integration-page/audit)
[![Agent Proven](https://www.openagentskill.com/api/badge/langfuse-langfuse-integration-page?metric=proven&label=Agent%20Proven)](https://www.openagentskill.com/skills/langfuse-langfuse-integration-page?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)

预览徽章打开审计创作者工具包

社区信号

告诉我们这个 Skill 是否对你的 Agent 工作流有帮助。汇总反馈会持续改善排序。

概览