langfuse-debug-bundle
Collect Langfuse debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Langfuse problems. Trigger with phrases like "langfuse debug", "langfuse support bundle", "collect langfuse logs", "langfuse diagnostic", "langfuse troubleshoot".
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
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 with strong trigger terms and clear 'what/when' guidance. Its main weakness is that the capabilities described are somewhat general ('collect debug evidence') without specifying the concrete actions involved (e.g., gathering logs, checking configurations, exporting traces). The distinctiveness is excellent due to the Langfuse-specific focus.
Suggestions
Add more specific concrete actions to improve specificity, e.g., 'Collects Langfuse logs, checks service configuration, captures trace data, and verifies connectivity for support tickets and troubleshooting.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Langfuse debug evidence) and a general action (collect debug evidence for support tickets and troubleshooting), but does not list multiple specific concrete actions like 'gather logs, capture configuration, export trace data, check service health'. | 2 / 3 |
Completeness | Clearly answers both 'what' (collect Langfuse debug evidence for support tickets and troubleshooting) and 'when' (encountering persistent issues, preparing support tickets, collecting diagnostic information) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent trigger term coverage with explicit natural phrases: 'langfuse debug', 'langfuse support bundle', 'collect langfuse logs', 'langfuse diagnostic', 'langfuse troubleshoot'. These are terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Langfuse-specific debug/diagnostic collection. The specific product name 'Langfuse' combined with 'debug evidence' and 'support bundle' makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%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, actionable skill with executable scripts and a clear workflow for collecting Langfuse debug information. Its main weakness is that the large inline bash script and reproduction template inflate the SKILL.md when they could be separate bundle files, and some sections (Prerequisites, parts of Error Handling) add tokens without proportional value.
Suggestions
Extract the main bash script to a bundle file (e.g., langfuse-debug.sh) and reference it from SKILL.md to reduce inline bulk.
Remove the Prerequisites section — the script's error handling already accounts for missing tools, and Claude can infer requirements from the code.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary elements like the Prerequisites section (Claude knows what's needed from the script itself) and the Error Handling table which largely restates obvious information. The reproduction template embedded inline adds bulk that could be generated on-the-fly. | 2 / 3 |
Actionability | Fully executable bash scripts are provided — both the comprehensive debug bundle script and the quick inline diagnostic. Commands are copy-paste ready with proper error handling, redaction logic, and real API endpoints. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence: run script → review/redact → submit → quick alternative. The redaction review step (Step 2) serves as an explicit validation checkpoint before sharing sensitive data. The script itself has built-in redaction as a safety measure. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but the 60+ line bash script dominates the file and could be extracted to a separate bundled script file. The reproduction template is also inline when it could be a referenced file. No bundle files are provided despite the content being long enough to benefit from splitting. | 2 / 3 |
Total | 10 / 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.