CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

running-dbt-commands

Formats and executes dbt CLI commands, selects the correct dbt executable, and structures command parameters. Use when running models, tests, builds, compiles, or show queries via dbt CLI. Use when unsure which dbt executable to use or how to format command parameters.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

90%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.

A lean, highly actionable CLI reference with executable commands throughout and real validation guidance (list-before-run, run_results.json inspection, selector-typo guards). It falls short of top marks only on structure: the validation steps are not consolidated into an explicit workflow, and some exhaustive lookup tables could be split into a reference file.

Suggestions

Add a short numbered 'Standard workflow' section consolidating the existing checkpoints (preview with `dbt list --select …` → run `dbt build` with warn-error-options → inspect `target/run_results.json` for failures), turning scattered validation guidance into an explicit feedback loop.

Move the exhaustive `--output json` key list and valid resource-type enumeration into a reference file (e.g. `references/list-output.md`) and keep a few common examples inline, slimming the main body toward quick-reference size.

State explicitly in the workflow that on `fail`/`error` status the next step is to re-run the failing node with `dbt build --select <node>` after fixing, closing the error-recovery loop the run_results.json section currently leaves implicit.

DimensionReasoningScore

Conciseness

The body is dense tables and copy-paste command blocks with no explanation of concepts Claude already knows — preferences, a quick reference, and per-topic command snippets where every token earns its place.

5 / 5

Actionability

Commands like "dbt build --select my_model --quiet --warn-error-options '{…}'" and "dbt show --inline \"select * from {{ ref('orders') }}\" --limit 5" are fully executable and cover the common cases (build, show, list, defer, vars, static analysis).

5 / 5

Workflow Clarity

Validation checkpoints are present ("Use `dbt list` to preview what will be selected before running", run_results.json failure checks, warn-error-options for selector typos) but they are scattered across sections rather than presented as one sequenced run→verify→fix loop, so it falls between anchors 4 and 5.

4 / 5

Progressive Disclosure

Sections are well-organized with no bundle files to navigate, but exhaustive inline lists (all --output json keys, all valid resource types, full selector tables) push the body past quick-reference size where a one-level-deep reference file would fit anchor 5.

4 / 5

Total

18

/

20

Passed

Description

92%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.

An exemplary description: concrete third-person capabilities paired with two explicit trigger clauses that cleanly separate it from other skills. The only weakness is trigger-term coverage, which uses one phrasing per dbt verb and misses a few natural variations.

DimensionReasoningScore

Specificity

"Formats and executes dbt CLI commands, selects the correct dbt executable, and structures command parameters" lists multiple concrete third-person actions with comprehensive coverage of the skill's scope, matching the top anchor.

5 / 5

Completeness

Both questions are explicitly answered: a clear "what" (three named capabilities) followed by two concrete "Use when…" trigger clauses, matching the score-5 exemplar structure.

5 / 5

Trigger Term Quality

"running models, tests, builds, compiles, or show queries via dbt CLI" covers the natural dbt verbs, but gives a single phrasing per verb with no synonyms and omits terms like seeds, snapshots, or docs generation — "a few natural terms missing" rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The description is firmly niche — dbt CLI executable selection and command parameter formatting — with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

dbt-labs/dbt-agent-skills

Path

skills/dbt/skills/running-dbt-commands/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.