snowflake-create-view
Provides best practices and parameter references for writing Snowflake CREATE VIEW statements.
Install
mkdir -p .claude/skills/snowflake-create-view && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19543" && unzip -o skill.zip -d .claude/skills/snowflake-create-view && rm skill.zipInstalls to .claude/skills/snowflake-create-view
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Consult Snowflake CREATE VIEW parameter reference before generating any CREATE VIEW DDL.Key capabilities
- →Generate CREATE VIEW DDL for Snowflake
- →Implement change tracking on views
- →Manage security with the SECURE keyword
- →Create session-scoped temporary views
- →Handle recursive view definitions
How it works
The skill guides the generation of DDL by referencing specific parameters and enforcing constraints like using IF NOT EXISTS and explicit column aliasing.
Inputs & outputs
When to use snowflake-create-view
- →Create a secure Snowflake view
- →Implement change tracking on views
- →Define session-scoped temporary views
- →Refactor view DDL to follow Snowflake best practices
About this skill
Before writing a CREATE VIEW statement:
- Read
references/parameters.mdto review all available parameters and their defaults. - For each parameter, decide whether the user's request implies a non-default value.
- Include only the parameters that differ from the default or that the user explicitly requested — do not bloat the DDL with unnecessary clauses.
- Never use
CREATE OR REPLACE— always useCREATE VIEW IF NOT EXISTS. - 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).
- Use TEMPORARY/TEMP/VOLATILE only when the view is needed for session-scoped intermediate work; it will be dropped automatically at session end.
- 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.
- Enable CHANGE_TRACKING = TRUE only when the user needs to create a stream on this view or track row-level changes.
- Views share the namespace with tables — a view and a table cannot have the same name within a schema.
- The SELECT statement is limited to 95 KB; all columns derived from expressions must be given explicit aliases.
When not to use it
- →Using CREATE OR REPLACE
- →Including unnecessary parameters that match defaults
Limitations
- →SELECT statement is limited to 95 KB
- →Views and tables cannot share the same name in a schema
How it compares
It mandates specific Snowflake-compliant patterns like avoiding CREATE OR REPLACE and requiring explicit aliases for derived columns.
Compared to similar skills
snowflake-create-view side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| snowflake-create-view (this skill) | 0 | 4mo | No flags | Beginner |
| sql-optimization-patterns | 64 | 2mo | No flags | Advanced |
| drizzle-orm | 32 | 1mo | No flags | Intermediate |
| qdrant-vector-search | 18 | 8mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Gyrus-Dev
View all by Gyrus-Dev →You might also like
sql-optimization-patterns
wshobson
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
drizzle-orm
EpicenterHQ
Drizzle ORM patterns for type branding and custom types. Use when working with Drizzle column definitions, branded types, or custom type conversions.
qdrant-vector-search
zechenzhangAGI
High-performance vector similarity search engine for RAG and semantic search. Use when building production RAG systems requiring fast nearest neighbor search, hybrid search with filtering, or scalable vector storage with Rust-powered performance.
postgres-patterns
affaan-m
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.
postgresql-table-design
wshobson
Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features
agentdb-advanced-features
ruvnet
Master advanced AgentDB features including QUIC synchronization, multi-database management, custom distance metrics, hybrid search, and distributed systems integration. Use when building distributed AI systems, multi-agent coordination, or advanced vector search applications.