snowflake-create-event-table

SkillDatabases & data

Consult Snowflake CREATE EVENT TABLE parameter reference before generating any CREATE EVENT 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-event-table skill

What this skill tells your AI

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

Before writing a CREATE EVENT 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 EVENT TABLE IF NOT EXISTS where supported.
Event tables share a namespace with regular tables and views; ensure the chosen name does not conflict with existing objects in the same schema.
CHANGE_TRACKING = FALSE is the default; enable it only if the user explicitly needs to track changes via streams.
Do not add CLUSTER BY unless the table is expected to be multi-terabyte or the user specifically requests it; clustering is not recommended for most event tables.
DATA_RETENTION_TIME_IN_DAYS defaults to 1; increase it only if the user requires a longer Time Travel window (max 90 days on Enterprise edition).
Using OR REPLACE on an existing event table drops the old table and makes any existing streams on it stale — warn the user about this side effect if they ask about replacing an existing event table.

Advanced