migrating-dbt-core-to-fusion
Guides migration of dbt projects from dbt Core to the Fusion engine. Use when making a project compatible with Fusion, addressing deprecations, or running dbtf commands.
Install with Tessl CLI
npx tessl i github:dbt-labs/dbt-agent-skills --skill migrating-dbt-core-to-fusion88
Quality
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 skill description with clear 'what' and 'when' clauses, good trigger terms specific to the dbt/Fusion ecosystem, and a distinct niche. The main weakness is that the capabilities could be more specific about what concrete migration actions the skill performs beyond the general 'guides migration' framing.
Suggestions
Add more specific concrete actions like 'converts legacy macros', 'updates configuration files', or 'resolves breaking changes' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (dbt migration to Fusion) and some actions ('migration', 'addressing deprecations', 'running dbtf commands'), but lacks comprehensive concrete actions like specific migration steps or transformation tasks. | 2 / 3 |
Completeness | Clearly answers both what ('Guides migration of dbt projects from dbt Core to the Fusion engine') and when ('Use when making a project compatible with Fusion, addressing deprecations, or running dbtf commands') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'dbt', 'dbt Core', 'Fusion', 'deprecations', 'dbtf commands', 'migration', 'compatible'. These are terms a user migrating dbt projects would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting dbt Core to Fusion migration specifically. The combination of 'dbt', 'Fusion engine', and 'dbtf commands' creates a distinct trigger profile unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%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, well-structured migration skill with excellent workflow clarity and actionability. The multi-step process includes explicit validation checkpoints, concrete commands, and helpful example fixes. The main weakness is some redundancy in resource listings and verbose external URL documentation that could be consolidated.
Suggestions
Consolidate the three separate resource listings (Additional Resources, inline references, and Resources section) into a single, well-organized reference section to reduce redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy—the resources are listed multiple times (in 'Additional Resources', 'Resources' section, and inline references), and some explanations could be tightened. The external URL list at the end is verbose. | 2 / 3 |
Actionability | Provides fully executable commands (dbtf debug, dbtf parse, uvx dbt-autofix), concrete code examples for fixes, and copy-paste ready templates. Each step has specific terminal commands to run. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit validation checkpoints (run dbtf parse after each step), clear success criteria ('0 errors'), a progress checklist, and feedback loops for error recovery. The decision tree for unsupported features adds clarity. | 3 / 3 |
Progressive Disclosure | Well-structured with a clear overview, progress checklist upfront, and one-level-deep references to detailed materials in the references/ directory. Content is appropriately split between quick-start workflow and detailed reference files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
87%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- 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.