langfuse-docs: Skill for Claude Code

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:

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, no-code, developer-tools, analytics, clickhouse, 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 and platforms you build with — LangChain, CrewAI, Pydantic AI, Google ADK, Temporal, Semantic Kernel, Inferable, mcp-use, etc.
  • gateways: LLM proxies/routers — Portkey, LiteLLM proxy, TrueFoundry, OpenRouter, Kong AI, etc.
  • no-code: chat UIs, workflow automation, and standalone agents you configure rather than code against — Dify, Flowise, n8n, Zapier, OpenWebUI, Goose, OpenClaw, Hermes, etc.
  • developer-tools: AI coding assistants, editors, and CLIs — Cursor, Claude Code, Codex, Copilot, OpenCode, etc.
  • analytics: tools that visualize Langfuse traces and metrics — Mixpanel, PostHog, Coval, Trubrics.
  • clickhouse: ClickHouse products and the LibreChat + ClickHouse stack.
  • other: anything else — scraping and search (Firecrawl, Exa, Tavily), vector/memory (Milvus, Cognee), OTEL instrumentors (OpenLIT, OpenLLMetry), eval tools (Promptfoo).
• 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.