Skip to content
Back to skills

Snowflake Create Pipe

ASecurity

Consult Snowflake CREATE PIPE parameter reference before generating any CREATE PIPE DDL.

  • 77 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added June 11, 2026
devopsawsazure

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-pipe --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Snowflake Create Pipe?

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

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

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-pipe
description: Consult Snowflake CREATE PIPE parameter reference before generating any CREATE PIPE DDL.
---

Before writing a CREATE PIPE 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 — do not bloat the DDL with unnecessary clauses.
4. Never use `CREATE OR REPLACE` — always use `CREATE PIPE IF NOT EXISTS`.
5. The `AS <copy_statement>` clause is required; always generate a valid `COPY INTO <table> FROM @<stage>` statement as part of the pipe definition.
6. `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).
7. For S3 auto-ingest, include `AWS_SNS_TOPIC` with the ARN of the SNS topic configured on the source bucket.
8. For GCS or Azure auto-ingest, include `INTEGRATION` referencing a notification integration.
9. `ERROR_INTEGRATION` is optional but recommended for production pipelines to route load errors to a notification channel.
10. Do not combine `OR REPLACE` and `IF NOT EXISTS` in the same statement — they are mutually exclusive.

Files in this skill

  • SKILL.md1.3 KB
  • references/parameters.md6.7 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.