omni-to-snowflake-semantic-view

Convert Omni Analytics topics into Snowflake Semantic View YAML definitions.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/noiz354/oc-rebirth-rca --skill omni-to-snowflake-semantic-view-noiz354
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omni-to-snowflake-semantic-view
Source: https://github.com/noiz354/oc-rebirth-rca/tree/main/planning-zip/omni-agent-skills/skills/omni-integrations/skills/omni-to-snowflake-semantic-view
Command: npx skills add https://github.com/noiz354/oc-rebirth-rca --skill omni-to-snowflake-semantic-view-noiz354

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams that model metrics in Omni Analytics often need those same definitions hardened into Snowflake so tools like Cortex Analyst can query them directly. Manually translating Omni topics, views, joins, and measures into Snowflake Semantic View YAML is error-prone and slow, especially with field exclusions, templated filters, and join hierarchies. ## Core Features & Use Cases - Omni Model Exploration: Uses the Omni CLI to fetch topic files, relationships, and view definitions from the Shared Model via API. - Full Semantic Translation: Maps Omni dimensions, time dimensions, groups, bins, durations, booleans, and measures (including derived and filtered measures) into Snowflake Semantic View YAML, resolving templated filter-only fields to static SQL. - Environment-Aware Execution: Detects whether it runs in Cortex Code or an external IDE and executes SYSTEM$CREATE_SEMANTIC_VIEW_FROM_YAML plus GRANT statements via snow CLI, SnowSQL, or the Python connector. - Use Case: A data engineer wants to expose the ecomm order_items topic to Snowflake Cortex Analyst. The skill explores the Omni model, resolves the field list and relationships, generates the Semantic View YAML, creates the view in the target database/schema, and grants access to the chosen role. ## Quick Start Convert my Omni order_items topic into a Snowflake Semantic View named ORDER_ANALYTICS in ANALYTICS.PUBLIC and grant SELECT to the ANALYST role.

Frequently Asked Questions about omni-to-snowflake-semantic-view

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert an Omni topic to a Snowflake Semantic View?▼

Use the Omni CLI to fetch the topic file, relationships, and referenced view YAMLs from the Shared Model, then translate fields, joins, and measures into the Semantic View YAML format. Finally run SYSTEM$CREATE_SEMANTIC_VIEW_FROM_YAML against your target database and schema.

How do I export Omni metrics to Snowflake Cortex Analyst?▼

Create a Snowflake Semantic View from the Omni topic definitions, since Cortex Analyst consumes Semantic Views. The conversion maps Omni measures to metrics, dimensions to dimensions or time_dimensions, and ai_context to module_custom_instructions.

Can I run this conversion outside of Snowflake, like in Claude Code or Cursor?▼

Yes, external environments work using the snow CLI, SnowSQL, or the snowflake-connector-python library to execute the CREATE and GRANT statements. Only Cortex Code has native SQL execution without extra tooling.

How are Omni templated filters handled in Snowflake Semantic Views?▼

Snowflake Semantic Views have no runtime parameter system, so filter-only fields are resolved to static SQL. The converter uses the inline fallback block or the filter's default_filter value, and warns the user when neither exists.

What happens to excluded fields in the Omni topic fields list?▼

Exclusions prefixed with a dash always win over wildcard inclusions and are removed from the final field set. Excluded fields are never emitted as dimensions, metrics, or filters in the Semantic View output.

Why does omni whoami return a 401 error during conversion?▼

A 401 means the active Omni CLI profile is not authenticated. Run omni config login with the profile name to complete the OAuth browser flow, or configure an API key, before retrying the model exploration commands.