CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

74

1.75x
Quality

79%

Does it follow best practices?

Impact

65%

1.75x

Average score across 2 eval scenarios

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/langfuse-pack/skills/langfuse-prod-checklist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

The content is actionable and reasonably well-sequenced with a built-in pre-deploy verification step, but it loses conciseness and progressive-disclosure points because the same code appears both inline and in an unreferenced, duplicative bundle file.

Suggestions

Link references/implementation.md from the body (e.g., 'See [implementation.md](references/implementation.md) for full code') and keep only essential snippets inline, removing the duplicated blocks.

De-duplicate: keep one canonical version of each config/error-handling/verify block rather than repeating it across SKILL.md and the reference file.

Tighten the verification script in the body to the check list and results logic, pointing to the reference for the full executable file, to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but large TypeScript blocks (config, error handling, the full verification script) are duplicated nearly verbatim in references/implementation.md, padding token use without adding value.

3 / 5

Actionability

Provides concrete, mostly executable TypeScript code (v3 and v4+ configs, error wrapping, a runnable verify script) plus a specific troubleshooting table; minor gaps such as undefined imports and assumed scaffolding keep it just below copy-paste-perfect.

4 / 5

Workflow Clarity

A clear sequence is implied (prerequisites -> configure -> run verification -> checklist), and the pre-deployment verification script acts as an explicit validation checkpoint with pass/fail exit behavior.

4 / 5

Progressive Disclosure

A reference bundle (references/implementation.md) exists but is never linked from the body, and its content largely duplicates the inline blocks instead of cleanly splitting detail out, so navigation and structure are only partially realized.

3 / 5

Total

14

/

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.

The description is strong: it states concrete capabilities, gives explicit 'Use when' guidance with multiple natural trigger phrases, and occupies a distinct niche. Minor room to tighten the action list from general to fully enumerated.

DimensionReasoningScore

Specificity

Names the Langfuse production domain plus several concrete actions ('checklist and verification', 'preparing to deploy', 'validating production configuration', 'auditing existing setup'), but coverage is somewhat general rather than enumerating many specific operations.

4 / 5

Completeness

Explicitly answers both what ('Langfuse production readiness checklist and verification') and when ('Use when preparing to deploy Langfuse to production, validating production configuration, or auditing existing setup') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides multiple natural phrases a user would actually say ('langfuse production', 'langfuse prod ready', 'deploy langfuse', 'langfuse checklist', 'langfuse go live'), giving comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Langfuse production deployment) with distinct triggers, making conflict with other skills minimal.

5 / 5

Total

19

/

20

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.