snowflake-create-secret

SkillDatabases & data

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

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the snowflake-create-secret skill

What this skill tells your AI

The instructions your AI receives, as published by gyrus-dev/frosty in skills/snowflake-create-secret/SKILL.md and read by ahel’s review.

Before writing a CREATE SECRET statement:

Read references/parameters.md to 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.
Never use CREATE OR REPLACE — always use CREATE SECRET IF NOT EXISTS.
Select the correct TYPE based on the use case:
- GENERIC_STRING for API tokens or arbitrary sensitive strings accessed via SYSTEM$GET_SECRET.
- PASSWORD for username/password basic-auth credentials.
- OAUTH2 with API_AUTHENTICATION + OAUTH_SCOPES for OAuth2 client-credentials flow.
- OAUTH2 with OAUTH_REFRESH_TOKEN + OAUTH_REFRESH_TOKEN_EXPIRY_TIME + API_AUTHENTICATION for OAuth2 authorization-code-grant flow.
The secret value (SECRET_STRING, PASSWORD, OAUTH_REFRESH_TOKEN) is never shown after creation; advise users to store the original value securely.
For OAUTH2 secrets, the referenced security integration must exist and its OAUTH_ALLOWED_SCOPES must cover any requested OAUTH_SCOPES.

Advanced