langfuse-local-dev-loop

Set up Langfuse local development workflow with hot reload and debugging. Use when developing LLM applications locally, debugging traces, or setting up a fast iteration loop with Langfuse. Trigger with phrases like "langfuse local dev", "langfuse development", "debug langfuse traces", "langfuse hot reload", "langfuse dev workflow".

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/langfuse-pack/skills/langfuse-local-dev-loop/SKILL.md

Quality

Content

65%

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 complete, executable examples and a clear step sequence. Its main weaknesses are conciseness (parallel v4/v3 setup and inline docker-compose inflate length) and the lack of explicit validation checkpoints and external file splitting for a skill this size.

Suggestions

Add an explicit verification checkpoint after setup, e.g. 'Run a traced call and confirm the trace URL prints / appears in the Langfuse UI before proceeding'.

Move the v3 Legacy setup and the docker-compose self-hosting block into separate reference files (e.g. legacy-v3.md, self-hosted.md) and link to them from the main flow to improve progressive disclosure and conciseness.

Tighten the dual SDK-version setup by leading with the current v4+ path and summarizing v3 as a short fallback note rather than two full parallel code blocks.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code with no concept-padding Claude already knows, but at ~225 lines it carries redundancy (full parallel v4+ and v3 Legacy setups) and an inline docker-compose block that could be tightened, so it is 'mostly efficient but could be tightened' rather than fully lean.	2 / 3
Actionability	It provides copy-paste-ready, executable TypeScript, package.json scripts, docker-compose, and bash commands with concrete env values, matching the 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	Steps are clearly sequenced (Step 1-6) and an Error Handling table offers recovery, but there is no explicit validation checkpoint (e.g. 'verify traces appear in the Langfuse UI') after setup, so checkpoints are implicit rather than explicit.	2 / 3
Progressive Disclosure	Sections are well-organized, but the skill is a monolithic 225-line file with no bundle files; content that could be separate (the v3 legacy setup, the docker-compose self-hosting block) is inline, fitting 'some structure but content that should be separate is inline'.	2 / 3
	Total	9 / 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 strong: it states what the skill does, when to use it, and gives natural trigger phrases tied to a distinct Langfuse-local-dev niche. The only mild weakness is specificity, where it names the domain and a few features rather than enumerating many discrete concrete actions.

Dimension	Reasoning	Score
Specificity	It names the domain and a couple of actions ('hot reload and debugging', 'fast iteration loop'), but does not list multiple distinct concrete actions like the score-3 anchor; it is closer to 'names domain and some actions, but not comprehensive'.	2 / 3
Completeness	It explicitly answers what ('Set up Langfuse local development workflow with hot reload and debugging') and when ('Use when developing LLM applications locally, debugging traces...'), plus explicit trigger phrases, matching the score-3 anchor.	3 / 3
Trigger Term Quality	It supplies several natural phrases a user would say ('langfuse local dev', 'debug langfuse traces', 'langfuse hot reload', 'langfuse dev workflow'), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The Langfuse local-dev niche with version-specific, product-named triggers makes it clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 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

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/langfuse-pack/skills/langfuse-local-dev-loop/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.