snowflake-semanticview

Create, alter, and validate Snowflake semantic views via Snowflake CLI.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/webmaxru/octocat_supply --skill snowflake-semanticview-webmaxru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: snowflake-semanticview
Source: https://github.com/webmaxru/octocat_supply/tree/main/.github/skills/snowflake-semanticview
Command: npx skills add https://github.com/webmaxru/octocat_supply --skill snowflake-semanticview-webmaxru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides data engineers to author, validate, and deploy Snowflake semantic view DDL reliably, eliminating accidental schema breaks and incomplete semantic metadata.

Core Features & Use Cases

  • Draft and Iterate DDL: Produce CREATE or ALTER SEMANTIC VIEW statements tailored to a target database, schema, role, and warehouse.
  • Validate via CLI: Validate definitions against Snowflake using the Snowflake CLI with a temporary name to avoid clobbering production views.
  • Synonyms and Comments Management: Read existing table/view/column comments, suggest or create synonyms and comments with user approval.
  • Use Case: A data engineer preparing a new semantic layer for BI tools can draft the semantic view, validate it against Snowflake, iterate on errors, and apply the final view safely.

Quick Start

Use the configured Snowflake CLI connection to validate a draft semantic view DDL under a temporary name before applying the final CREATE or ALTER SEMANTIC VIEW.

Frequently Asked Questions about snowflake-semanticview

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

FAQPage Schema
How do I validate Snowflake semantic view DDL before applying it?

To validate Snowflake semantic view DDL safely, use the Snowflake CLI to execute CREATE or ALTER statements under a temporary name, preventing accidental overwrites to production views before finalizing.

What's the best way to manage synonyms and comments when creating a semantic view in Snowflake?

Managing synonyms and comments for a Snowflake semantic view involves reading existing table and column metadata, then suggesting or explicitly creating missing synonyms and comments with user approval before finalizing the DDL.

Do I need the Snowflake CLI to draft and iterate on semantic view definitions?

Yes, you need a configured Snowflake CLI connection to perform iterative DDL validation, execute snow sql commands, and ensure your semantic layer definitions are correct before deployment.

Why does my Snowflake semantic view validation break my schema?

Semantic view validation can break a schema if applied directly to production, so you must use a temporary validation name during iterative snow sql checks to avoid clobbering existing database objects.

Can I alter an existing Snowflake semantic view without losing metadata?

Yes, you can alter a Snowflake semantic view without losing metadata by reading existing comments and synonyms first, validating the ALTER DDL with a temporary name, and preserving or explicitly recreating the metadata.