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

83%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Content

77%

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

This is a strong, actionable skill with executable code examples covering the full multi-environment setup lifecycle. The workflow is clearly sequenced with validation steps, and the safety/error tables provide useful reference. Minor weaknesses include some content redundancy between tables and a monolithic structure that could benefit from splitting provider-specific details into separate files.

Suggestions

Merge the 'Cross-Environment Safety' and 'Error Handling' tables into a single reference table to reduce redundancy

Consider extracting cloud-provider-specific secret management commands (AWS, GCP) into a separate referenced file to reduce the main file length

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with good use of tables and code blocks, but includes some redundancy between the error handling table and cross-environment safety table (overlapping concerns), and the environment strategy table partially duplicates what's in the code. The two troubleshooting tables at the end could be merged.	2 / 3
Actionability	Provides fully executable TypeScript code, concrete bash commands for secret management, complete GitHub Actions YAML, Zod validation schema, and specific .env file structures. All examples are copy-paste ready with realistic values and patterns.	3 / 3
Workflow Clarity	Clear 5-step sequential workflow from configuration through validation. Includes explicit validation checkpoints (Step 5 Zod validation, Step 1 credential validation with throw), fail-fast patterns, and the cross-environment safety table serves as a verification checklist against common risks.	3 / 3
Progressive Disclosure	The content is well-structured with clear sections and tables, but it's a fairly long monolithic file (~180 lines of content) with no bundle files to offload detail. The secret management examples for multiple providers (AWS, GCP) and the full CI/CD workflow could be split into referenced files for better organization.	2 / 3
	Total	10 / 12 Passed

Description

89%

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

This is a well-structured skill description with strong completeness and distinctiveness. It explicitly provides both 'Use when' and 'Trigger with' clauses, and targets a very specific niche (Langfuse environment configuration). The main weakness is that the capability description could be more specific about the concrete actions performed beyond 'configure' and 'set up'.

Suggestions

Add more specific concrete actions to the first sentence, e.g., 'Configure Langfuse across development, staging, and production environments, including setting API keys, configuring host URLs, managing project IDs, and handling environment variable files.'

Dimension	Reasoning	Score
Specificity	It names the domain (Langfuse multi-environment configuration) and some actions like 'setting up multi-environment deployments' and 'configuring per-environment keys', but doesn't list multiple concrete specific actions (e.g., what configuration steps, what files are modified, what outputs are produced).	2 / 3
Completeness	Clearly answers both 'what' (configure Langfuse across dev/staging/prod environments) and 'when' (explicit 'Use when' clause with specific scenarios, plus a 'Trigger with phrases' section listing concrete trigger terms).	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms including 'langfuse environments', 'langfuse staging', 'langfuse dev prod', 'langfuse environment setup', 'langfuse config by env', plus natural phrases like 'multi-environment deployments' and 'per-environment keys'. These are terms users would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — the combination of 'Langfuse' (a specific tool) with 'multi-environment configuration' creates a very clear niche. The explicit trigger phrases further reduce conflict risk with other 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 — 9 / 11 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	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 57b5254

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