Add Yourself To Team Langfuse
langfuse/langfuse-docs/.agents/skills/add-yourself-to-team-langfuse
analysisOfficial
Official Provider SkillView repo
Add a new team member to Langfuse's canonical team data and shared team table. Use when onboarding a new employee who needs to appear on the website team, press, about, careers, or handbook pages.
Files1 files
SKILL.md63 lines
Loading editor…
Install
RecommendedOne command — your agent picks it up automatically.
Select an AI agent above to see the install command.
or
Manual Install
More stepsDownload the file and paste it into your agent's system prompt.
Skill details
Versionv1.0.0
AuthorLangfuse
Categoryanalysis
Skill IDlangfuse/langfuse-docs/.agents/skills/add-yourself-to-team-langfuse
Related skills
Customer Story SetupConverts draft customer-story Markdown into Langfuse website MDX (Fumadocs), collects missing metadata and assets, wires meta.json and authors. Use when adding or converting a customer case study, user story, or /users page, or when the user mentions customer story setup, cresta/canva-style posts, or CustomerStoryCTA/BlogHeader for customers.Langfuse Integration PageCreate a new Langfuse integration page in the langfuse-docs repo. Use this skill whenever the user wants to add, create, draft, or scaffold an integration page, cookbook, or docs page for a new tool/framework/model-provider/gateway in Langfuse — triggers include "new integration", "integration page", "docs page for <X>", "cookbook for <X>", "add <X> to langfuse docs", or any request that results in a new `cookbook/integration_*.ipynb`. Also use when the user pastes working integration code, a liDatadog Query RecipesLangfuse-specific Datadog query recipes for production telemetry research.
Use when asked to investigate tenant or project activity, public API endpoint
usage, queue consumer behavior, spans, logs, metrics, or ad hoc production
questions across prod-us, prod-eu, prod-hipaa, and prod-jp. This skill is for
reusable query shapes and measured research; pair it with
debug-issue-with-datadog when the task is an incident or root-cause analysis.Debug Issue With DatadogDebug a user-reported issue, Linear ticket, or incident report by combining
Datadog (APM, logs, metrics) with the Langfuse repo to establish a
root cause. Use when given a Linear issue URL/ID (e.g. LFE-XXXX), a GitHub
issue, or a pasted error/report and asked to investigate, root-cause, or
triage. Produces a structured analysis — error breakdown, hypothesis-by-class,
suggested patches with code references.Linear Bug TriageDeduplicate measured bug or regression evidence against Linear, then either
add evidence comments to related existing issues or create concise Linear bug
issues in Triage. Use when Codex has confirmed evidence from Datadog,
benchmarks, traces, timings, flamegraphs, logs, or production measurements and
needs Linear search, comments, labels, Datadog links, or bug ticket creation
without fix suggestions, but only after a human has approved sharing the
findings in Linear.Weekly Production ReviewPrepare Langfuse weekly production reviews that audit what broke, what was
fixed, what remains open, and where Datadog, incident.io, or Linear tracking
needs cleanup. Use when asked for a production review, "what broke last week",
fixed/open production bugs, Datadog alerted monitors/pages, Datadog error log
patterns, incident.io incidents, incident.io alert load, pager load by
engineer or time of day, or a source-table engineering review across
incident.io, Linear bugs, Datadog alerts, and Datad