langfuse-multi-env-setup

Configure Langfuse across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment keys, or implementing environment-specific Langfuse configurations. Trigger with phrases like "langfuse environments", "langfuse staging", "langfuse dev prod", "langfuse environment setup", "langfuse config by env".

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

82%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 highly actionable, well-structured skill body with copy-paste-ready code for all environments. Its main weaknesses are slight redundancy between the safety/error tables and a missing explicit post-deploy verification step in the CI/CD workflow.

Suggestions

Add an explicit post-deploy verification checkpoint in Step 4 (e.g., confirm traces land in the correct Langfuse project and no dev data appears in prod) to strengthen the workflow's feedback loop.

Consolidate the Cross-Environment Safety and Error Handling tables, or trim redundant mitigations that already appear in Step 1, to reduce token overlap.

Consider moving the full env-config module and CI/CD workflow into scripts/ or references/ bundle files, leaving SKILL.md as a tighter overview, to better leverage progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Lean body that jumps to executable code without explaining concepts Claude already knows, but the Cross-Environment Safety and Error Handling tables overlap and restate mitigations already shown in Step 1, which could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready code and commands across all five steps (TypeScript config module, env files, AWS/GCP secret commands, GitHub Actions workflow, Zod schema) covering dev/staging/prod.	5 / 5
Workflow Clarity	Steps 1-5 form a clear sequenced process with a startup validation checkpoint (Zod fail-fast) and credential checks, but the CI/CD deployment step lacks an explicit post-deploy verification feedback loop, leaving a minor validation gap for a batch operation.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and self-contained with no nested references, but content that could be offloaded to bundle files (the env-config module, CI/CD workflow) is inlined and the body exceeds the simple-skill size threshold.	4 / 5
	Total	17 / 20 Passed

Description

95%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, well-constructed description that clearly states what the skill does, when to use it, and provides natural trigger phrases. It is specific, distinctive, and concise without padding.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions (configure across envs, set up multi-env deployments, configure per-env keys, implement env-specific configs) in a named domain, with only minor breadth gaps since all actions revolve around multi-environment config rather than distinct capabilities.	4 / 5
Completeness	Explicitly answers both 'what' (configure Langfuse across dev/staging/prod with per-env keys and configs) and 'when' ('Use when setting up multi-environment deployments...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Provides comprehensive natural trigger phrases a user would actually say ('langfuse environments', 'langfuse staging', 'langfuse dev prod', 'langfuse environment setup', 'langfuse config by env'), including multiple synonyms and variations.	5 / 5
Distinctiveness Conflict Risk	Targets a narrow, specific niche (multi-environment Langfuse deployment) with distinct trigger phrases, minimizing overlap with other Langfuse skills that would target different tasks.	5 / 5
	Total	19 / 20 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-multi-env-setup/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.