Skip to content
Back to skills

Snowflake Create Row Access Policy

ASecurity

Consult Snowflake CREATE ROW ACCESS POLICY parameter reference before generating any CREATE ROW ACCESS POLICY DDL.

  • 77 stars
  • 0 votes
  • 0 copies
  • 2 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-row-access-policy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Snowflake Create Row Access Policy?

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

Security grade badge for Snowflake Create Row Access Policy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gyrus-dev-snowflake-create-row-access-policy/badge)](https://www.skillsdirectory.com/skills/gyrus-dev-snowflake-create-row-access-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-row-access-policy
description: Consult Snowflake CREATE ROW ACCESS POLICY parameter reference before generating any CREATE ROW ACCESS POLICY DDL.
---

Before writing a CREATE ROW ACCESS 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 ROW ACCESS POLICY IF NOT EXISTS`.
5. The policy signature `AS ( <arg_name> <arg_type> [, ...] )` must match the columns it will be attached to; the signature cannot be modified once the policy is attached to a table or view.
6. The body must be a boolean SQL expression; return `TRUE` to expose a row and `FALSE` to hide it.
7. Row access policies are evaluated before masking policies — factor this into the policy logic when both types are applied to the same table.
8. Avoid complex subqueries in the body where possible; subqueries can cause runtime errors in some configurations.
9. The same column cannot appear in both a masking policy signature and a row access policy signature on the same table.

Files in this skill

  • SKILL.md1.3 KB
  • references/parameters.md3.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.