agentleFS
Sign inStart free
avivsinaiavivsinai/langfuse-mcp/skills/langfuse/SKILL.md

langfuse

Skill112 starsChanged 8 months agoMITView on GitHub

Investigate AI traces, observations, exceptions, latency, sessions, prompts, datasets, annotation queues, and scores through Langfuse MCP. Use when the request names Langfuse or asks to diagnose recorded AI behavior.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use algorithmic-art, web-design-guidelines and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GoogleSkill

    algorithmic-art

    Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

    Also in 3 projects that use this

  • VercelSkill

    web-design-guidelines

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 4 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use Langfuse evidence to move from a broad symptom to the relevant trace, observation, session, prompt, or dataset.

    line 12
  2. Very specific:

    Treat model names, prompts, timestamps, and other values in historical traces as recorded evidence.

    line 33
  3. Distinctive:

    Prefer read-only server mode for diagnostic work.

    line 39
  4. Distinctive:

    Never commit Langfuse credentials.

    line 47

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Langfuse

Use Langfuse evidence to move from a broad symptom to the relevant trace, observation, session, prompt, or dataset. Start with the narrowest read-only query that can locate the event, then inspect its concrete inputs, outputs, timing, and errors.

Route the task

  • For trace, observation, exception, latency, or session diagnosis, read diagnostic and management workflows.
  • For installation, credentials, tool groups, output defaults, connection failures, or empty results, read setup.
  • For exact parameters, filters, pagination, output modes, and response shapes, read the tool reference.

A common investigation starts with fetch_traces(age=60) or find_exceptions(age=1440, group_by="file"), then fetches the selected trace or observation by ID. Use full_json_file only when the complete payload is needed; exports can contain sensitive user data.

Evidence and mutation boundaries

  • Treat model names, prompts, timestamps, and other values in historical traces as recorded evidence. Do not rewrite or normalize old model identifiers to a current name such as gpt-6-astra.
  • Trace discovery and inspection are read-only. Prompt creation or relabeling, dataset changes, annotation-queue changes, and deletions mutate Langfuse; perform them only when the user requested that change.

  • Prefer read-only server mode for diagnostic work. It disables prompt and dataset write tools:

    langfuse-mcp --read-only
# or LANGFUSE_MCP_READ_ONLY=true
  • Never commit Langfuse credentials. Keep public key, secret key, and host in the supported environment or MCP configuration described in the setup reference. Rotate any exposed key.
  • Preserve exact IDs and filters in findings so another reader can reproduce the query. State when pagination, lookback limits, or compact output limits the conclusion.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free