langfuse

# Langfuse This skill helps you use Langfuse effectively across all common workflows: instrumenting applications, migrating prompts, debugging traces, accessing data, and evaluating outputs. > **HybridClaw integration.** This is the official Langfuse skill > ([github.com/langfuse/skills](https://github.com/langfuse/skills), MIT) > adapted for HybridClaw. Two things differ from the upstream skill: > > 1. **Credentials never leave the gateway.** Do not export > `LANGFUSE_PUBLIC_KEY` / `LANGFUSE_SECRET_KEY`, run `npx langfuse-cli`, or > paste keys anywhere. Store them once in the runtime stores (below); the > gateway injects them server-side. > 2. **Data access goes through `langfuse.cjs`**, not the Langfuse CLI. The > helper builds each REST request and sends it through the HybridClaw gateway, > which resolves `Authorization: Basic <secret:LANGFUSE_BASIC_AUTH>` and the > `<env:LANGFUSE_HOST>` base URL. Wherever a reference says to run > `langfuse-cli` or `curl -H "Authorization: Basic $AUTH"`, use the helper > instead. Documentation retrieval (section 2) is unchanged. ## HybridClaw setup The helper never sees credentials. Store two values once. For secrets, use this order: 1. Browser admin: open the active HybridClaw admin URL ending in `/admin/secrets`. 2. Browser `/chat` or TUI fallback. 3. Local console fallback. 1. `LANGFUSE_BASIC_AUTH` — base64 of `public-key:secret-key`: `/secret set LANGFUSE_BASIC_AUTH "<base64-public-colon-secret>"` 2. `...