← Browse

@gyrus-dev/snowflake-create-replication-group

A

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

skillclaude

Install

agr install @gyrus-dev/snowflake-create-replication-group --target claude

Writes 1 file into .claude/skills/, pinned to git-c122c71d.

  • .claude/skills/snowflake-create-replication-group/SKILL.md

Document


name: snowflake-create-replication-group description: Consult Snowflake CREATE REPLICATION GROUP parameter reference before generating any CREATE REPLICATION GROUP DDL.

Before writing a CREATE REPLICATION 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 REPLICATION 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. Unlike failover groups, replication groups do not support automatic failover — clarify this distinction if the user's intent is high availability.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-c122c71d7dba2026-07-31