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".
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/langfuse-pack/skills/langfuse-common-errors/SKILL.mdQuality
Discovery
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 with realistic user phrases, and answers both what and when. The main weakness is that the capability description could be more specific about the concrete actions it performs (e.g., specific error types, configuration fixes, SDK issues).
Suggestions
Add more specific concrete actions beyond 'diagnose and fix' — e.g., 'resolve authentication errors, fix SDK configuration, troubleshoot missing or incomplete traces, debug callback handler setup'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | 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 resolving auth errors, fixing SDK configuration, or handling specific exception types. | 2 / 3 |
Completeness | Clearly answers both 'what' (diagnose and fix common Langfuse errors and exceptions) and 'when' (explicit 'Use when' clause with triggers, plus a 'Trigger with phrases like' section providing concrete examples). | 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 Langfuse issues. | 3 / 3 |
Distinctiveness Conflict Risk | Langfuse is a very specific tool/product, 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 |
Implementation
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, highly actionable troubleshooting reference with real error messages and executable fixes for each common Langfuse issue. Its main weaknesses are the lack of explicit verification steps after applying fixes (e.g., 'confirm the fix worked by running X') and the monolithic structure that could benefit from progressive disclosure into supporting files. The content is mostly concise but could trim some obvious prerequisites and minor redundancies.
Suggestions
Add a brief verification step after each fix (e.g., 'Re-run the auth test above to confirm the new key works') to close the feedback loop — this is critical for debugging workflows.
Consider splitting the 10 error entries into a separate ERRORS_REFERENCE.md and keeping SKILL.md as a concise overview with a quick-lookup table mapping error messages to solutions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with real error messages and targeted fixes, but some sections include minor redundancy (e.g., the prerequisites section states obvious things like 'API credentials configured'). The diagnostic script at the end adds value but the overall document is lengthy for a reference skill. | 2 / 3 |
Actionability | Excellent actionability throughout — every error includes the actual error message, root cause, and executable code/commands to diagnose and fix. The bash scripts use `set -euo pipefail`, the TypeScript examples are copy-paste ready, and the diagnostic script is fully executable. | 3 / 3 |
Workflow Clarity | Each error follows a clear pattern (Error → Cause → Fix), and the escalation path provides a sequenced 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 debugging workflows. | 2 / 3 |
Progressive Disclosure | The document is well-structured with numbered sections and a clear table-of-contents-like flow, but it's a monolithic ~200-line file with no content split into supporting files. The references to external skills ('langfuse-debug-bundle', 'langfuse-rate-limits') are good signals, but the inline detail for 10 errors could benefit from being split into a separate reference file with the SKILL.md providing a quick lookup overview. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%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 | |
- Commit
a04d1a2
- 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.