Skip to content
Back to skills

Snowflake Create Semantic View

ASecurity

Consult Snowflake CREATE SEMANTIC VIEW parameter reference before generating any CREATE SEMANTIC VIEW DDL.

  • 77 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added June 11, 2026
documentationsqlexpress

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned June 11, 2026

npx -y skills add Gyrus-Dev/frosty --skill snowflake-create-semantic-view --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Snowflake Create Semantic View?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Snowflake Create Semantic View
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gyrus-dev-snowflake-create-semantic-view/badge)](https://www.skillsdirectory.com/skills/gyrus-dev-snowflake-create-semantic-view)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: snowflake-create-semantic-view
description: Consult Snowflake CREATE SEMANTIC VIEW parameter reference before generating any CREATE SEMANTIC VIEW DDL.
---

Before writing a CREATE SEMANTIC VIEW statement:
1. Read `references/parameters.md` to review all available parameters and their defaults.
2. For each parameter, decide whether the user's request implies a non-default value.
3. Include only the parameters that differ from the default or that the user explicitly requested.
4. Never use `CREATE OR REPLACE` — always use `CREATE SEMANTIC VIEW IF NOT EXISTS` where supported.
5. Every semantic view must include a `TABLES` clause; at least one `DIMENSIONS` or `METRICS` clause is also required for the view to be valid.
6. Define `RELATIONSHIPS` whenever two or more logical tables must be joined; specify join type (standard, ASOF, or range) explicitly.
7. Populate `AI_SQL_GENERATION` with concise natural-language instructions that guide Cortex Analyst when generating SQL from the view.
8. Mark fact expressions `PRIVATE` when they should not be exposed directly to end users; dimensions are always `PUBLIC`.

Files in this skill

  • SKILL.md1.1 KB
  • references/parameters.md6.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.