Skip to content
Back to skills

Snowflake Create Notification Integration

ASecurity

Consult Snowflake CREATE NOTIFICATION INTEGRATION parameter reference before generating any CREATE NOTIFICATION INTEGRATION DDL.

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

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-notification-integration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Snowflake Create Notification Integration?

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

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

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-notification-integration
description: Consult Snowflake CREATE NOTIFICATION INTEGRATION parameter reference before generating any CREATE NOTIFICATION INTEGRATION DDL.
---

Before writing a CREATE NOTIFICATION INTEGRATION 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 NOTIFICATION INTEGRATION IF NOT EXISTS`.
5. Select the correct TYPE variant based on context: use `TYPE = EMAIL` for email notifications, `TYPE = WEBHOOK` for webhook integrations, and `TYPE = QUEUE` with the appropriate `NOTIFICATION_PROVIDER` (AWS_SNS, AZURE_EVENT_GRID, or GCP_PUBSUB) for cloud message-queue integrations.
6. Note that `OR REPLACE` and `IF NOT EXISTS` are mutually exclusive — always prefer `IF NOT EXISTS`.
7. For QUEUE types, always include `DIRECTION = OUTBOUND` and the provider-specific ARN or endpoint parameters.
8. For WEBHOOK types, include `WEBHOOK_SECRET` whenever the URL requires authentication credentials.

Files in this skill

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