snowflake-create-packages-policy

SkillDatabases & data

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

What this skill tells your AI

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

Before writing a CREATE PACKAGES 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 PACKAGES POLICY IF NOT EXISTS.
LANGUAGE PYTHON is the only supported language and is always required.
Package specs follow the format package_name==version or package_name (wildcard version). Use * in ALLOWLIST to allow all packages (the default); be explicit when restricting to specific packages.
ADDITIONAL_CREATION_BLOCKLIST restricts packages at UDF/procedure creation time in addition to runtime; use this for packages that should never appear in any code even temporarily.

Advanced