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

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/langfuse-pack/skills/langfuse-performance-tuning/SKILL.md

Quality

Content

76%Weight 40%Scale 1-5

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

A well-structured, highly actionable performance-tuning skill with executable code and concrete tuning matrices throughout. Its main gap is the absence of an explicit before/after validation checkpoint in the workflow, which is important for batch/performance work; progressive disclosure is solid but slightly limited by inlined code and a non-existent referenced script path.

Suggestions

Add a validation checkpoint after the optimization steps: 'Re-run scripts/benchmark-langfuse.ts and compare P50/P95/flush against the Performance Targets table; iterate until targets are met.'

Either provide the referenced scripts/benchmark-langfuse.ts as a real bundle file or remove the path comment to avoid a dangling reference.

Consider moving the larger code blocks (e.g. the sampler and truncation helpers) into a scripts/ or references/ bundle and linking from SKILL.md to improve progressive disclosure for this 250-line skill.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — code-first steps, compact config tables, and short orienting sentences ('Large trace payloads slow down flush and increase costs') — with only minor over-explanation that could be trimmed; it never pads concepts Claude already knows.	4 / 5
Actionability	Every step ships complete, copy-paste-ready TypeScript with concrete values (exportIntervalMillis: 10000, flushAt: 100) and a tuning matrix with specific numbers per volume tier, fully covering the common cases.	5 / 5
Workflow Clarity	The six steps are clearly sequenced (benchmark -> batch -> non-blocking -> payload -> sampling -> memory), but for a batch/performance-tuning skill there is no explicit validation checkpoint that says 're-run the benchmark and compare against the Performance Targets', which caps this dimension per the batch-operation feedback-loop rule.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections with external references cleanly signaled in the Resources section (one level deep); however all large code blocks are inlined and a code comment references scripts/benchmark-langfuse.ts without an actual bundle file present, a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

82%Weight 40%Scale 1-5

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

A strong, clearly-scoped description that explicitly states both purpose and triggering conditions with natural user phrases and a distinct niche. The only weakness is that the action vocabulary is somewhat narrow ('Optimize' as the sole verb) while the rest of the text frames when-to-use rather than what-it-does.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Langfuse tracing performance') and one concrete action ('Optimize'), but the remaining phrases ('latency issues, optimizing trace overhead, scaling Langfuse') describe trigger contexts rather than distinct capabilities, so coverage is not comprehensive.	3 / 5
Completeness	It explicitly answers both what ('Optimize Langfuse tracing performance for high-throughput applications') and when ('Use when experiencing latency issues... or scaling Langfuse for production workloads') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	It lists five natural phrases a user would say ('langfuse performance', 'optimize langfuse', 'langfuse latency', 'langfuse overhead', 'langfuse slow'), giving good keyword coverage, though a few natural variations (e.g. 'tracing slow', 'langfuse throughput') are absent.	4 / 5
Distinctiveness Conflict Risk	Every trigger is Langfuse-prefixed and the niche (tracing performance tuning for a specific product) is distinct, giving minimal conflict risk with other skills.	5 / 5
	Total	17 / 20 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: 8585d6d

Reviewed: 13 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.