Skip to content
Back to skills

Snowflake Create Materialized View

ASecurity

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

  • 77 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added June 11, 2026
code-qualitygoperformance

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-materialized-view --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Snowflake Create Materialized View?

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

Security grade badge for Snowflake Create Materialized View
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gyrus-dev-snowflake-create-materialized-view/badge)](https://www.skillsdirectory.com/skills/gyrus-dev-snowflake-create-materialized-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-materialized-view
description: Consult Snowflake CREATE MATERIALIZED VIEW parameter reference before generating any CREATE MATERIALIZED VIEW DDL.
---

Before writing a CREATE MATERIALIZED 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 — do not bloat the DDL with unnecessary clauses.
4. Never use `CREATE OR REPLACE` — always use `CREATE MATERIALIZED VIEW IF NOT EXISTS`.
5. Materialized views require Snowflake Enterprise Edition or higher; flag this requirement to the user if the edition is unknown.
6. The SELECT statement used to define the materialized view must NOT include HAVING, ORDER BY clauses, or references to stream objects.
7. Add CLUSTER BY only for large datasets where the clustering key matches the most common filter patterns — always include an explicit column list when using CLUSTER BY.
8. Use SECURE only when the user needs to hide the view definition from non-privileged users.
9. Use INTERACTIVE only when the materialized view is based on a single interactive table and low-latency query performance is required.
10. Apply MASKING POLICY, ROW ACCESS POLICY, AGGREGATION POLICY, or TAG clauses only when the user explicitly requests governance controls.

Files in this skill

  • SKILL.md1.4 KB
  • references/parameters.md5.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.