snowflake-create-network-policy

SkillDatabases & data

Consult Snowflake CREATE NETWORK POLICY parameter reference before generating any CREATE NETWORK POLICY 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-network-policy skill

What this skill tells your AI

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

Before writing a CREATE NETWORK POLICY 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 NETWORK POLICY IF NOT EXISTS.
Prefer ALLOWED_NETWORK_RULE_LIST and BLOCKED_NETWORK_RULE_LIST (referencing named NETWORK RULEs) over the legacy ALLOWED_IP_LIST / BLOCKED_IP_LIST parameters.
Remind the user that a network policy has no effect until it is attached via ALTER ACCOUNT SET NETWORK_POLICY, ALTER USER SET NETWORK_POLICY, or ALTER INTEGRATION SET NETWORK_POLICY.
BLOCKED_IP_LIST is evaluated before ALLOWED_IP_LIST; entries in both lists result in the IP being blocked.

Advanced