Skip to content
Back to skills

Snowflake Create Failover Group

ASecurity

Consult Snowflake CREATE FAILOVER GROUP parameter reference before generating any CREATE FAILOVER GROUP DDL.

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

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-failover-group --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Snowflake Create Failover Group?

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

Security grade badge for Snowflake Create Failover Group
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gyrus-dev-snowflake-create-failover-group/badge)](https://www.skillsdirectory.com/skills/gyrus-dev-snowflake-create-failover-group)

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-failover-group
description: Consult Snowflake CREATE FAILOVER GROUP parameter reference before generating any CREATE FAILOVER GROUP DDL.
---

Before writing a CREATE FAILOVER GROUP 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 FAILOVER GROUP IF NOT EXISTS`.
5. Use the primary group syntax when creating in the source account; use the secondary (AS REPLICA OF) syntax when creating in a target account.
6. `OBJECT_TYPES` is required — always confirm which object types the user wants to replicate.
7. When DATABASES is in OBJECT_TYPES, `ALLOWED_DATABASES` is also required. Similarly, `ALLOWED_SHARES` is required when SHARES is included, `ALLOWED_EXTERNAL_VOLUMES` for EXTERNAL VOLUMES, and `ALLOWED_INTEGRATION_TYPES` for INTEGRATIONS.
8. `ALLOWED_ACCOUNTS` is required and must use `org_name.account_name` format.
9. This feature requires Business Critical Edition or higher — note this limitation when relevant.

Files in this skill

  • SKILL.md1.3 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.