Skip to content
Back to skills

Snowflake Create View

ASecurity

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

  • 77 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added June 11, 2026
databasesexpress

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

Installs into .claude/skills of the current project.

Are you the author of Snowflake Create View?

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

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

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-view
description: Consult Snowflake CREATE VIEW parameter reference before generating any CREATE VIEW DDL.
---

Before writing a CREATE VIEW 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 VIEW IF NOT EXISTS`.
5. Add the SECURE keyword only when the user explicitly needs to restrict access to the view definition (e.g. hiding business logic from non-privileged users).
6. Use TEMPORARY/TEMP/VOLATILE only when the view is needed for session-scoped intermediate work; it will be dropped automatically at session end.
7. Use RECURSIVE only when the SELECT statement needs to reference the view itself (self-referencing query); provide an explicit column list when RECURSIVE is used.
8. Enable CHANGE_TRACKING = TRUE only when the user needs to create a stream on this view or track row-level changes.
9. Views share the namespace with tables — a view and a table cannot have the same name within a schema.
10. The SELECT statement is limited to 95 KB; all columns derived from expressions must be given explicit aliases.

Files in this skill

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