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

Quality

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/saas-packs/langfuse-pack/skills/langfuse-common-errors/SKILL.md

Quality

Content

64%

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

This is a solid diagnostic reference skill with real error messages, concrete fixes, and good coverage of common Langfuse issues. Its main strengths are actionability (executable code for every error) and clear error-to-fix mapping. Weaknesses include missing verification steps after applying fixes and the monolithic structure that could benefit from progressive disclosure via supporting bundle files.

Suggestions

Add a verification step after each fix (e.g., 'Re-run the auth test above to confirm the fix worked') to close the feedback loop in the diagnostic workflow.

Consider splitting the 10 error references into a separate ERRORS_REFERENCE.md and keeping SKILL.md as a concise index/lookup table with links to each error's detailed fix.

Dimension	Reasoning	Score
Conciseness	Generally efficient with real error messages and targeted fixes, but some sections include minor unnecessary context (e.g., Prerequisites listing obvious items like 'API credentials configured'). The diagnostic script at the end adds useful but somewhat redundant content given the per-error bash snippets already provided.	2 / 3
Actionability	Every error includes the actual error message, root cause, and executable fix code (bash commands, TypeScript snippets). The diagnostic script is copy-paste ready, and fixes are concrete with specific API calls, configuration options, and code patterns.	3 / 3
Workflow Clarity	Each error follows a clear pattern (Error → Cause → Fix), and the escalation path provides a sequenced troubleshooting workflow. However, there are no explicit validation/verification steps after applying fixes — e.g., 'after changing the key, re-run the auth test to confirm' — which is important for diagnostic workflows.	2 / 3
Progressive Disclosure	The content is well-structured with clear headings and a logical reference format, but at ~200 lines it's a long monolithic file. Some errors (like rate limiting) reference other skills ('langfuse-rate-limits skill', 'langfuse-debug-bundle skill') which is good, but the main content could benefit from splitting detailed fixes into a separate reference file while keeping the SKILL.md as a quick-lookup index.	2 / 3
	Total	9 / 12 Passed

Description

89%

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

This is a well-structured skill description that clearly identifies its niche (Langfuse error troubleshooting), provides explicit trigger guidance, and uses appropriate third-person voice. Its main weakness is that the 'what' portion could be more specific about the concrete actions or error types it handles, rather than staying at the general 'diagnose and fix' level.

Suggestions

Add more specific concrete actions to improve specificity, e.g., 'resolve authentication errors, fix missing trace callbacks, debug SDK configuration, troubleshoot callback handler setup'.

Dimension	Reasoning	Score
Specificity	It names the domain (Langfuse errors/exceptions) and some actions (diagnose, fix, debug missing traces, troubleshoot integration issues), but doesn't list multiple specific concrete actions like 'resolve authentication errors, fix missing trace callbacks, configure SDK initialization'.	2 / 3
Completeness	Clearly answers both 'what' (diagnose and fix common Langfuse errors and exceptions) and 'when' (encountering Langfuse errors, debugging missing traces, troubleshooting integration issues), with an explicit 'Use when' clause and trigger phrases.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would actually say: 'langfuse error', 'fix langfuse', 'langfuse not working', 'debug langfuse', 'traces not appearing'. These are realistic phrases a user would type when encountering issues.	3 / 3
Distinctiveness Conflict Risk	Langfuse is a specific observability tool, making this highly distinctive. The trigger terms are all Langfuse-specific and unlikely to conflict with other skills unless there were multiple Langfuse-related skills.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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 — 9 / 11 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	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 00c0702

Reviewed: 2 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.