langfuse-prod-checklist
Langfuse production readiness checklist and verification. Use when preparing to deploy Langfuse to production, validating production configuration, or auditing existing setup. Trigger with phrases like "langfuse production", "langfuse prod ready", "deploy langfuse", "langfuse checklist", "langfuse go live".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill langfuse-prod-checklist85
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 excellent trigger term coverage and clear completeness. The main weakness is that the specificity of capabilities could be improved by listing concrete actions (e.g., 'verify API keys, check database connections, validate environment variables') rather than abstract terms like 'checklist' and 'verification'.
Suggestions
Add specific concrete actions that the checklist covers, such as 'verify API keys, check database connections, validate environment variables, review security settings'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Langfuse production) and mentions actions like 'checklist', 'verification', 'validating configuration', and 'auditing', but doesn't list specific concrete actions like what checks are performed or what configurations are validated. | 2 / 3 |
Completeness | Clearly answers both what (production readiness checklist and verification) and when (preparing to deploy, validating configuration, auditing setup) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases users would say: 'langfuse production', 'langfuse prod ready', 'deploy langfuse', 'langfuse checklist', 'langfuse go live' - these are realistic variations of how users would request this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Langfuse production deployment specifically. The combination of 'Langfuse' + 'production/deploy/checklist' creates distinct triggers 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 solid production checklist skill with excellent actionability - all code is executable and production-ready. The workflow is clear with explicit verification steps and error handling. The main weakness is length; some code examples (like the full metrics endpoint) could be referenced rather than inline to improve conciseness.
Suggestions
Consider moving the detailed implementation code (Steps 2-4) to separate reference files and keeping only the essential configuration and checklist in SKILL.md
Remove the redundant 'Final production Langfuse configuration' section at the end since it duplicates Step 1's configuration
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient with good use of tables and code examples, but includes some redundancy (e.g., similar configuration shown multiple times, metrics code that could be referenced rather than inline). The checklist tables are efficient, but the overall length could be tightened. | 2 / 3 |
Actionability | Excellent executable code examples throughout - production configuration, error handling wrapper, verification script, and monitoring endpoint are all copy-paste ready TypeScript. Specific recommended values are provided for all configuration options. | 3 / 3 |
Workflow Clarity | Clear 4-step workflow with explicit verification (Step 3 runs pre-deployment checks). The verification script includes pass/fail feedback and exits with error code on failure. Graceful shutdown is explicitly handled with signal handlers. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and tables, but the skill is quite long (~200 lines of code) and could benefit from splitting detailed implementations into separate files. References to external resources are present but the inline code could be externalized. | 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 | |
- 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.