Skip to content
Agentmart
Submit a tool

snowflake-create-security-integration

Consult Snowflake CREATE SECURITY INTEGRATION parameter reference before generating any CREATE SECURITY INTEGRATION DDL.

Skill by Gyrus-Dev

IndexedApache-2.0★ 78
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/gyrus-dev-snowflake-create-security-integration

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Consult Snowflake CREATE SECURITY INTEGRATION parameter reference before generating any CREATE SECURITY INTEGRATION DDL.

Use cases: data, security

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/snowflake-create-security-integration

What's inside

Skill name
snowflake-create-security-integration
Description
Consult Snowflake CREATE SECURITY INTEGRATION parameter reference before generating any CREATE SECURITY INTEGRATION DDL.
License
Apache-2.0
Instructions
16 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • parameters.md · references/

SKILL.md (first lines)

Before writing a CREATE SECURITY INTEGRATION 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 SECURITY INTEGRATION IF NOT EXISTS`.
5. Select the correct TYPE based on the use case:
   - `API_AUTHENTICATION` — for connecting Snowflake to external APIs via OAuth2 (used with EXTERNAL ACCESS INTEGRATION and SECRETs).
   - `AWS_IAM` — for authenticating Snowflake with AWS services using IAM roles.
   - `EXTERNAL_OAUTH` — for allowing external OAuth providers (Okta, Azure AD, custom) to authorize Snowflake access.
   - `OAUTH` — for Snowflake-managed OAuth flows (Snowflake OAuth for partners or custom clients).
   - `SAML2` — for SAML-based SSO from an identity provider.
   - `SCIM` — for provisioning and managing users and groups via SCIM 2.0.
6. Each TYPE has mutually exclusive required parameters; only include parameters documented for the selected TYPE.
7. For SAML2, the SAML2_X509_CERT value must be the raw base64-encoded certificate without PEM headers.

From Gyrus-Dev/frosty, Apache-2.0.

More from Gyrus-Dev/frosty

Signals

Stars
78
Forks
10
Open issues
2
Last commit (this folder)
Mar 24, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from Gyrus-Dev

Cite this page

snowflake-create-security-integration skill. Agent Mart. https://agentmart.dev/skills/gyrus-dev-snowflake-create-security-integration (last updated 2026-10-24)