snowflake-create-external-table

SkillDatabases & data

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

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the snowflake-create-external-table skill

What this skill tells your AI

The instructions your AI receives, as published by gyrus-dev/frosty in skills/snowflake-create-external-table/SKILL.md and read by ahel’s review.

Before writing a CREATE EXTERNAL TABLE statement:

Read references/parameters.md to 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 use CREATE EXTERNAL TABLE IF NOT EXISTS where supported.
Always specify LOCATION (referencing an external stage on S3, Azure, or GCS — internal Snowflake stages are not supported) and FILE_FORMAT.
All data columns must be defined as virtual columns using expressions against the VALUE (VARIANT) pseudocolumn, METADATA$FILENAME, or METADATA$FILE_ROW_NUMBER; do not attempt to define plain physical columns.
AUTO_REFRESH = TRUE and REFRESH_ON_CREATE = TRUE are the defaults; only override them if the user explicitly opts out of automatic refreshes.
Use PARTITION_TYPE = USER_SPECIFIED only when the user intends to manage partitions manually via ALTER EXTERNAL TABLE … ADD PARTITION.
External tables do not support Time Travel, clustering keys, or cloning — do not include those parameters.

Advanced