langfuse-performance-tuning

Optimize Langfuse tracing performance for high-throughput applications. Use when experiencing latency issues, optimizing trace overhead, or scaling Langfuse for production workloads. Trigger with phrases like "langfuse performance", "optimize langfuse", "langfuse latency", "langfuse overhead", "langfuse slow".

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and token-efficient, with executable code and concrete tuning values throughout. It loses points for missing explicit post-change validation checkpoints and for keeping full scripts inline rather than offloading them to bundle files.

Suggestions

Add an explicit validation step after the tuning changes (e.g. "Re-run scripts/benchmark-langfuse.ts and confirm P95/overhead hit the Performance Targets table") to close the workflow feedback loop.

Move the larger code blocks (benchmark, TraceSampler) into a scripts/ bundle and reference them from the body, reducing inline bulk and improving progressive disclosure.

Confirm the referenced scripts/benchmark-langfuse.ts file is actually included in the bundle, or remove the path comment to avoid a dangling reference.

Dimension	Reasoning	Score
Conciseness	Lean, code-forward content with no padding of concepts Claude already knows; brief prose such as "Large trace payloads slow down flush and increase costs" earns its place and assumes competence.	3 / 3
Actionability	Each of the six steps ships fully executable TypeScript with concrete configuration values and tuning tables (e.g. exportIntervalMillis: 10000, batch size 50-100), making the guidance copy-paste ready.	3 / 3
Workflow Clarity	The six steps are clearly sequenced and titled, but the batch/tuning workflow lacks an explicit validation checkpoint (e.g. "re-run the benchmark to confirm improvement") between changes; verification is only implicit via the upfront benchmark and the reactive Error Handling table.	2 / 3
Progressive Disclosure	Sections are well-organized with headers and an external Resources list, but the ~250-line body is monolithic with full inline scripts (benchmark, sampler) that could be split out; no references/scripts/assets bundle files exist, and the code comment referencing scripts/benchmark-langfuse.ts points to a file that is not bundled.	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-constructed with explicit what/when guidance and natural trigger phrases tightly scoped to a clear niche. Its only weakness is that the capability statement is a single broad action rather than an enumeration of concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain and a concrete action ("Optimize Langfuse tracing performance for high-throughput applications") but offers a single broad action rather than a list of multiple specific concrete actions like the score-3 anchor.	2 / 3
Completeness	Explicitly answers both what ("Optimize Langfuse tracing performance...") and when ("Use when experiencing latency issues, optimizing trace overhead, or scaling Langfuse for production workloads") with explicit trigger guidance.	3 / 3
Trigger Term Quality	Provides natural phrases a user would actually say — "langfuse performance", "langfuse latency", "langfuse overhead", "langfuse slow", "optimize langfuse" — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	A clear niche (Langfuse tracing performance tuning) with distinct, domain-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/langfuse-pack/skills/langfuse-performance-tuning/SKILL.md
Commit: b2e8c53

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.