agentleFS
Bbar0n234Bbar0n234/learnflow-ai/.claude/skills/langfuse/SKILL.md

langfuse

Skill35 starsChanged 3 months agoApache-2.0View on GitHub

Interact with Langfuse and access its documentation. Use when needing to (1) query or modify Langfuse data programmatically via the CLI — traces, prompts, datasets, scores, sessions, and any other API resource, (2) look up Langfuse documentation, concepts, integration guides, or SDK usage, or (3) understand how any Langfuse feature works. This skill covers CLI-based API access (via npx) and multiple documentation retrieval methods.

  • Reads credentials

20 other projects use a version of this, 11 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use algorithmic-art, web-design-guidelines and 1 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

  • 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

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the langfuse-cli to interact with the full Langfuse REST API from the command line.

    line 12
  2. Very specific:

    If not set, ask the user for their API keys (found in Langfuse UI → Settings → API Keys) and which host they use (cloud.langfuse.com, …

    line 41
  3. Distinctive:

    When you need to find information across all docs and github issues/discussions without knowing the specific page:

    line 74
  4. Distinctive:

    Search is a great fallback if you cannot find the relevant pages or need more context.

    line 94
  5. Distinctive:

    Start with llms.txt to orient — scan for relevant page titles

    line 98
  6. Distinctive:

    Fetch specific pages: when you identify the right one

    line 99

“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

Two core capabilities: programmatic API access via the Langfuse CLI, and documentation retrieval via llms.txt, page fetching, and search.

1. Langfuse API via CLI

Use the langfuse-cli to interact with the full Langfuse REST API from the command line. Run via npx (no install required):

npx langfuse-cli api <resource> <action>

Quick Start

# Discover all available resources
npx langfuse-cli api __schema

# List actions for a resource
npx langfuse-cli api <resource> --help

# Show args/options for a specific action
npx langfuse-cli api <resource> <action> --help

Credentials

Set environment variables before making calls:

export LANGFUSE_PUBLIC_KEY=pk-lf-...
export LANGFUSE_SECRET_KEY=sk-lf-...
export LANGFUSE_HOST=https://cloud.langfuse.com  # optional, default is EU

If not set, ask the user for their API keys (found in Langfuse UI → Settings → API Keys) and which host they use (cloud.langfuse.com, us.cloud.langfuse.com, or self-hosted URL).

Detailed CLI Reference

For common workflows, tips, and full usage patterns, see references/cli.md.

2. Langfuse Documentation

Three methods to access Langfuse docs, in order of preference:

2a. Documentation Index (llms.txt)

Fetch the full index of all documentation pages:

curl -s https://langfuse.com/llms.txt

Returns a structured list of every doc page with titles and URLs. Use this to discover the right page for a topic, then fetch that page directly.

Alternatively, you can start on https://langfuse.com/docs and explore the site to find the page you need.

2b. Fetch Individual Pages as Markdown

Any page listed in llms.txt can be fetched as markdown by appending .md to its path or by using Accept: text/markdown in the request headers. Use this when you know which page contains the information needed. Returns clean markdown with code examples and configuration details.

curl -s "https://langfuse.com/docs/observability/overview.md"
curl -s "https://langfuse.com/docs/observability/overview" -H "Accept: text/markdown"

2c. Search Documentation

When you need to find information across all docs and github issues/discussions without knowing the specific page:

curl -s "https://langfuse.com/api/search-docs?query=<url-encoded-query>"

Example:

curl -s "https://langfuse.com/api/search-docs?query=How+do+I+trace+LangGraph+agents"

Returns a JSON response with:

  • query: the original query
  • answer: a JSON string containing an array of matching documents, each with:
    • url: link to the doc page
    • title: page title
    • source.content: array of relevant text excerpts from the page

Search is a great fallback if you cannot find the relevant pages or need more context. Especially useful when debugging issues as all GitHub Issues and Discussions are also indexed. Responses can be large — extract only the relevant portions.

Documentation Workflow

  1. Start with llms.txt to orient — scan for relevant page titles
  2. Fetch specific pages when you identify the right one
  3. Fall back to search when the topic is unclear and you want more context

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.