snowflake-create-projection-policy
SkillDatabases & dataConsult Snowflake CREATE PROJECTION POLICY parameter reference before generating any CREATE PROJECTION 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-projection-policy skill
What this skill tells your AI
The instructions your AI receives, as published by gyrus-dev/frosty in skills/snowflake-create-projection-policy/SKILL.md and read by ahel’s review.
Before writing a CREATE PROJECTION POLICY statement:
- Read
references/parameters.mdto 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 — do not bloat the DDL with unnecessary clauses.
- Never use
CREATE OR REPLACE— always useCREATE PROJECTION POLICY IF NOT EXISTS. - The policy body must call
PROJECTION_CONSTRAINT(ALLOW => {TRUE|FALSE} [, ENFORCEMENT => {'FAIL'|'NULLIFY'}]). ALLOW => TRUEpermits column projection (pass-through);ALLOW => FALSErestricts it — use theENFORCEMENTargument to control whether restricted queries fail or return NULLs.- The default
ENFORCEMENTisFAIL; only specifyNULLIFYif the user explicitly wants columns silently nullified rather than causing query failures. - Projection policies only affect columns in the final result set (outermost SELECT); columns used only in WHERE or JOIN clauses are not blocked. Requires Enterprise Edition or higher.
Signals
- GitHub stars
- 77
- Forks
- 9
- Last commit
- Apr 2026
Advanced
- Catalog kind
- skill
- Gateway key
snowflake-create-projection-policy- Source
- github.com/gyrus-dev/frosty