CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Quality

83%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

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 comprehensive, copy-paste-ready bash script with built-in secret redaction. The primary weakness is that the large inline script and embedded template make the SKILL.md longer than necessary, and some sections (Prerequisites, explanatory table) add modest bloat.

Suggestions

Extract the main debug bundle script to a separate file (e.g., langfuse-debug.sh) in the bundle and reference it from SKILL.md to reduce inline bulk.

Remove the Prerequisites section — the script itself makes requirements self-evident, and Claude can infer these.

DimensionReasoningScore

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 'Current State' dynamic commands at the top which duplicate what the script does. The Error Handling table explaining why each item matters is useful context but adds bulk.

2 / 3

Actionability

The skill provides fully executable bash scripts that are copy-paste ready, including both a comprehensive debug bundle script and a quick inline diagnostic. The scripts handle edge cases (missing tools, redaction of secrets) and are complete with proper error handling via set -euo pipefail.

3 / 3

Workflow Clarity

The workflow is clearly sequenced: run script → review/redact → fill reproduction template → submit. Step 2 includes an explicit validation checkpoint (review before sharing) with a clear include/redact table. The feedback loop of reviewing bundle contents for leaked secrets before submission addresses the destructive risk of sharing sensitive data.

3 / 3

Progressive Disclosure

The content is reasonably well-structured with clear sections, but the large inline bash script (~70 lines) could benefit from being extracted to a bundle file. The reproduction template embedded in the script is also inline content that could be a separate referenced file. No bundle files are provided despite the content being substantial enough to warrant splitting.

2 / 3

Total

10

/

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 with strong trigger terms and clear when/what guidance. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., what logs are collected, what diagnostic steps are taken). The explicit trigger phrases and Langfuse-specific focus make it highly distinctive and easy for Claude to match correctly.

Suggestions

Add more specific concrete actions to the 'what' portion, e.g., 'Collects server logs, captures configuration state, exports trace data, and compiles environment details for Langfuse support tickets.'

DimensionReasoningScore

Specificity

The description names the domain (Langfuse debug evidence, support tickets) and some actions (collect, troubleshoot), but doesn't list specific concrete actions like 'gather log files, capture configuration state, export trace data, compile error reports'. The actions remain somewhat general.

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 combination of 'Langfuse' + 'debug/diagnostic/support bundle' creates a very specific trigger profile unlikely to conflict with other skills.

3 / 3

Total

11

/

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.

Validation9 / 11 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

9

/

11

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.