Omni → dbt MetricFlow

Export Omni model logic to dbt MetricFlow YAML. The logic lives in views (dimensions, measures, primary keys) and in the relationships file. Each dbt-backed view becomes one semantic model. A topic is optional: it scopes the views and fields, and its default_filters and sample_queries become saved queries. Once the YAML is merged in dbt, Omni brings it in on the next schema refresh or dbt sync, and the Omni model layer still wins over it. The last part of this skill removes the Omni override so Omni falls back to the dbt definition. Treat exported YAML as a draft until the user approves a write or promotion.

Read FIELD-MAPPING.md for mappings and worked examples. Read YAML-REFERENCE.md for legacy and dbt 1.12 YAML. Read FALLBACK-TO-DBT.md before you remove an Omni override.

Prerequisites

command -v omni >/dev/null || echo "ERROR: Omni CLI is not installed."
omni config show
omni config use <profile-name>
omni whoami whoami

Auth: a profile uses an API key or OAuth. If whoami returns 401, ask the user to run ! omni config login <profile>. Do not run browser login in a headless session. See omni-api-conventions for profile setup and --schema.