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".
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 solid skill description with excellent trigger term coverage and completeness, clearly answering both what and when. Its main weakness is that the capability description could be more specific about the concrete actions performed during migrations (e.g., schema mapping, trace export, configuration transfer) rather than staying at a somewhat abstract level.
Suggestions
Add more specific concrete actions to the first sentence, e.g., 'Export traces and spans, map schemas between platforms, transfer API configurations, and validate migrated 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 mentions 'observability platforms' and 'infrastructure migrations' as contextual triggers. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Langfuse migrations — the repeated use of 'Langfuse' and migration-specific terminology makes it very unlikely to conflict with other skills. Clear niche with distinct triggers. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable migration guide with clear step-by-step workflows, validation checkpoints, and rollback procedures. Its main weakness is verbosity — the inline code blocks are extensive and repetitive, making the document quite long when the scripts could be referenced as separate files. The error handling table and migration scenario matrix add practical value.
Suggestions
Extract the export, import, and validation scripts into separate referenced files (e.g., scripts/export-langfuse.ts) and reference them from SKILL.md to improve progressive disclosure and reduce inline bulk.
Consolidate the repetitive pagination pattern in the export script into a reusable helper function to reduce code duplication and token usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with extensive code blocks that could be more concise. Some code comments are helpful but the overall volume is high — the export/import scripts are quite verbose with repetitive pagination patterns that could be abstracted. However, it doesn't waste tokens explaining basic concepts Claude already knows. | 2 / 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 built in. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with logical ordering (export → import → dual-write → validate → cutover). Step 4 is an explicit validation checkpoint with variance thresholds, and there's a dedicated rollback plan and error handling table. The dual-write timeline provides a phased approach with clear milestones. | 3 / 3 |
Progressive Disclosure | The skill is a monolithic document with all code inline — the export and import scripts are lengthy and could be split into separate referenced files. External resource links are provided at the end, but the main content would benefit from being split into separate script files with the SKILL.md serving as an overview with references. | 2 / 3 |
Total | 10 / 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
23fe3bf
- 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.