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

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.

The content is highly actionable with executable code and a clear, validated workflow, but it is token-heavy due to a large inline script and duplicated diagnostic checks, and it misses progressive-disclosure opportunities by inlining material that belongs in a bundled script file.

Suggestions

Move the Step 1 debug script into a bundled scripts/langfuse-debug.sh file and reference it one level deep, keeping only a short usage snippet inline in SKILL.md to improve conciseness and progressive disclosure.

De-duplicate the environment/SDK/network checks that appear in both the "Current State" dynamic blocks and Step 1/Step 4 to reduce token cost.

Tighten the inline script by trimming redundant comments and consolidating the network/env sections now that a quick-check path exists in Step 4.

DimensionReasoningScore

Conciseness

The body embeds a ~110-line bash script inline and duplicates environment/SDK/network checks across the "Current State" dynamic blocks, Step 1, and Step 4. It is actionable and free of concept-explaining fluff (above 1) but is not lean enough for a 3 because the script and several checks could be tightened or de-duplicated.

2 / 3

Actionability

Provides fully executable, copy-paste-ready bash (curl health/auth checks, npm/pip version checks, redaction sed, tar packaging) plus a concrete quick-diagnostic block and a precise redaction table — concrete and specific throughout.

3 / 3

Workflow Clarity

Steps 1–4 are clearly sequenced with an explicit validation checkpoint (Step 2 "Always redact before submitting" and Step 3 "Review bundle contents for leaked secrets") placed between generation and submission, serving as the feedback loop for this log-collection/shipping workflow.

3 / 3

Progressive Disclosure

No bundle files exist (references/scripts/assets absent) and the entire debug script is inlined monolithically in SKILL.md rather than split into a one-level-deep scripts/ file. Sections are well-organized (above 1) but content that should be separate is inline, so it does not reach the well-signaled one-level-deep reference structure of a 3.

2 / 3

Total

10

/

12

Passed

Description

90%

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

The description is well-structured with explicit "what" and "when" guidance plus strong, natural trigger phrases. Its only weakness is specificity, since it describes one composite action rather than enumerating multiple distinct capabilities.

DimensionReasoningScore

Specificity

Names the domain and a concrete action ("Collect Langfuse debug evidence for support tickets and troubleshooting") but stays at a single high-level action rather than listing multiple specific concrete actions. It is not vague (so above 1) but not comprehensive enough for a 3.

2 / 3

Completeness

Explicitly answers both what ("Collect Langfuse debug evidence for support tickets and troubleshooting") and when ("Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information…") plus explicit trigger phrases.

3 / 3

Trigger Term Quality

Provides five natural trigger phrases a user would say ("langfuse debug", "langfuse support bundle", "collect langfuse logs", "langfuse diagnostic", "langfuse troubleshoot"), giving good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (Langfuse debugging) with distinctive langfuse-prefixed triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 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

14

/

16

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.