CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

migrating-dbt-core-to-v2

Use when a user needs help triaging dbt-core to dbt v2 migration errors. Runs dbt-autofix first, then classifies remaining errors into actionable categories (auto-fixable, guided fixes, needs input, blocked).

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is dbt-labs/dbt-agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

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

The body delivers an exceptionally clear, enforced workflow with executable commands, concrete error-code mappings, and strong validation feedback loops, backed by a well-structured one-level-deep reference bundle. The main weakness is redundancy: repeated dbt1065 guidance and a recap-heavy Important Notes section inflate token cost without adding new information.

Suggestions

Remove the duplicated dbt1065 'ignore these warnings' paragraph — it appears nearly verbatim in both 'Hard rules' and 'Important Notes'; state it once.

Cut or drastically trim the 'Important Notes' section: most bullets restate rules already covered in 'Mandatory execution order', 'Step 1', and 'Progressive Fixing Approach'.

Move the full Category A/B pattern lists and the 'Presenting Findings' / 'Track progress' templates into references/ (e.g. classification-categories.md or a new presentation.md), keeping only a summary and links in SKILL.md to tighten progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient, but the dbt1065 'ignore these warnings' guidance appears twice nearly verbatim (Hard rules and Important Notes), and the Important Notes section restates rules already given in the workflow sections (autofix first, review diffs, validate after each fix, suggest dbt debug). This is more than minor trimmable material, so it sits at the 'mostly efficient but could be tightened' anchor rather than 4.

3 / 5

Actionability

Fully executable guidance throughout: copy-paste commands (dbt debug, uvx --from git+...dbt-autofix deprecations, git stash create), exact error-code-to-fix mappings (e.g. dbt1501: config.require('meta').key to config.meta_require('key')), a concrete WebFetch GitHub-search URL template, and ready-to-use output format templates. Common cases are covered.

5 / 5

Workflow Clarity

Mandatory numbered execution order with hard rules, a violation-recovery protocol ('acknowledge the violation... execute that step now'), and an explicit validate-fix-retry feedback loop ('After EVERY fix, re-run the repro command'), plus handling for cascading errors and same-node latent duplicates. This matches the anchor-5 checklist pattern.

5 / 5

Progressive Disclosure

Three reference files are well signaled, one level deep, indexed by a README, and every in-body anchor (case-sensitive-identifier-mismatches, verifying-against-the-real-warehouse..., guardrail-...) resolves to a real heading. Kept at 4 rather than 5 because the body retains full category pattern lists and presentation templates inline and duplicates guidance across sections — a minor organization gap rather than a clean overview-plus-references split.

4 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

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 strong description: explicit 'Use when...' trigger, concrete what-statement, and enumerated output categories. Trigger coverage is good though a few common synonyms ('upgrade', 'dbt-fusion') are absent.

DimensionReasoningScore

Specificity

Names the domain and lists concrete actions — 'Runs dbt-autofix first, then classifies remaining errors into actionable categories (auto-fixable, guided fixes, needs input, blocked)' — with the four categories enumerated. Falls short of a 5 because other capabilities (credential validation, GitHub issue search, the fix/validate workflow) are not covered.

4 / 5

Completeness

Explicitly answers both what ('Runs dbt-autofix first, then classifies remaining errors into actionable categories') and when ('Use when a user needs help triaging dbt-core to dbt v2 migration errors') with a concrete trigger phrase — the anchor-5 pattern.

5 / 5

Trigger Term Quality

'triaging dbt-core to dbt v2 migration errors' supplies natural terms users would say (dbt, dbt-core, v2, migration errors). A few natural variations are missing (e.g. 'upgrade', 'dbt-fusion', specific error codes), matching the 'good coverage, a few natural terms missing' anchor rather than comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

dbt v2 migration triage is a clear niche with distinct triggers; no realistic overlap with other skills, so conflict risk is minimal.

5 / 5

Total

18

/

20

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

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

dbt-labs/dbt-agent-skills

Path

skills/dbt-migration/skills/migrating-dbt-core-to-v2/SKILL.md

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.