Skip to content
Back to skills

Snowflake Create Masking Policy

ASecurity

Consult Snowflake CREATE MASKING POLICY parameter reference before generating any CREATE MASKING POLICY DDL.

  • 77 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added June 11, 2026
code-qualitysqlexpress

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-masking-policy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Snowflake Create Masking Policy?

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

Security grade badge for Snowflake Create Masking Policy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gyrus-dev-snowflake-create-masking-policy/badge)](https://www.skillsdirectory.com/skills/gyrus-dev-snowflake-create-masking-policy)

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-masking-policy
description: Consult Snowflake CREATE MASKING POLICY parameter reference before generating any CREATE MASKING POLICY DDL.
---

Before writing a CREATE MASKING POLICY 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 MASKING POLICY IF NOT EXISTS`.
5. The return data type in `RETURNS` must exactly match the data type of the first argument (`<arg_name_to_mask>`); cross-type transformations are not allowed.
6. The policy body (`<body>`) must be a valid SQL expression — use conditional functions (e.g. `IFF`, `CASE`) along with masking functions (e.g. `SHA2`, `REGEXP_REPLACE`) or return the column value unchanged.
7. Only set `EXEMPT_OTHER_POLICIES = TRUE` if the user explicitly needs this policy to bypass other row access or conditional masking policies — this setting cannot be changed once the policy is attached to a table or view.
8. For conditional masking policies (multiple arguments), the first argument represents the column to mask; additional arguments provide context values but cannot be virtual columns.

Files in this skill

  • SKILL.md1.4 KB
  • references/parameters.md4.6 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.