langfuse-observability

Set up comprehensive observability for Langfuse with metrics, dashboards, and alerts. Use when implementing monitoring for LLM operations, setting up dashboards, or configuring alerting for Langfuse integration health. Trigger with phrases like "langfuse monitoring", "langfuse metrics", "langfuse observability", "monitor langfuse", "langfuse alerts", "langfuse dashboard".

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with complete, executable code and a clear sequenced workflow, and it is reasonably token-efficient. Its main weakness is progressive disclosure: a reference bundle exists but is never linked, while its content is duplicated inline in SKILL.md.

Suggestions

Link references/implementation.md from the body (e.g., add an 'Advanced / full implementation' section pointing to it) and move the bulk metrics, Grafana, and alert definitions there, keeping SKILL.md as an overview.

Add a verification checkpoint after exposing the metrics endpoint (e.g., 'curl /metrics and confirm Prometheus target is up') to close the workflow validation gap.

Tighten the Step 1 prose ('Langfuse provides pre-built dashboards in the UI at...') into a terser pointer to reduce remaining over-explanation.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code and tables with little concept padding, assuming Claude knows Prometheus/Grafana; minor introductory prose around a few steps could be trimmed, keeping it just below a 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready artifacts across every step: prom-client metric definitions, an instrumented LLM wrapper, a metrics endpoint, prometheus.yml, Grafana JSON, and alertmanager YAML.	5 / 5
Workflow Clarity	Steps 1–6 are clearly sequenced with concrete code per step, but there is no explicit validation/verification checkpoint (e.g., confirm Prometheus scrapes /metrics or Grafana renders data), leaving a minor validation gap.	4 / 5
Progressive Disclosure	The body inlines metrics, Grafana, and alert content that duplicates the existing references/implementation.md bundle, yet never links to that file, so references are present but not signaled and content that could be separate is inline.	3 / 5
	Total	16 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person voice, clear what/when structure, and a rich set of natural trigger phrases scoped to a distinct Langfuse niche. The only minor weakness is that the listed actions (metrics, dashboards, alerts) are somewhat generic rather than fully enumerated.

Dimension	Reasoning	Score
Specificity	Names the Langfuse observability domain and several concrete actions ('metrics, dashboards, and alerts'), but the actions are somewhat high-level rather than enumerated in full detail, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Set up comprehensive observability for Langfuse with metrics, dashboards, and alerts') and when ('Use when implementing monitoring for LLM operations...'), supplemented with concrete trigger phrases.	5 / 5
Trigger Term Quality	Lists six natural trigger phrases a user would actually say ('langfuse monitoring', 'langfuse metrics', 'langfuse observability', 'monitor langfuse', 'langfuse alerts', 'langfuse dashboard') with good synonym coverage.	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Langfuse-specific observability) with distinct 'langfuse'-prefixed triggers, making conflict with other skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/langfuse-pack/skills/langfuse-observability/SKILL.md
Commit: 8585d6d

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.