ClawHub

Langfuse

v0.1.2

Query and manage Langfuse traces, prompts, datasets, sessions, observations, scores, and metrics via Langfuse SDKs and the public API. Use when setting up or...

⭐ 1· 32·0 current·0 all-time
bySouth American Cowboy@south-american-cowboy
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
Crypto
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description match the behavior: the skill describes interacting with Langfuse traces, prompts, datasets, etc., and it requires only LANGFUSE_PUBLIC_KEY, LANGFUSE_SECRET_KEY, and LANGFUSE_BASE_URL — all directly relevant to Langfuse API/SDK access.
✓
Instruction Scope
SKILL.md instructions stick to Langfuse integration patterns (SDK usage, API examples, prompt migration, self-hosting guidance). It explicitly limits when live credentials are needed and instructs to prefer environment variables; it does not ask for unrelated files, system paths, or extra credentials.
✓
Install Mechanism
Instruction-only skill with no install spec or remote downloads. Nothing is written to disk or fetched at install time by the skill itself, which is the lowest-risk install model.
✓
Credentials
The three required environment variables are proportional to the functionality. LANGFUSE_SECRET_KEY is the primary credential (sensitive), and LANGFUSE_BASE_URL is needed for self-hosted deployments; the SKILL.md also recommends using least-privilege/scoped keys and avoiding pasting production keys into chat.
✓
Persistence & Privilege
The skill is not marked always:true and is user-invocable only. It does not request modification of other skills or system-wide settings and has no install-time persistence requirements.
Assessment
This skill appears coherent and focused on Langfuse integration. Before installing, only provide LANGFUSE_SECRET_KEY and LANGFUSE_PUBLIC_KEY when a live connection is truly needed; prefer scoped/read-only keys for read-only tasks. For self-hosted deployments, confirm the LANGFUSE_BASE_URL is correct and that network/TLS access is intended. Do not paste production secret keys into chat — use environment variables as recommended. If you need the skill to run autonomously with live credentials, be aware it will be able to query your Langfuse project data (traces, prompts, metrics) while enabled.

Like a lobster shell, security has layers — review code before you run it.

latestvk974zzj0f97p9kk486maa35g1h84bfws

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

EnvLANGFUSE_PUBLIC_KEY, LANGFUSE_SECRET_KEY, LANGFUSE_BASE_URL
Primary envLANGFUSE_SECRET_KEY

Comments