Skip to content
Back to skills

Snowflake Create Table

ASecurity

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

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

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

Installs into .claude/skills of the current project.

Are you the author of Snowflake Create Table?

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

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

Before writing a CREATE 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 — do not bloat the DDL with unnecessary clauses.
4. Never use `CREATE OR REPLACE` — always use `CREATE TABLE IF NOT EXISTS`.
5. Choose the correct table type: permanent (default), TRANSIENT (no Fail-safe, lower cost), or TEMPORARY/TEMP/VOLATILE (session-scoped, dropped at session end). Default to permanent unless the user implies otherwise.
6. For CTAS (CREATE TABLE … AS SELECT), omit column definitions when the SELECT list already provides unambiguous names and types.
7. Use CLUSTER BY only for very large (multi-terabyte) tables where the chosen clustering key matches common filter/join patterns — do not add it speculatively.
8. Enable CHANGE_TRACKING = TRUE only when the user explicitly needs CDC or stream support on the table.
9. Set DATA_RETENTION_TIME_IN_DAYS only when the user specifies a non-default retention window; the platform default is 1 day.
10. Apply MASKING POLICY, ROW ACCESS POLICY, AGGREGATION POLICY, or TAG clauses only when the user explicitly requests governance controls.

Files in this skill

  • SKILL.md1.4 KB
  • references/parameters.md8.8 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.