Langfuse Previews
langfuse/langfuse
Use Langfuse's disposable per-PR previews at pr-N.preview.langfuse.com (synthetic data only).
Configure Langfuse across development, staging, and production environments.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill langfuse-multi-env-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace langfuse-multi-env-setup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/langfuse-multi-env-setup .claude/skills/langfuse-multi-env-setup && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "langfuse-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/langfuse-multi-env-setup into .claude/skills/langfuse-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "langfuse-multi-env-setup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/langfuse-multi-env-setupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill langfuse-multi-env-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace langfuse-multi-env-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/langfuse-multi-env-setup .agents/skills/langfuse-multi-env-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "langfuse-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/langfuse-multi-env-setup into .agents/skills/langfuse-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "langfuse-multi-env-setup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill langfuse-multi-env-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace langfuse-multi-env-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/langfuse-multi-env-setup .cursor/skills/langfuse-multi-env-setup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "langfuse-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/langfuse-multi-env-setup into .cursor/skills/langfuse-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "langfuse-multi-env-setup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/langfuse-multi-env-setup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill langfuse-multi-env-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace langfuse-multi-env-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/langfuse-multi-env-setup .gemini/skills/langfuse-multi-env-setup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "langfuse-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/langfuse-multi-env-setup into .gemini/skills/langfuse-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "langfuse-multi-env-setup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace langfuse-multi-env-setupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill langfuse-multi-env-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/langfuse-multi-env-setup .github/skills/langfuse-multi-env-setup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "langfuse-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/langfuse-multi-env-setup into .github/skills/langfuse-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "langfuse-multi-env-setup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill langfuse-multi-env-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace langfuse-multi-env-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/langfuse-multi-env-setup .opencode/skills/langfuse-multi-env-setup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "langfuse-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/langfuse-multi-env-setup into .opencode/skills/langfuse-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "langfuse-multi-env-setup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
langfuse-multi-env-setupConfigure Langfuse across development, staging, and production environments.
Langfuse Multi Env Setup is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure Langfuse across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment keys, or implementing environment-specific Langfuse configurations. Trigger with phrases like "langfuse environments", "langfuse staging", "langfuse dev prod", "langfuse environment setup", "langfuse config by env".
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Designed for Claude Code
It sits in AI & LLM Engineering, covering LLM observability and Deployment. It works with Langfuse and Zod. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 80f86df. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBash(aws:*)Bash(gcloud:*)Bash(vault:*)From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
awsgcloudFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
cloud.langfuse.comAlso links to:
langfuse.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
LANGFUSE_PUBLIC_KEYLANGFUSE_SECRET_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Langfuse Multi Env Setup loads about 2k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 292 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
| Development | `.env.local` | Dev project | Debug on, flush immediately, 100% sampling |# .env.local (development -- git-ignored)# .env.staging (used by CI/CD)# .env.production (used by CI/CD).env.env.local.env.*.local| Leaked keys in git | `.env` in `.gitignore`, secret scanning in CI |Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 292 words, ~1,989 tokens.
.claude/skills/langfuse-multi-env-setup/SKILL.md (or your agent's skills folder).Configure Langfuse across dev/staging/production with isolated API keys, environment-specific SDK settings, secret management, and CI/CD integration to prevent cross-environment data leakage.
| Environment | API Key Source | Langfuse Project | Settings |
|---|---|---|---|
| Development | .env.local | Dev project | Debug on, flush immediately, 100% sampling |
| Staging | CI/CD secrets | Staging project | Prod-like settings, 50% sampling |
| Production | Secret manager | Prod project | Optimized batching, 10% sampling |
// src/config/langfuse.ts
import { LangfuseSpanProcessor } from "@langfuse/otel";
import { NodeSDK } from "@opentelemetry/sdk-node";
import { LangfuseClient } from "@langfuse/client";
type Env = "development" | "staging" | "production";
interface LangfuseEnvConfig {
exportIntervalMillis: number;
maxExportBatchSize: number;
debug: boolean;
sampleRate: number;
}
const ENV_CONFIGS: Record<Env, LangfuseEnvConfig> = {
development: {
exportIntervalMillis: 1000,
maxExportBatchSize: 1,
debug: true,
sampleRate: 1.0,
},
staging: {
exportIntervalMillis: 5000,
maxExportBatchSize: 25,
debug: false,
sampleRate: 0.5,
},
production: {
exportIntervalMillis: 10000,
maxExportBatchSize: 50,
debug: false,
sampleRate: 0.1,
},
};
function detectEnvironment(): Env {
const env = process.env.NODE_ENV || "development";
if (env === "production") return "production";
if (env === "staging" || process.env.VERCEL_ENV === "preview") return "staging";
return "development";
}
export function initLangfuse() {
const env = detectEnvironment();
const config = ENV_CONFIGS[env];
// Validate credentials
const required = ["LANGFUSE_PUBLIC_KEY", "LANGFUSE_SECRET_KEY"];
for (const key of required) {
if (!process.env[key]) {
throw new Error(`${key} not set for environment: ${env}`);
}
}
// Initialize OTel with env-specific settings
const processor = new LangfuseSpanProcessor({
exportIntervalMillis: config.exportIntervalMillis,
maxExportBatchSize: config.maxExportBatchSize,
});
const sdk = new NodeSDK({ spanProcessors: [processor] });
sdk.start();
// Client for prompts, datasets, scores
const client = new LangfuseClient();
console.log(`Langfuse initialized [${env}] (sample: ${config.sampleRate * 100}%)`);
return { sdk, client, env, config };
}# .env.local (development -- git-ignored)
LANGFUSE_PUBLIC_KEY=pk-lf-dev-...
LANGFUSE_SECRET_KEY=sk-lf-dev-...
LANGFUSE_BASE_URL=https://cloud.langfuse.com
NODE_ENV=development
# .env.staging (used by CI/CD)
LANGFUSE_BASE_URL=https://cloud.langfuse.com
NODE_ENV=staging
# Keys injected via CI secrets
# .env.production (used by CI/CD)
LANGFUSE_BASE_URL=https://cloud.langfuse.com
NODE_ENV=production
# Keys injected via secret manager# .gitignore
.env
.env.local
.env.*.localset -euo pipefail
# GitHub Actions: Add per-environment secrets
# Settings > Environments > staging > Secrets
# Settings > Environments > production > Secrets
# AWS Secrets Manager
aws secretsmanager create-secret \
--name "langfuse/production/public-key" \
--secret-string "pk-lf-prod-..."
aws secretsmanager create-secret \
--name "langfuse/production/secret-key" \
--secret-string "sk-lf-prod-..."
# GCP Secret Manager
echo -n "pk-lf-prod-..." | gcloud secrets create langfuse-public-key-prod --data-file=-
echo -n "sk-lf-prod-..." | gcloud secrets create langfuse-secret-key-prod --data-file=-# .github/workflows/deploy.yml
name: Deploy
on:
push:
branches: [main, staging]
jobs:
deploy-staging:
if: github.ref == 'refs/heads/staging'
runs-on: ubuntu-latest
environment: staging
env:
LANGFUSE_PUBLIC_KEY: ${{ secrets.LANGFUSE_PUBLIC_KEY }}
LANGFUSE_SECRET_KEY: ${{ secrets.LANGFUSE_SECRET_KEY }}
LANGFUSE_BASE_URL: https://cloud.langfuse.com
NODE_ENV: staging
steps:
- uses: actions/checkout@v4
- run: npm ci && npm run build && npm run deploy:staging
deploy-production:
if: github.ref == 'refs/heads/main'
runs-on: ubuntu-latest
environment: production
env:
LANGFUSE_PUBLIC_KEY: ${{ secrets.LANGFUSE_PUBLIC_KEY }}
LANGFUSE_SECRET_KEY: ${{ secrets.LANGFUSE_SECRET_KEY }}
LANGFUSE_BASE_URL: https://cloud.langfuse.com
NODE_ENV: production
steps:
- uses: actions/checkout@v4
- run: npm ci && npm run build && npm run deploy:productionimport { z } from "zod";
const langfuseConfigSchema = z.object({
LANGFUSE_PUBLIC_KEY: z.string().startsWith("pk-lf-", "Must start with pk-lf-"),
LANGFUSE_SECRET_KEY: z.string().startsWith("sk-lf-", "Must start with sk-lf-"),
LANGFUSE_BASE_URL: z.string().url().optional(),
NODE_ENV: z.enum(["development", "staging", "production"]).default("development"),
});
// Validate at startup -- fail fast on misconfiguration
const config = langfuseConfigSchema.parse(process.env);
console.log(`Langfuse config validated for ${config.NODE_ENV}`);| Risk | Mitigation |
|---|---|
| Dev traces in prod project | Separate API keys per environment |
| Prod keys in dev env | Validate key prefix at startup |
| Leaked keys in git | .env in .gitignore, secret scanning in CI |
| Wrong env detected | Explicit NODE_ENV in deployment config |
| Config drift | Zod schema validation at startup |
| Issue | Cause | Solution |
|---|---|---|
| Wrong environment | Missing NODE_ENV | Set explicitly in deployment config |
| Secret not found | Wrong secret path | Verify secret manager paths match |
| Cross-env data leak | Shared API key | Use separate keys per environment |
| Startup crash | Missing config | Add Zod validation with clear error messages |
Produce an environment matrix showing each deployment's Langfuse project, secret reference names, host, and startup-validation status. Include a synthetic trace result for each environment, never the credentials themselves.
Deploy development and staging with separate secret-manager entries, then verify each synthetic trace appears only in its designated project. Before production promotion, intentionally test a missing configuration value in staging and confirm startup fails with the safe validation message rather than sending traffic to another environment.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/.curated/langfuse-multi-env-setup of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit 80f86df
Langfuse Multi Env Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Langfuse Multi Env Setup this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2k | Automated safety check: Notes | MIT | |
| Langfuse Previewslangfuse/langfuse | 36k | — | ~2.8k | Automated safety check: Notes | Custom licence | |
| Backend Dev Guidelineslangfuse/langfuse | 36k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Langfuselangfuse/skills | 300 | — | ~2.1k | Automated safety check: Notes | MIT | |
| Agentsop Observability Setupagentsope/SkillAlchemy | 466 | — | ~4.4k | Automated safety check: Pass | MIT | |
| Agent Setup Maintenancelangfuse/langfuse | 36k | — | ~799 | Automated safety check: Pass | Custom licence |
langfuse/langfuse
Use Langfuse's disposable per-PR previews at pr-N.preview.langfuse.com (synthetic data only).
langfuse/langfuse
Build or review Langfuse backend code. An agent skill from langfuse/langfuse.
langfuse/skills
Interact with Langfuse and access its documentation: tracing, monitoring, creating datasets, running experiments, and evaluating AI applications.
agentsope/SkillAlchemy
Enhancement-overlay skill — the DECISION + WIRING layer for LM observability that the single-backend skills [[langsmith]], [[phoenix]], [[mlflow]] do NOT cover.
langfuse/langfuse
Shared workflow for editing Langfuse's repo-owned agent setup under .agents/.
soba-labs/langchain-agent-skills
Deploy and operate production agent servers with LangSmith Deployment.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Categories
Configure Langfuse across development, staging, and production environments. Langfuse Multi Env Setup is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure Langfuse across development, staging, and production environments.
Langfuse Multi Env Setup fits situations like: setting up multi-environment deployments; configuring per-environment keys; implementing environment-specific Langfuse configurations; with phrases like langfuse environments.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill langfuse-multi-env-setup -a claude-code`. Or copy the skill folder (skills/.curated/langfuse-multi-env-setup in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/langfuse-multi-env-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill langfuse-multi-env-setup -a codex`. Or copy the skill folder (skills/.curated/langfuse-multi-env-setup in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/langfuse-multi-env-setup in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill langfuse-multi-env-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/langfuse-multi-env-setup, .gemini/skills/langfuse-multi-env-setup, .github/skills/langfuse-multi-env-setup and .opencode/skills/langfuse-multi-env-setup in your project.
Going by SKILL.md and its folder, Langfuse Multi Env Setup needs the command-line tools its instructions call (aws and gcloud) and credentials named LANGFUSE_PUBLIC_KEY and LANGFUSE_SECRET_KEY. Our summary lists: A credential in LANGFUSE_PUBLIC_KEY; A credential in LANGFUSE_SECRET_KEY. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(aws:*), Bash(gcloud:*), Bash(vault:*). Compatibility (from SKILL.md): Designed for Claude Code.
SKILL.md names 2 domains. In commands or code: cloud.langfuse.com; the agent is likely to contact it when it follows the instructions. As links in the text: langfuse.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Langfuse Multi Env Setup is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Langfuse Multi Env Setup: Langfuse Previews (langfuse/langfuse, 36k stars), Backend Dev Guidelines (langfuse/langfuse, 36k stars), Langfuse (langfuse/skills, 300 stars) and Agentsop Observability Setup (agentsope/SkillAlchemy, 466 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.