CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is highly actionable with complete executable examples and a clear step sequence, but it duplicates content from an orphaned reference file and omits validation checkpoints in the workflow. Tightening the inline detail and linking the reference would raise conciseness and disclosure scores.

Suggestions

Add explicit validation checkpoints to the workflow — e.g., after exposing /metrics, verify with `curl localhost:3000/metrics` and confirm Prometheus targets are UP before building dashboards.

Link references/implementation.md from the body (e.g., under an 'Advanced' section) and move the duplicated Grafana dashboard and alert-rule blocks there, keeping SKILL.md as a concise overview.

Drop or condense the 'Key Metrics Reference' and 'Error Handling' tables where they restate the code, keeping only entries that add information not already visible in the examples.

DimensionReasoningScore

Conciseness

The body is mostly lean code/config with little concept explanation, but the 'Key Metrics Reference' and 'Error Handling' tables restate what the code already shows, and the Prometheus/Grafana/alert content duplicates references/implementation.md — so it could be tightened.

2 / 3

Actionability

Provides complete, copy-paste-ready TypeScript, YAML, and JSON examples (metrics definitions, instrumented LLM wrapper, scrape config, dashboard, alert rules) with no pseudocode gaps.

3 / 3

Workflow Clarity

Steps 1–6 are clearly sequenced, but there are no validation or verification checkpoints (e.g., confirm Prometheus scrapes /metrics, verify the dashboard renders), leaving feedback loops implicit.

2 / 3

Progressive Disclosure

Sections are organized, but the bundled references/implementation.md is never linked or signaled from the body, and the body inlines full Grafana/alert content that duplicates that file — content that should be split out is inline and the reference is orphaned.

2 / 3

Total

9

/

12

Passed

Description

100%

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 concise, specific, and complete: it states concrete capabilities, gives explicit 'Use when' guidance, and lists natural trigger phrases within a clearly distinct Langfuse-observability niche. It aligns closely with the rubric's good examples.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'metrics, dashboards, and alerts' — rather than vague language, matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Set up comprehensive observability...with metrics, dashboards, and alerts') and when ('Use when implementing monitoring for LLM operations...'), with explicit trigger guidance.

3 / 3

Trigger Term Quality

Lists natural phrases a user would say ('langfuse monitoring', 'langfuse metrics', 'monitor langfuse', 'langfuse alerts', 'langfuse dashboard'), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The Langfuse-specific niche and scoped triggers make it unlikely to fire for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.