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".
85
83%
Does it follow best practices?
Impact
Pending
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 capability description is somewhat general — it says 'collect debug evidence' without specifying what concrete actions that entails (e.g., gathering logs, checking configurations, exporting traces). Overall it's a solid description that would perform well in skill selection.
Suggestions
Add more specific concrete actions to improve specificity, e.g., 'Gathers server logs, checks API connectivity, exports trace data, and captures configuration details for Langfuse debug evidence.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Langfuse debug evidence, support tickets, troubleshooting) and some actions (collect diagnostic information, prepare support tickets), but doesn't list multiple specific concrete actions like 'gather trace logs, export session data, capture configuration state'. | 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 coverage of natural trigger terms: 'langfuse debug', 'langfuse support bundle', 'collect langfuse logs', 'langfuse diagnostic', 'langfuse troubleshoot'. These are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — specifically scoped to Langfuse debug/diagnostic evidence collection. The 'Langfuse' qualifier and specific trigger phrases make it highly 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 strength is the completeness and copy-paste readiness of the bash scripts with proper secret redaction. The main weakness is that the inline script is quite long, making the skill somewhat heavy, and some content (like the reproduction template) could be referenced rather than inlined.
Suggestions
Consider moving the full debug bundle script to a separate referenced file (e.g., langfuse-debug.sh) and keeping only the quick inline diagnostic in the SKILL.md body.
Remove the Prerequisites section — Claude already knows these are needed from context.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The script is fairly comprehensive but includes some unnecessary elements like the reproduction template boilerplate and the prerequisites section (Claude knows what a bash shell is). The 'Current State' dynamic commands at the top are a nice touch but the overall content could be tightened. | 2 / 3 |
Actionability | Fully executable bash scripts with proper error handling (set -euo pipefail), concrete curl commands, specific redaction patterns, and a quick inline alternative. Everything is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence: run bundle → review/redact → submit → quick alternative. Step 2 explicitly includes a validation checkpoint (review for leaked secrets before sharing), and the redaction table provides a clear checklist for sensitive data handling. | 3 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the main debug script is quite long inline (~70 lines of bash). The reproduction template could be a separate file reference. The Error Handling table and Resources section are well-placed, but the skill is somewhat monolithic. | 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
c8a915c
- 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.