snowflake-create-session-policy

SkillDatabases & data

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

What this skill tells your AI

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

Before writing a CREATE SESSION 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 SESSION POLICY IF NOT EXISTS.
SESSION_IDLE_TIMEOUT_MINS applies to all Snowflake clients and programmatic connections; SESSION_UI_IDLE_TIMEOUT_MINS applies only to Snowsight. Set both when the user needs consistent behavior across interfaces.
BLOCKED_SECONDARY_ROLES takes precedence over ALLOWED_SECONDARY_ROLES; avoid specifying the same role in both lists.
Remind the user that the policy must be attached to a user or account with ALTER USER SET SESSION_POLICY or ALTER ACCOUNT SET SESSION_POLICY to take effect.

Advanced