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".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
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 clearly specifies when to use the skill and provides explicit trigger phrases. The main weakness is that the capability description could be more concrete — listing specific actions like configuring API keys, setting up project IDs, or managing trace routing would strengthen specificity.
Suggestions
Add more concrete actions to the first sentence, e.g., 'Configure Langfuse API keys, project IDs, and trace routing across development, staging, and production environments' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Langfuse multi-environment configuration) and some actions like 'configuring per-environment keys' and 'implementing environment-specific configurations', but doesn't list multiple concrete distinct actions (e.g., setting up API keys, configuring endpoints, managing project IDs). | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Langfuse across dev/staging/prod environments, per-environment keys, environment-specific configs) and 'when' (explicit 'Use when' clause and 'Trigger with phrases' section providing clear activation guidance). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases like 'langfuse environments', 'langfuse staging', 'langfuse dev prod', 'langfuse environment setup', 'langfuse config by env' — these are terms users would naturally say when needing this skill, with good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Langfuse multi-environment configuration is a narrow, well-defined domain. The combination of 'Langfuse' + 'environments/staging/prod' makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
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 well-sequenced with validation checkpoints. The main weakness is that it's somewhat long for a single SKILL.md file—provider-specific secret management and CI/CD examples could be split into referenced files to improve progressive disclosure and reduce token cost.
Suggestions
Consider splitting provider-specific secret management (AWS, GCP) and CI/CD workflow examples into separate referenced files to reduce the main skill's token footprint.
Remove the error handling table or merge it with the cross-environment safety table, as they overlap significantly (e.g., cross-env data leak appears in both).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill 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 overview and prerequisites sections are reasonably lean. | 2 / 3 |
Actionability | Provides fully executable TypeScript code, bash commands for secret management, complete GitHub Actions workflow YAML, Zod validation schema, and concrete .env file examples. All code is copy-paste ready with specific library imports and realistic configurations. | 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 fail-fast behavior), error handling tables, and cross-environment safety mitigations. The workflow naturally builds from config → env files → secrets → CI/CD → validation. | 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). The secret management examples for multiple providers (AWS, GCP) and the full CI/CD workflow could be split into referenced files. The Resources section at the end provides external links but no internal file references for advanced topics. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%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 | |
- Commit
c8a915c
- Reviewed
Table of Contents
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.