snowflake-create-pipe

SkillDatabases & data

Consult Snowflake CREATE PIPE parameter reference before generating any CREATE PIPE 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-pipe skill

What this skill tells your AI

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

Before writing a CREATE PIPE 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 — do not bloat the DDL with unnecessary clauses.
Never use CREATE OR REPLACE — always use CREATE PIPE IF NOT EXISTS.
The AS <copy_statement> clause is required; always generate a valid COPY INTO <table> FROM @<stage> statement as part of the pipe definition.
AUTO_INGEST = TRUE is required for fully automated Snowpipe ingestion from external stages; it requires cloud event notification setup (SQS for S3, Pub/Sub for GCS, Azure Event Grid for Azure).
For S3 auto-ingest, include AWS_SNS_TOPIC with the ARN of the SNS topic configured on the source bucket.
For GCS or Azure auto-ingest, include INTEGRATION referencing a notification integration.
ERROR_INTEGRATION is optional but recommended for production pipelines to route load errors to a notification channel.
Do not combine OR REPLACE and IF NOT EXISTS in the same statement — they are mutually exclusive.

Advanced