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".
79
76%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/langfuse-pack/skills/langfuse-migration-deep-dive/SKILL.mdQuality
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 description with strong completeness and excellent trigger term coverage. Its main weakness is that the capability description could be more specific about the concrete actions performed during migrations (e.g., trace export, schema mapping, configuration transfer). The Langfuse-specific focus makes it highly distinctive.
Suggestions
Add more specific concrete actions to improve specificity, e.g., 'Export traces and spans, map schemas between platforms, transfer API configurations, migrate prompt management data.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Langfuse migrations) and mentions some actions like 'data migration and platform changes', but doesn't list multiple specific concrete actions (e.g., schema mapping, trace export, API key migration, configuration transfer). | 2 / 3 |
Completeness | Clearly answers both 'what' (execute complex Langfuse migrations including data migration and platform changes) and 'when' (migrating from other observability platforms, moving between instances, major infrastructure migrations) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases like 'langfuse migration', 'migrate to langfuse', 'langfuse data migration', 'langfuse platform migration', 'switch to langfuse' — these are terms users would naturally say. Also includes 'observability platforms' as context. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Langfuse migrations — the combination of 'Langfuse' + 'migration' creates a very clear niche that is unlikely to conflict with other skills. The trigger terms are all Langfuse-specific. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at actionability and workflow clarity with fully executable migration scripts and a well-sequenced 5-step process including validation and rollback. However, it is significantly over-verbose—the full script bodies could be replaced with concise specifications or referenced as separate files, since Claude can generate pagination loops and console logging from brief instructions. The inline code bloat undermines token efficiency.
Suggestions
Replace full inline scripts with concise pseudocode specifications (e.g., 'Export traces, scores, prompts, datasets with pagination at 100/page, 200ms rate limit') and let Claude generate the full scripts on demand, or reference them as separate files.
Move the complete TypeScript files to referenced script files (e.g., 'See scripts/export-langfuse.ts') and keep only the key patterns and API calls inline in SKILL.md.
Remove repetitive patterns like the pagination boilerplate that appears identically for traces and scores—show it once and note it applies to all paginated endpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines with large code blocks that could be significantly condensed. The full export/import scripts include repetitive pagination patterns and console.log statements that inflate token count without adding proportional value. Claude could generate these scripts from much terser specifications. | 1 / 3 |
Actionability | The skill provides fully executable TypeScript scripts for each migration step—export, import, dual-write, validation, and cutover. Code is copy-paste ready with concrete API calls, environment variable patterns, and rate limiting included. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with explicit validation in Step 4 (comparing counts, checking variance), a feedback loop via the dual-write timeline (Week 1-4 progression), and a dedicated rollback plan. The validation step includes a concrete threshold (<5% variance) for proceeding. | 3 / 3 |
Progressive Disclosure | The skill includes external resource links at the bottom, but the body itself is monolithic—all code is inline rather than referenced from separate script files. The migration scenarios table and error handling table provide some structure, but the massive inline code blocks could be split into referenced files. | 2 / 3 |
Total | 9 / 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 | |
- Commit
4dee593
- 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.