Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/langfuse-migration-deep-dive
Execute complex Langfuse migrations including data migration and platform changes.
Passed 16 of 20 test cases with the skill, and 9 of 20 without it.
and 10 more in the full report
9 fixed9 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
What step is required in the application telemetry code when cutting over from dual-writing to target-only writing after the dual-write validation period passes?
| Checked | Without skill | With skill |
|---|---|---|
| Removes source span processor from NodeSDK configuration so only target processor remains. | Missed | Passed |
The instructions your model reads when the skill loads.
!npm list langfuse @langfuse/client 2>/dev/null | head -5 || echo 'No langfuse packages'
Comprehensive guide for complex migrations: cloud-to-self-hosted, LangSmith-to-Langfuse, cross-instance data migration, and zero-downtime dual-write patterns.
| Scenario | Complexity | Downtime | Data Loss Risk |
|---|---|---|---|
| Cloud to Cloud (different project) | Low | None | None |
| Cloud to Self-hosted | Medium | Minutes | Low |
| Self-hosted to Cloud | Medium | Minutes | Low |
| LangSmith to Langfuse | High | Hours | Medium |
| SDK v3 to v4+ (no data migration) | Low | None | None |
// scripts/export-langfuse.ts
import { LangfuseClient } from "@langfuse/client";
import { writeFileSync, mkdirSync } from "fs";
const source = new LangfuseClient({
publicKey: process.env.SOURCE_LANGFUSE_PUBLIC_KEY,
secretKey: process.env.SOURCE_LANGFUSE_SECRET_KEY,
baseUrl: process.env.SOURCE_LANGFUSE_BASE_URL,
test cases passed, vs 9 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.