Agent skill · software engineering · jeremylongshore
langfuse-multi-env-setup
Configure Langfuse across development, staging, and production environments.
Why this skill is useful
Provides specific environment configuration patterns for Langfuse that the AI wouldn't reliably generate on its own.
What it needs
Requires aws, gcloud, vault installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Langfuse Multi-Environment Setup Overview 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. Prerequisites Separate Langfuse API key pairs per environment (or separate projects) Secret management solution (env vars, Vault, AWS/GCP secrets) CI/CD pipeline with environment-aware deployment Environment Strategy 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 Instructions Step 1: Environment-Specific Configuration Step 2: Environment Variable Files Step 3: Secret Management Step 4: CI/CD Integration Step 5: Startup Validation with Zod Cross-Environment Safety 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 NODEENV in deployment config Config drift Zod schema validation at startup Error Handling Issue Cause Solution ------- ------- ---------- Wrong environment Missing NODEENV 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 Output 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/langfuse-multi-env-setup