Skip to content
Back to skills

Snowflake Create Authentication Policy

ASecurity

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

  • 77 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added June 11, 2026
securitysecurity

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

Installs into .claude/skills of the current project.

Are you the author of Snowflake Create Authentication Policy?

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

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

Before writing a CREATE AUTHENTICATION 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.
4. Never use `CREATE OR REPLACE` — always use `CREATE AUTHENTICATION POLICY IF NOT EXISTS`.
5. When the user specifies MFA requirements, select MFA_ENROLLMENT carefully: use `REQUIRED` to force all users and `REQUIRED_PASSWORD_ONLY` only for password-based logins. Omit if leaving the default `OPTIONAL` behavior.
6. For SECURITY_INTEGRATIONS, only list specific integration names when the user's SAML or OAuth setup is known; otherwise leave as the default `ALL`.
7. When configuring PAT_POLICY or WORKLOAD_IDENTITY_POLICY, always include each sub-property explicitly rather than relying on nested defaults.

Files in this skill

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