Skip to content
Back to skills

Snowflake Create Dynamic Table

ASecurity

Consult Snowflake CREATE DYNAMIC TABLE parameter reference before generating any CREATE DYNAMIC TABLE DDL.

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

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-dynamic-table --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Snowflake Create Dynamic Table?

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

Security grade badge for Snowflake Create Dynamic Table
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gyrus-dev-snowflake-create-dynamic-table/badge)](https://www.skillsdirectory.com/skills/gyrus-dev-snowflake-create-dynamic-table)

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-dynamic-table
description: Consult Snowflake CREATE DYNAMIC TABLE parameter reference before generating any CREATE DYNAMIC TABLE DDL.
---

Before writing a CREATE DYNAMIC TABLE 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 DYNAMIC TABLE IF NOT EXISTS` where supported.
5. Always specify both `TARGET_LAG` and `WAREHOUSE` — they are required. Choose `TARGET_LAG = DOWNSTREAM` only when the dynamic table feeds other dynamic tables and downstream refresh semantics are desired; otherwise use an explicit interval (e.g., `'1 minutes'`).
6. Prefer `REFRESH_MODE = AUTO` unless the user explicitly requires `FULL` or `INCREMENTAL`; the system will choose the most efficient mode automatically.
7. Do not add `CLUSTER BY` unless the table is expected to be multi-terabyte or the user requests it.
8. Do not use `EXECUTE AS USER` unless the user explicitly provides an impersonation user, as it requires the IMPERSONATE privilege.
9. Append the defining query as the `AS <query>` clause at the end of the statement — it is required.

Files in this skill

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