CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

building-dbt-semantic-layer

Use when creating or modifying dbt Semantic Layer components — semantic models, metrics, dimensions, entities, measures, or time spines. Covers MetricFlow configuration, metric types (simple, derived, cumulative, ratio, conversion), and validation for both latest and legacy YAML specs.

Quality

91%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

Excellent instructional content: a clear version-routing decision procedure, complete minimal YAML examples for both spec generations, concrete validation commands with feedback loops, and a well-structured one-level reference bundle. The only tightening opportunities are the introductory component definitions and the generic external-content boilerplate.

DimensionReasoningScore

Conciseness

The body is dense and domain-specific (routing rules, minimal YAML examples, validation commands, pitfalls table) with little padding, but a few sections could be trimmed: the opening definition list ('Semantic models - Metadata configurations that define...') restates somewhat obvious context, and 'Handling External Content' is generic boilerplate. This fits anchor 4 (efficient, minor instances of over-explanation) better than anchor 5's 'every token earns its place', and is far above the verbosity of anchor 3.

4 / 5

Actionability

Two complete, copy-paste-ready YAML examples for both spec variants ('# models/fct_orders.yml' and '# models/sem_orders.yml'), exact commands ('dbt parse', 'dbtf parse', 'dbt sl validate', 'mf validate-configs', 'uvx dbt-autofix deprecations --semantic-layer'), and concrete filter syntax templates cover the common cases. This matches anchor 5 (fully executable, copy-paste ready, covers common cases); anchor 4 would imply missing key details, which are not evident.

5 / 5

Workflow Clarity

The spec-determination workflow is explicitly sequenced (Step 1: check existing config → Step 2: route by spec and dbt version → Step 3: follow the guide) and validation is enforced with feedback loops: two-stage validation, 'Do not consider work complete until both validations pass', and the stale-manifest recovery instruction to re-run 'dbt parse' before 'mf validate-configs'. This matches anchor 5 (clear sequence, explicit validation, error-recovery guidance); anchor 4 would require missing checkpoints, which are present.

5 / 5

Progressive Disclosure

SKILL.md functions as an overview with well-signaled, one-level-deep references: 'Additional Resources' lists all four files (time-spine, best-practices, latest-spec, legacy-spec), each of which exists in references/ and is self-contained (no nested reference chains). Minimal examples are inline while full YAML specs are appropriately split out, matching anchor 5.

5 / 5

Total

19

/

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 that clearly states what the skill covers and when to use it, with concrete component and metric-type terminology that users would naturally employ. The only minor gaps are a limited set of action verbs and a few missing synonyms (e.g., KPIs) in the trigger vocabulary.

DimensionReasoningScore

Specificity

The description names concrete components ('semantic models, metrics, dimensions, entities, measures, or time spines') and concrete coverage areas ('MetricFlow configuration, metric types (simple, derived, cumulative, ratio, conversion), and validation'), but the action verbs are limited to 'creating or modifying' rather than a fuller set of specific actions. This matches anchor 4 (several specific actions, minor gaps) better than anchor 5, and is clearly above anchor 3 given the enumerated component and metric-type coverage.

4 / 5

Completeness

It explicitly answers both questions: 'what' via 'Covers MetricFlow configuration, metric types (simple, derived, cumulative, ratio, conversion), and validation for both latest and legacy YAML specs', and 'when' via the leading 'Use when creating or modifying dbt Semantic Layer components' with concrete trigger objects listed. This mirrors the anchor-5 good example structure; anchor 4 would require the 'when' clause to be less explicit than it is.

5 / 5

Trigger Term Quality

Strong natural keywords a user would actually say: 'semantic models', 'metrics', 'dimensions', 'dbt Semantic Layer', 'MetricFlow', 'measures', 'time spines'. A few natural variations are missing (e.g., 'KPIs', 'business metrics', 'dbt metrics'), which places it at anchor 4 rather than the comprehensive synonym coverage of anchor 5; it is well above the sparse keyword coverage of anchor 3.

4 / 5

Distinctiveness Conflict Risk

The dbt Semantic Layer / MetricFlow niche is highly specific with distinct triggers (semantic models, measures, time spines, MetricFlow) that no generic skill would claim, matching the anchor-5 'clear niche with distinct triggers; minimal conflict risk'. Anchor 4 would imply overlap with closely related skills, which is not the case here.

5 / 5

Total

18

/

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/building-dbt-semantic-layer/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.