langfuse-migration-deep-dive

Execute complex Langfuse migrations including data migration and platform changes. Use when migrating from other observability platforms, moving between Langfuse instances, or performing major infrastructure migrations. Trigger with phrases like "langfuse migration", "migrate to langfuse", "langfuse data migration", "langfuse platform migration", "switch to langfuse".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

The body is highly actionable with a well-sequenced, validated migration workflow. Its main weaknesses are verbosity from inline scripts that duplicate the reference file, and poor progressive disclosure since the reference is never referenced from the body.

Suggestions

Signal references/implementation.md from the body (e.g. 'See [implementation.md](references/implementation.md) for per-scenario detail') and move the duplicate per-scenario code out of SKILL.md.

Trim the inline export/import scripts to the essential pattern in the body, keeping full implementations in the reference file to reduce token cost.

Consider splitting the LangSmith-to-Langfuse adapter and dual-write class (currently only in the reference) so the body's scenario table is backed by clearly linked detail.

Dimension	Reasoning	Score
Conciseness	The body avoids concept-padding and assumes Claude's competence, but carries large inline export/import scripts that substantially duplicate content already present in references/implementation.md.	2 / 3
Actionability	Every step ships complete, executable TypeScript with concrete env vars, rate-limit handling, and copy-paste-ready commands.	3 / 3
Workflow Clarity	A clear Export -> Import -> Dual-write -> Validate -> Cutover sequence with an explicit validation step, variance thresholds, a rollback plan, and an error-handling table.	3 / 3
Progressive Disclosure	A reference file (references/implementation.md) exists but is never signaled or linked from the body, and per-scenario detail lives inline rather than being split out into the reference.	2 / 3
	Total	10 / 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 explicit what/when structure and strong natural trigger phrases. Its only weakness is that the stated capabilities ('data migration', 'platform changes') are somewhat abstract rather than enumerating concrete migration actions.

Dimension	Reasoning	Score
Specificity	Names the Langfuse migration domain and some actions ('data migration', 'platform changes') but these are high-level and not a comprehensive list of concrete actions.	2 / 3
Completeness	Explicitly answers both what ('Execute complex Langfuse migrations...') and when ('Use when migrating from other observability platforms...').	3 / 3
Trigger Term Quality	Lists five natural trigger phrases ('langfuse migration', 'migrate to langfuse', 'switch to langfuse') that users would plausibly say.	3 / 3
Distinctiveness Conflict Risk	Targets a clear Langfuse-migration niche with distinct triggers, unlikely to fire for unrelated 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 — 13 / 16 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
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

Reviewed: 1 day 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.