Skip to content
Back to skills

Snowflake Create Iceberg Table

ASecurity

Consult Snowflake CREATE ICEBERG TABLE parameter reference before generating any CREATE ICEBERG TABLE DDL.

  • 77 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added June 11, 2026
documentation

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-iceberg-table --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Snowflake Create Iceberg Table?

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

Security grade badge for Snowflake Create Iceberg Table
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gyrus-dev-snowflake-create-iceberg-table/badge)](https://www.skillsdirectory.com/skills/gyrus-dev-snowflake-create-iceberg-table)

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-iceberg-table
description: Consult Snowflake CREATE ICEBERG TABLE parameter reference before generating any CREATE ICEBERG TABLE DDL.
---

Before writing a CREATE ICEBERG TABLE 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 ICEBERG TABLE IF NOT EXISTS` where supported.
5. Always specify `EXTERNAL_VOLUME` and `BASE_LOCATION` when Snowflake is the catalog (the most common case); omit them only when integrating an external catalog.
6. `CATALOG = 'SNOWFLAKE'` is the default; omit it unless you are referencing an external catalog integration.
7. `STORAGE_SERIALIZATION_POLICY = COMPATIBLE` is the default; use `OPTIMIZED` only when the user explicitly wants Snowflake-optimised encoding and compression and does not need to read the files with other engines.
8. Note that `NOT NULL` and `UNIQUE` constraints on `PRIMARY KEY` columns are represented in Iceberg metadata as identifier fields but are **not enforced** by Snowflake at DML time.
9. Do not add `CLUSTER BY` unless the table is expected to be very large or the user requests it.
10. Use `PARTITION BY` only when the user specifies a partitioning strategy; choose identity, bucket, truncate, or temporal transforms as appropriate.

Files in this skill

  • SKILL.md1.5 KB
  • references/parameters.md9.6 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.