Agent skill · langfuse
langfuse-onboarding
Configure an agent for whoever is using it — outside contributor or Langfuse maintainer, which areas they work on, which integrations are connected — and, for someone genuinely new, walk them through onboarding. Use on "onboard me", "I'm new here", "what do I need to set up", "am I set up correctly", "why can't you see my tickets", and whenever you need to know someone's role and no identity file exists yet.
What it needs
About 6k tokens when loaded.
What this skill does
Onboarding at Langfuse Two jobs, and they are separable — most of the time you only want the first. 1. Configuration (steps 1, 2 and 4): work out who is using this agent, what they work on, and what they are connected to. Seconds, not a session. Someone who has been here a year needs this and nothing else — do not walk a colleague through a new-joiner path to find out their name. 2. Onboarding (steps 3 and 5): the walkthrough, for people who are actually new. Everything an agent needs in order to behave differently for a contributor than for a maintainer comes from the first, so do that before anything else. Step 1 — derive the role; do not ask what you can find out Two signals, in order. Both are read-only. push: true → maintainer. They have write access to the app repo. push: false or the call fails → treat as an outside contributor until they say otherwise. Then check whether the tracker answers a real read. That is the second signal, and the one that matters here: a maintainer with no tracker connection is a setup gap, not a contributor, and step 4 is where you fix it. Do not infer this from git config user.email. That is a local setting, not an identity: roughly a third of recent commits here come from personal addresses, and both @clickhouse.com (the company domain — Langfuse is part of ClickHouse) and the older @langfuse.com are still in daily use. Write access answers the question directly, so ask that instead of guessing from a string. Say what you found and let them correct it. Never announce a role silently — a wrong guess sends someone down the wrong half of this file. Step 2 — record it, so this happens once Write ~/.config/langfuse/me.md. Machine-level on purpose: it has to answer the question in langfuse, in langfuse-docs, and in a scratch directory, so it cannot live in one repo. Create the directory if it does not exist. Never commit this file, and never put a secret in it. It is notes, not config: no tokens, no keys. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills langfuse/langfuse-onboarding