CtrlK
BlogDocsLog inGet started
Tessl Logo

langfuse-common-errors

Diagnose and fix common Langfuse errors and exceptions. Use when encountering Langfuse errors, debugging missing traces, or troubleshooting integration issues. Trigger with phrases like "langfuse error", "fix langfuse", "langfuse not working", "debug langfuse", "traces not appearing".

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

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 content is highly actionable with executable fixes for ten well-organized errors, but it is verbose for a single SKILL.md and lacks explicit verification steps within each fix. Splitting the catalog into a reference file and consolidating repeated diagnostic checks would improve both conciseness and progressive disclosure.

Suggestions

Add a brief verification step to each fix (e.g., after the auth fix, re-run the auth curl to confirm a 200) so the diagnostic workflow has explicit checkpoints.

Consolidate the repeated connectivity/health-check curl blocks into the single Quick Diagnostic Script and reference it from errors 1, 3, and 9 instead of duplicating the commands.

Move the ten-entry error catalog into a separate references file (e.g. ERRORS.md) and keep SKILL.md as an overview pointing to it, improving progressive disclosure.

DimensionReasoningScore

Conciseness

The error/cause/fix format is efficient and avoids explaining concepts Claude knows, but the ~330-line catalog repeats connectivity checks (curl health probes in errors 1, 3, and 9 plus the diagnostic script) and carries v3/v4 version notes that could be tightened.

2 / 3

Actionability

Every fix is concrete, executable code — e.g. `curl -s -o /dev/null -w "HTTP %{http_code}"`, `npm install @langfuse/client@latest`, `await sdk.shutdown()`, `stream_options: { include_usage: true }` — copy-paste ready.

3 / 3

Workflow Clarity

A sequenced escalation path and a Quick Diagnostic Script provide a checkpoint, but the per-error fixes generally lack an explicit verify-the-fix-succeeded step, leaving validation gaps in the diagnostic workflow.

2 / 3

Progressive Disclosure

The body is a single self-contained ~330-line error catalog with no bundle/reference files; everything is inline and could be split so SKILL.md serves as an overview pointer to a separate error reference.

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 strong: it states concrete capabilities, provides explicit trigger guidance, uses natural user phrasing, and occupies a distinct niche. It is written in third person with no padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Diagnose and fix common Langfuse errors", "debugging missing traces", "troubleshooting integration issues" — rather than vague domain naming.

3 / 3

Completeness

Explicitly answers both what ("Diagnose and fix common Langfuse errors and exceptions") and when ("Use when encountering Langfuse errors...") with explicit trigger phrases.

3 / 3

Trigger Term Quality

Provides natural trigger phrases users would actually say: "langfuse error", "fix langfuse", "langfuse not working", "debug langfuse", "traces not appearing".

3 / 3

Distinctiveness Conflict Risk

A clear Langfuse-specific niche with distinct triggers like "traces not appearing" makes it unlikely to fire for unrelated skills.

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.