<< All versions
Skill v1.0.0
currentAutomated scan100/100gyrus-dev/frosty/snowflake-create-iceberg-table
──Details
PublishedOctober 18, 2026 at 07:23 AM
Content Hashsha256:34fdf599dd1e68e5...
Git SHA
──Files
Files (1 file, 1.5 KB)
SKILL.md1.5 KBactive
SKILL.md · 18 lines · 1.5 KB
version: "1.0.0" 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:
- Read
references/parameters.mdto review all available parameters and their defaults. - For each parameter, decide whether the user's request implies a non-default value.
- Include only the parameters that differ from the default or that the user explicitly requested.
- Never use
CREATE OR REPLACE— always useCREATE ICEBERG TABLE IF NOT EXISTSwhere supported. - Always specify
EXTERNAL_VOLUMEandBASE_LOCATIONwhen Snowflake is the catalog (the most common case); omit them only when integrating an external catalog. CATALOG = 'SNOWFLAKE'is the default; omit it unless you are referencing an external catalog integration.STORAGE_SERIALIZATION_POLICY = COMPATIBLEis the default; useOPTIMIZEDonly when the user explicitly wants Snowflake-optimised encoding and compression and does not need to read the files with other engines.- Note that
NOT NULLandUNIQUEconstraints onPRIMARY KEYcolumns are represented in Iceberg metadata as identifier fields but are not enforced by Snowflake at DML time. - Do not add
CLUSTER BYunless the table is expected to be very large or the user requests it. - Use
PARTITION BYonly when the user specifies a partitioning strategy; choose identity, bucket, truncate, or temporal transforms as appropriate.