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.
SkillScore84Maintained
Automatic
◆Coding pack
Last verified 9/27/2026
What it changes
Passed 18 of 21 test cases with the skill, and 8 of 21 without it.
Without skill36%
With skill84%
Checks it passed that the model alone missed
Routes model pricing additions to langfuse/langfuse.
Recommends using the add-model-price repo-local skill.
Limits ordinary updates to a title and a few sentences.
and 17 more in the full report
14 fixed7 passed either way2 still failing2 broke
Pass-rate lift
+48 pp
Tokens
+29%
Agent turns
0%
Response time
-53%
Model gemini-3.6-flashMeasured 9/27/2026v321 of 25 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
When working locally in langfuse and needing langfuse-python which is not yet present in the parent directory, what exact GitHub CLI command clones it into the sibling parent location?
What was checked, without and with the skill
Checked
Without skill
With skill
Uses gh repo clone langfuse/langfuse-python $LANGFUSE_PARENT/langfuse-python to clone into the sibling parent directory.
Missed
Passed
case-17 · gemini-3.6-flash · 9/27/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md65 lines2 files
Langfuse Codebase Navigator
Use this as the first stop for Langfuse org navigation. Your job is to choose the right repository, code area, and more specific skill before doing deeper work.
SDK or client library behavior: langfuse/langfuse-js, langfuse/langfuse-python, langfuse/langfuse-java, or generated clients in langfuse/langfuse.
Deployment or self-hosting: langfuse/langfuse-k8s, langfuse/langfuse-terraform-*, langfuse/oss-llmops-stack, and docs self-hosting content.
Langfuse Cloud infrastructure and ops: langfuse/infrastructure, langfuse/analytics, langfuse/langfuse-ops, or langfuse/platform.
Agent skills: langfuse/skills, langfuse/langfuse-internal-skills, repo-local .agents/skills, or repo-local .claude/skills.
GitHub Actions, CLI, MCP, n8n, examples, or experiments: route to the specialized repo in references/repository-map.md.
Read references/repository-map.md when the route is not obvious, the task spans repos, or the user asks for org-level orientation.
Before editing, check for a more specific skill in the target repo or a sibling internal-skills checkout. If one matches, open it and follow it.
Search locally first in sibling repos next to the current checkout. If a needed repo is absent, clone it into the same parent directory with gh repo clone langfuse/<repo> "$LANGFUSE_PARENT/<repo>".
Return or act on a route decision with: target repo(s), relevant folders/files, specific skills to load, and the next search command or implementation step.
Quick Skill Routing
Product implementation in langfuse/langfuse: choose the matching repo-local skill under .agents/skills, such as backend-dev-guidelines, frontend-browser-review, clickhouse-best-practices, add-model-price, turborepo, pnpm-upgrade-package, code-review, or production-debug skills as applicable.
Cursor Cloud or Cursor desktop agents implementing a Linear issue, opening a PR, applying the cursor GitHub label, asking a human to test, or handling Claude, Greptile, or Codex review comments: use cursor-agents-workflow.
A change too large for one reviewable PR: split it into small stacked PRs rather than one wide PR.
"What should I do today", or preparing a weekly project update: use linear-work-rhythm.
Reconstructing why a surface is the way it is before changing it, or proposing the reasoning behind finished work onto its Linear ticket: use linear-context-handover.
Before any agent write to Linear — a comment, a description edit, a ticket: use linear-agent-writes, the write policy (propose updates; mark every write). Ordinary writes stay a title and a few sentences. Subtickets under an existing parent are free.
Frontend work under langfuse/langfuse/web: also check web/.agents/skills/vercel-react-best-practices and web/.agents/skills/vercel-composition-patterns.
Infrastructure autoscaling or cloud capacity: use infra-scaling.
Public Langfuse usage, docs lookup, API access, instrumentation, prompt migration, SDK upgrade, trace analysis, or CLI work: use the public langfuse skill from langfuse/skills.
Support, support review, PR funnel, social copy, meeting notes, Plain search, blog writing, or unslop work: use the matching skill from langfuse/langfuse-internal-skills when available.
Search Patterns
Use rg and file lists before broad reading.
# Resolve the parent directory that holds sibling Langfuse repos
LANGFUSE_REPO_ROOT="$(git rev-parse --show-toplevel)"
LANGFUSE_PARENT="$(dirname "$LANGFUSE_REPO_ROOT")"