Skip to content
Back to skills

Snowflake Create Procedure

ASecurity

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

  • 77 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added June 11, 2026
developmentjavascriptpythonjavasql

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

Installs into .claude/skills of the current project.

Are you the author of Snowflake Create Procedure?

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

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

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

Before writing a CREATE PROCEDURE 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 PROCEDURE IF NOT EXISTS` where supported.
5. Confirm the handler language (SQL/Snowflake Scripting, JavaScript, Python, Java, or Scala) before generating code; each language has distinct required parameters (`RUNTIME_VERSION`, `PACKAGES`, `HANDLER`).
6. Default execution context is `EXECUTE AS OWNER`; switch to `EXECUTE AS CALLER` only when the procedure must run with the caller's privileges.
7. Stored procedures support overloading by argument count or data types; ensure the signature is unambiguous.
8. Procedures are not atomic — individual statement failures do not automatically roll back the entire procedure; advise explicit transaction control when needed.

Files in this skill

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