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

83

1.14x
Quality

Does it follow best practices?

Impact

96%

1.14x

Average score across 3 eval scenarios

SecuritybySnyk

Risky

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A code-dense, actionable production checklist with strong executable examples and a built-in verification script. Its main weaknesses are duplicated content between the body and the unreferenced implementation.md bundle and the absence of an explicitly sequenced, gated deployment workflow.

Suggestions

Replace the inline verification script with a brief summary and link to references/implementation.md (or move it to scripts/) to remove duplication and improve progressive disclosure.

Add a short numbered deployment workflow (configure -> verify -> deploy -> monitor) with explicit validation checkpoints so the sequence is unambiguous.

Add a clearly signaled pointer to references/implementation.md from the body, and reconcile the scripts/verify-langfuse-prod.ts reference with an actual file or remove the comment.

DimensionReasoningScore

Conciseness

The body is mostly code and checklists with no padding about concepts Claude already knows, but the full inline pre-deployment verification script (~65 lines) duplicates content that also appears in references/implementation.md, so it could be tightened.

2 / 3

Actionability

Provides fully executable TypeScript configs with concrete values (flushAt: 25, requestTimeout: 15000), a runnable verification script, and checklists with specific thresholds, making it copy-paste ready.

3 / 3

Workflow Clarity

Content is organized by topic (config, error handling, verification, checklist) and a verification script supplies a validation gate with a failure exit, but the overall deploy process is not laid out as an explicit numbered, gated step sequence with clear checkpoints.

2 / 3

Progressive Disclosure

A references/implementation.md bundle exists, but the body never links to it and instead inlines the same config, error-handling, and verification content; the code comment referencing scripts/verify-langfuse-prod.ts points to a non-existent path, so references are present but not clearly signaled.

2 / 3

Total

9

/

12

Passed

Description

90%

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 well-formed description with an explicit Use-when clause and concrete trigger phrases, clearly scoped to Langfuse production readiness. It is slightly more deliverable-oriented than action-oriented, keeping specificity just below the top anchor.

DimensionReasoningScore

Specificity

Names the domain and several actions ("preparing to deploy Langfuse to production", "validating production configuration", "auditing existing setup"), but the lead phrase "production readiness checklist and verification" describes a deliverable rather than listing concrete actions like the top anchor.

2 / 3

Completeness

Clearly states what the skill does ("Langfuse production readiness checklist and verification") and includes an explicit "Use when..." clause plus a "Trigger with phrases like" list, answering both what and when.

3 / 3

Trigger Term Quality

Explicitly enumerates natural phrases users would say ("langfuse production", "langfuse prod ready", "deploy langfuse", "langfuse checklist", "langfuse go live"), giving good coverage of likely trigger terms.

3 / 3

Distinctiveness Conflict Risk

The narrow Langfuse-production niche and dedicated triggers ("langfuse prod ready", "deploy langfuse", "langfuse go live") make it unlikely to fire for an unrelated skill.

3 / 3

Total

11

/

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.

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.