What it does
This repo is a collection of 33 skills
- Connects Instruction files the AI reads, with steps that call an outside service
- Account or key Some steps need a key for LANGFUSE_SECRET_KEY, LANGFUSE_PUBLIC_KEY (per the README)
- Category Coding
Maker’s original description
🪢 Open source AI engineering platform: AI Gateway, agent observability, evals, and prompt/skill management, built on OpenTelemetry. One open platform for every AI call and every agent. Self-host or use Langfuse Cloud.For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/langfuse-langfuse)Use together with
MCP servers that connect the AI to services for the same work
Fallow
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
Desktop Commander
MCP server for terminal commands, file operations, and process management
Similar Skills
Same kind of work, ordered like the Skills list
| This one langfuse | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Maker | langfuse | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 33 | 1 | 1 | 1 | 1 |
| GitHub stars | 37,495 | 463,670 | 233,682 | 148,887 | 143,987 |
| Last code change | Nov 17, 2026 | Nov 17, 2026 | Apr 20, 2026 | Nov 17, 2026 | Nov 16, 2026 |
| License | – | MIT | – | Apache-2.0 | MIT |
33 skills (instruction sets) by langfuse that an AI reads and follows · not an MCP server
Pick the skill to install
Install only the ones you use. Open a skill to see how to install it
This set has 33 skills, too many to install at once: every installed skill’s description loads into every chat, so the AI picks the wrong one more easily. Pick only the ones you use from the list below
Showing 30 of 33 See all on GitHub
- add-model-price
Use when editing worker/src/constants/default-model-prices.json, packages/shared/src/server/llm/types.ts, pricing tiers, tokenizer IDs, or matchPattern regexes for OpenAI, Anthropic, Bedrock, Vertex, Azure, or Gemini model pricing.
- agent-setup-maintenance
Shared workflow for editing Langfuse's repo-owned agent setup under `.agents/`. Use when changing AGENTS files, shared skills, `.agents/config.json`, generated shim behavior, provider discovery paths, or install-time agent sync.
- analyze-cloud-costs
Analyze Langfuse Cloud infrastructure cost structure using Metabase cost marts. Use when asked about cloud spend, AWS versus ClickHouse cost splits, cost drivers by provider/service/usage type/account, daily cost per tracing event, infra cost dashboards, or cost regressions visible in Metabase.
- backend-dev-guidelines
Build or review Langfuse backend code. Use for tRPC routers, public REST APIs, BullMQ processors, services, middleware, Prisma or ClickHouse access, OpenTelemetry, Zod, environment configuration, or backend tests.
- changelog-writing
Shared workflow for writing Langfuse changelog entries after a feature is complete. Use when a branch is ready for merge and a changelog entry or changelog draft is needed.
- clickhouse-best-practices
MUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 28 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.
- code-review
Review Langfuse code changes for correctness, regressions, and best practices.
- create-repo-agent
Design, implement, review, or harden Langfuse repo-owned autonomous agents. Use for LLM-powered GitHub Actions, scheduled or dispatched agents, agent-created PRs, prompts, allowlists, tokens, untrusted content, or self-updating instructions.
- datadog-query-recipes
Research Langfuse production telemetry with reusable Datadog queries. Use for tenant or project activity, API usage, queue behavior, spans, logs, metrics, or ad hoc measurements across production regions; pair with debug-issue-with-datadog for root-cause analysis.
- debug-issue-with-datadog
Establish root cause by combining Datadog telemetry with the Langfuse repo. Use when investigating or triaging a user report, Linear or GitHub issue, incident, or pasted production error.
- frontend-browser-review
Shared workflow for browser-based review of user-visible frontend changes in Langfuse. Use when a change affects UI behavior, layout, styling, navigation, or browser-visible regressions and should be checked with available browser automation before signoff.
- frontend-large-feature-architecture
Architect large or state-heavy Langfuse frontend features. Use for virtualized lists, large tables, controllers, Zustand stores, row selection, high-frequency state, rendering performance, or before adding useEffect, useMemo, useCallback, or form defaults derived from loaded data.
- git-workflow
Langfuse repo Git, GitHub, commit, branch, pull request, issue search, release, and production-promotion workflow. Use when staging, committing, pushing, opening PRs, choosing a Linear git branch name, handling Claude, Greptile, or Codex review comments, searching GitHub issues, or changing release…
- housekeeping
Triage an engineer's work queue across Linear, Pylon, and GitHub. Use for assigned, urgent, waiting, or stale issues, support follow-ups, and PR reviews.
- incident-alert-tickets
Read and record root causes in the Linear `incident-alert` knowledge base. Use before and after investigating a named Datadog monitor, incident.io alert or incident, or on-call page to find or record root causes.
- infra-scaling
Tune and review Langfuse autoscaling for web, web-iso, and web-ingestion. Use for Terraform scale settings, RPM targets, scaling bounds, task counts, cost/performance tradeoffs, or Datadog evidence in the infrastructure repo.
- langfuse-codebase-navigator
Navigate Langfuse repositories, code areas, and agent skills. Use to locate code, choose the right repo or skill, search across the Langfuse organization, or orient before implementation, debugging, documentation, support, or operations.
- langfuse-previews
Use Langfuse's disposable per-PR previews at pr-N.preview.langfuse.com (synthetic data only). Use for preview access, failed deployments, test-data seeding, kubectl debugging, or waking sleeping previews.
- linear-bug-triage
Use this skill after a bug or regression candidate has measured evidence to document them within linear.
- pnpm-upgrade-package
Upgrade pnpm workspace dependencies to target/latest versions: direct/transitive bumps, release-age checks, temporary overrides, minimumReleaseAgeExclude, lockfile verification.
- posthog-instrumentation
Product analytics with posthog. Use when adding a meaningful user action or feature in `web/**`, touching PostHog capture code, changing session replay or its privacy boundaries, or answering product-usage questions.
- react-component-cleaner
Use this skill to clean up a React component. Only use this skill when instructed to do so by the user.
- react-component-guidelines
Guidelines for writing React components. Use this when creating a new react component.
- refactor-react-effects
Refactor avoidable React useEffect usage in Langfuse frontend code. Use when adding, reviewing, or removing effects; initializing forms or local UI state from query data; synchronizing client and server state; moving mutations or async workflows out of components; cleaning every effect from a front…
- security-review
Review Langfuse changes for SSRF, tenant isolation, secret handling, unsafe redirects or uploads, RBAC drift, and client telemetry privacy. Use when a design or change accepts URLs or host fields, handles secrets or cross-tenant data, makes outbound requests, adds an integration, follows redirects,…
- seed-test-data
Seed reproducible local Langfuse data in ClickHouse and Postgres. Use for complex traces, long sessions, v3/v4 events, bulk list data, or frontend rendering and performance tests; never use ad hoc scripts or raw inserts.
- sentry-instrumentation
Decide whether and how errors report to Sentry. Use when touching capture or error-handling paths in `web/**`, triaging Sentry noise, or changing Sentry settings.
- skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
- storybook
Use when writing or reviewing Storybook stories (`.stories.tsx`) for React components.
- turborepo
Configure and troubleshoot Turborepo monorepos. Use for turbo.json, task pipelines, dependsOn, caching, filters, affected packages, CI optimization, environment variables, package boundaries, or shared internal packages.
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Codex
From the maker’s README and the folders in the repo
Install
Pick a skill first
This repo has 33 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP
Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 37,495
Stars are for the whole repo, not each skill - Maker
- langfuse
- License
- No license stated This repo states no license. By default the author keeps all rights: ask before you share it or use it commercially.
- Last code change
- Nov 17, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 30
- Topics
- ai-gateway, analytics, evaluation, gateway, langchain, large-language-models, llama-index, llm, llm-evaluation, llm-gateway, llm-observability, llmops