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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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 code and clean organization, but loses points on conciseness (inline dual-version duplication) and workflow clarity (missing explicit validation checkpoints in the main flow).

Suggestions

Collapse the v4+ and v3-legacy setup blocks into one primary path and move the legacy variant into an 'Old patterns (v3)' section to reduce redundancy and version noise.

Add explicit validation checkpoints between steps — e.g., 'run a test trace and confirm the URL prints before continuing', and 'curl http://localhost:3000 and wait for 200 before creating API keys' for the self-hosted flow.

Resolve the small inconsistency where Step 6 calls initTracing() imported from ./lib/langfuse-dev but that module exports langfuse/logTrace and never defines initTracing.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and code-forward, but presents both v4+ and v3-legacy setup inline (Steps 2 and 3) with version-specific blocks not isolated in a deprecated/old-patterns section, adding redundancy that could be tightened.	2 / 3
Actionability	Provides fully executable TypeScript, package.json scripts, a docker-compose file, and env config that are copy-paste ready, matching the executable-and-complete anchor.	3 / 3
Workflow Clarity	Steps 1–6 are clearly sequenced with an error-handling table, but there are no explicit validation checkpoints (e.g., confirm traces appear before proceeding, verify the local instance is healthy) in the main workflow, capping clarity at 2 per the validation guideline.	2 / 3
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-organized with clear headers (Overview, Prerequisites, Steps, Optional, Error Handling, Resources, Next Steps) and no nested references, satisfying the simple-skill allowance for a 3.	3 / 3
	Total	10 / 12 Passed

Description

100%

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 across all dimensions: it states concrete capabilities, includes natural trigger phrases, explicitly covers both what and when, and occupies a distinct Langfuse-local-dev niche. No changes needed.

Dimension	Reasoning	Score
Specificity	Names concrete actions within a defined domain — 'hot reload and debugging', 'debugging traces', 'fast iteration loop' — matching the multiple-specific-actions anchor rather than the partial score-2 anchor.	3 / 3
Completeness	Explicitly answers both what ('Set up Langfuse local development workflow with hot reload and debugging') and when (an explicit 'Use when...' clause covering local dev, trace debugging, and iteration loops).	3 / 3
Trigger Term Quality	Provides natural, Langfuse-specific phrases a user would actually say ('langfuse local dev', 'langfuse hot reload', 'debug langfuse traces'), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The Langfuse-specific triggers carve out a clear niche unlikely to fire for unrelated skills, matching the distinct-triggers anchor.	3 / 3
	Total	12 / 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
Commit: 3022dd3

Reviewed: 1 day 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.