| [v1.1.27-beta] 2026-07-02 ADDED: +2 REMOVED: -1 MODIFIED: ~8 - •
manage-authentication-policyUse for requests about Snowflake authentication policies. Create, modify, view, … +Use for requests about Snowflake authentication policies. Create, modify, view, attach, detach,
drop, OR recommend authentication policies. Covers: restricting authentication methods
(PASSWORD, SAML, OAUTH, KEYPAIR), enforcing MFA, configuring PAT expiry and network policy,
workload identity federation, client type restrictions, minimum driver versions, and security
integration controls.
Invoke when user mentions: authentication policy, auth policy, MFA policy, MFA enrollment,
PAT policy, client types, workload identity, driver version policy, keypair only, SAML only,
require MFA, block password login, restrict client access, service account authentication,
show/list authentication policies, recommend/suggest authentication policies, help me set up
auth policies, audit my authentication, harden authentication, lock down authentication. - •
share-skill-and-pluginShare or unshare a local skill or plugin to users within the same account by exe… +Share or unshare a local skill or plugin to users within the same account by executing the Cortex Extension share SQL directly. Use when the user says "share skill", "publish skill", "share my skill", "share plugin", "publish plugin", "share my plugin", "share with users", "share publicly", "upload to cortex extension", "publish my skill", "publish my plugin", "make available", "add to skill catalog", "add to catalog", "add skill to catalog", "add plugin to catalog", "add my skill to the catalog", "publish to skill catalog", "publish to the catalog", "submit to skill catalog", "put in the skill catalog", "unshare skill", "unshare plugin", "stop sharing", "remove shared", "revoke access", "remove from catalog", "delete from catalog" or "delete shared". This is for publishing a local skill or plugin TO the catalog; to install or pull an existing skill FROM the catalog, use find-skill instead. Does not handle consumer/install flows. Does not handle sharing across accounts. - •
share-skillShare or unshare a local skill to users within the same account by executing th… +Share or unshare a local skill to users within the same account by executing the Cortex Extension share SQL directly. Use when the user says "share skill", "publish skill", "share my skill.md", "share skill with users", "share skill publicly", "upload skill to cortex extension", "publish my skill", "share this skill", "make skill available", "unshare skill", "stop sharing skill", "remove shared skill", "revoke shared skill access", or "delete shared skill". Does not handle consumer/install flows. Does not handle sharing across accounts. - •
cost-intelligence description_changed - •
data-cleanrooms description_changed - •
data-sharing description_changed - •
lineage description_changed - •
native-app-consumer description_changed - •
native-app-provider description_changed - •
sql-author description_changed - •
team-workflow description_changed
| | [v1.1.26-beta] 2026-07-02 ADDED: +2 REMOVED: -1 MODIFIED: ~8 - •
manage-authentication-policyUse for requests about Snowflake authentication policies. Create, modify, view, … +Use for requests about Snowflake authentication policies. Create, modify, view, attach, detach,
drop, OR recommend authentication policies. Covers: restricting authentication methods
(PASSWORD, SAML, OAUTH, KEYPAIR), enforcing MFA, configuring PAT expiry and network policy,
workload identity federation, client type restrictions, minimum driver versions, and security
integration controls.
Invoke when user mentions: authentication policy, auth policy, MFA policy, MFA enrollment,
PAT policy, client types, workload identity, driver version policy, keypair only, SAML only,
require MFA, block password login, restrict client access, service account authentication,
show/list authentication policies, recommend/suggest authentication policies, help me set up
auth policies, audit my authentication, harden authentication, lock down authentication. - •
share-skill-and-pluginShare or unshare a local skill or plugin to users within the same account by exe… +Share or unshare a local skill or plugin to users within the same account by executing the Cortex Extension share SQL directly. Use when the user says "share skill", "publish skill", "share my skill", "share plugin", "publish plugin", "share my plugin", "share with users", "share publicly", "upload to cortex extension", "publish my skill", "publish my plugin", "make available", "add to skill catalog", "add to catalog", "add skill to catalog", "add plugin to catalog", "add my skill to the catalog", "publish to skill catalog", "publish to the catalog", "submit to skill catalog", "put in the skill catalog", "unshare skill", "unshare plugin", "stop sharing", "remove shared", "revoke access", "remove from catalog", "delete from catalog" or "delete shared". This is for publishing a local skill or plugin TO the catalog; to install or pull an existing skill FROM the catalog, use find-skill instead. Does not handle consumer/install flows. Does not handle sharing across accounts. - •
share-skillShare or unshare a local skill to users within the same account by executing th… +Share or unshare a local skill to users within the same account by executing the Cortex Extension share SQL directly. Use when the user says "share skill", "publish skill", "share my skill.md", "share skill with users", "share skill publicly", "upload skill to cortex extension", "publish my skill", "share this skill", "make skill available", "unshare skill", "stop sharing skill", "remove shared skill", "revoke shared skill access", or "delete shared skill". Does not handle consumer/install flows. Does not handle sharing across accounts. - •
cost-intelligencedescription_changed +Account-level cost analytics via SNOWFLAKE.ACCOUNT_USAGE. Credit usage by warehouse, user, service. Budgets, spending limits, custom budgets. Quotas, per-user spending limits, per-user credit caps, quota notifications, quota enforcement, exclude users from quota, quota shared resources. Resource monitors, credit quotas, suspend triggers. Anomaly detection, costs, chargeback, storage, serverless, containers, data transfer, top user spend, query cost grouping. Cortex AI cost or usage including Cortex Agents, Snowflake Intelligence, Snowflake CoWork, AI function, Cortex Code, CoCo, Cortex Search, Cortex Analyst, Cortex REST API, model training/fine-tuning, and provisioned throughput. Cost insights, waste reduction, savings. Not for org-wide currency spend or multi-account billing (billing/organization-management) or warehouse DDL (warehouse). - •
data-cleanrooms description_changed - •
data-sharing description_changed - •
lineage description_changed - •
native-app-consumer description_changed - •
native-app-provider description_changed - •
sql-author description_changed - •
team-workflow description_changed
| | [v1.1.22-beta] 2026-06-29 ADDED: +2 REMOVED: -1 MODIFIED: ~7 - •
manage-authentication-policyUse for requests about Snowflake authentication policies. Create, modify, view, … +Use for requests about Snowflake authentication policies. Create, modify, view, attach, detach,
drop, OR recommend authentication policies. Covers: restricting authentication methods
(PASSWORD, SAML, OAUTH, KEYPAIR), enforcing MFA, configuring PAT expiry and network policy,
workload identity federation, client type restrictions, minimum driver versions, and security
integration controls.
Invoke when user mentions: authentication policy, auth policy, MFA policy, MFA enrollment,
PAT policy, client types, workload identity, driver version policy, keypair only, SAML only,
require MFA, block password login, restrict client access, service account authentication,
show/list authentication policies, recommend/suggest authentication policies, help me set up
auth policies, audit my authentication, harden authentication, lock down authentication. - •
share-skill-and-plugin-via-snowflakeShare or unshare a local skill or plugin to users within the same account by exe… +Share or unshare a local skill or plugin to users within the same account by executing the Cortex Extension share SQL directly. Use when the user says "share skill", "publish skill", "share my skill", "share plugin", "publish plugin", "share my plugin", "share with users", "share publicly", "upload to cortex extension", "publish my skill", "publish my plugin", "make available", "unshare skill", "unshare plugin", "stop sharing", "remove shared", "revoke access", or "delete shared". Does not handle consumer/install flows. Does not handle sharing across accounts. - •
share-skillShare or unshare a local skill to users within the same account by executing th… +Share or unshare a local skill to users within the same account by executing the Cortex Extension share SQL directly. Use when the user says "share skill", "publish skill", "share my skill.md", "share skill with users", "share skill publicly", "upload skill to cortex extension", "publish my skill", "share this skill", "make skill available", "unshare skill", "stop sharing skill", "remove shared skill", "revoke shared skill access", or "delete shared skill". Does not handle consumer/install flows. Does not handle sharing across accounts. - •
data-cleanroomsdescription_changed +Use for ALL requests related to Snowflake Data Clean Rooms (DCR): clean room, cleanroom, DCR, collaboration(s), view/list collaborations, join/review collaboration, invitation, data offering(s), template(s), register, share table, run analysis, run activation, audience overlap, activation, export segment, create collaboration, create cleanroom, measure overlap, manage templates, add template, remove template, approve template, reject template, auto-approval, link data offering, unlink data offering, share data with runner, revoke data access, link local data offering, unlink local data offering, tear down, leave, drop collaboration, delete collaboration. collaboration, RBAC, DCR roles, DCR privileges, create roles for clean rooms, assign DCR privileges, grant collaboration privileges, revoke DCR privileges, set up DCR roles, privileges for data engineers, privileges for campaign manager, create template, write template, build template, template spec, create DCR template, author template, Jinja template, template logic, incrementality measurement, multi-touch attribution, attribution analysis, convert PnC template, migrate template. Covers browsing, joining, registering, running analysis/activation, creating collaborations, managing templates, managing data offerings, and RBAC/role setup, leaving/tearing down collaborations collaborations, and creating/authoring template specs via the DCR Collaboration API. - •
data-sharingdescription_changed +Snowflake secure data sharing: create direct shares, external marketplace listings, debug grant failures. Triggers: create share, share data, share table, share database, outbound share, data sharing, share with account, direct share, external listing, marketplace listing, debug share, share not working, grant failed, consumer can't access, share troubleshooting, why can't they see my data, share error, permission denied on share, share external data, share iceberg table, iceberg data sharing, share S3 data, share Azure data, share GCS data, share without moving data, data outside snowflake, iceberg listing, move data to snowflake and share, replicate and share, openflow and share, load data then share. share, reshare imported database, reshare incoming data, reshare from listing, reshare ULL, reshare data I received, reshare from ORGDATACLOUD, share data from imported database. WHEN TO USE THIS SKILL: - User wants to share data (generic intent — will ask who they want to share with) - User wants to create direct shares with specific accounts - User wants to create external listings (Snowflake Marketplace) - User wants to reshare data they received from another account (imported DB or ULL) - User needs to debug why a share isn't working WHEN TO USE org-listing workflow INSTEAD: - User mentions "internal marketplace", "organization listing", or "data product" - User wants to share within their Snowflake organization - •
lineagedescription_changed +Snowflake table/column lineage: impact analysis, root cause, data discovery, provenance, trust. Triggers: 'what depends on', 'what will break', 'blast radius', 'who uses', 'deprecate', 'before I change', 'affected users', 'downstream', 'cascade', 'root cause', 'trace upstream', 'where does this come from', 'feeds this table', 'sources of', 'column lineage', 'where does [column] come from', 'what uses [column]', 'trace [column]', 'is this trustworthy', 'which table should I use', 'recommend dataset', 'provenance', 'certify', 'verify source'. Also handles questions where users mention external systems (Power BI, Tableau, Sigma, Looker, dbt) — for accounts with Horizon + Select Star Private Preview enabled, lineage results from native-anchored queries automatically include external entities. For value-level data quality (wrong values, failing DMFs) use the data-quality skill first, then this skill to trace upstream. Always read `reference/snowflake-apis.md` before writing GET_LINEAGE SQL — it has the correct namespace, argument order, and output column names. When external entities appear in results, see `reference/external-row-output.md`. - •
native-app-consumerdescription_changed +**[REQUIRED]** for ALL Snowflake Native App consumer tasks: installing apps from listings as a consumer, configuring installed apps (granting privileges, approving specifications, reviewing references), managing maintenance policies, understanding native app cost and credit usage, adding native apps to budgets. budgets, diagnosing and fixing agent and MCP server issues (caller grants, feature policies, role delegation), uninstalling apps. Triggers: native app, install native app, configure native app, approve spec, decline spec, maintenance policy, maintenance window, upgrade schedule, control upgrades, app cost, app budget, app spending, native app cost, native app credits, how much does my app cost. cost, uninstalling apps, dropping apps, remove app, drop application, app-created agent not working, app agent issues, app MCP issues, caller grants for app, GRANT CALLER to app, fix agent in app, diagnose app agent, configure agent in app, app-created MCP not working, grant caller to application, app MCP configuration. - •
native-app-providerdescription_changed +Use for **ALL** Snowflake Native App Framework tasks: creating app packages, writing manifest files, writing setup scripts, sharing data, testing, versioning, publishing, configuring telemetry and health status reporting, monitoring app health and lifecycle events, setting up event sharing, and debugging apps. Also use for **ALL** SPCS (Snowpark Container Services) work within native apps: adding containers, upgrading container services, building and pushing images, writing service specs, configuring compute pools, and managing service lifecycle. This is the **REQUIRED** entry point for any native app work. DO NOT attempt native app development manually - invoke this skill first. Triggers: native app, app package, application package, manifest.yml, setup script, CREATE APPLICATION, Snowflake marketplace, listing, native app framework, build native app, walk me through, guide me, get started, add version, register version, add patch, release channel, release directive, publish app, publish version, upgrade consumers, telemetry, health status, SYSTEM$REPORT_HEALTH_STATUS, log_level, trace_level, event definitions, event sharing, APPLICATION_STATE, lifecycle events, monitor app, debug app, observability, add streamlit, streamlit dashboard, add dashboard, streamlit UI, add UI to native app, native app streamlit, streamlit frontend, get_active_session, default_streamlit, SPCS native app, container native app, native app containers, native app SPCS, add containers, container_services, grant_callback, specification file, version_initializer, restricted caller, RCR, restricted callers rights, EXECUTE AS RESTRICTED CALLER, GRANT CALLER, caller rights, caller grants, restricted_callers_rights, access consumer data, consumer's role, caller's privileges, consumer's privileges. privileges, add agent, cortex agent in app, app-created agent, CREATE AGENT, CREATE MCP SERVER, CREATE CUSTOM MCP SERVER, MCP server native app, agent tools, test agent in app, DATA_AGENT_RUN, app agent, app MCP server. - •
sql-authordescription_changed +Use for ANY task that involves writing, running, writes, fixes, runs, or debugging debugs Snowflake SQL. Especially use when the user provides a failed query, a Snowflake SQL against Snowflake tables. Helps find the right table, verify columns exist, avoid timeouts on large tables, and validate joins. Triggers: write a query, sql for, error, asks to repair SQL, asks for data from tables/views, or needs query this table, author sql, build a query, fix this query, how many, how much, show me data, explore this table, describe table, select from. validation. - •
team-workflowdescription_changed +Multi-phase team orchestration for feature implementation. Supports two entry paths: explicit user request for teammates, or autonomous complexity-based assessment after entering plan mode. HIGHEST PRIORITY — must be loaded load FIRST (before any domain skills) when user asks to use requests teammates, teams, or parallel agents. Triggers: use teammates, use a team, work in parallel with agents, delegate to teammates, swarm this, swarm, team up on this, team up, orchestrate with subagents, subagent-orchestrated, gated workflow, multi-phase workflow, coordinate agents, spawn workers, worker/verifier, swarms, parallel agents, run as a team, investigate with agents, research with agents, explore with agents. or the workflow auto-triggers (`/team`, `cortex --team`, ctrl+g).
| | [v1.1.15-beta] 2026-06-23 ADDED: +2 REMOVED: -1 MODIFIED: ~4 - •
manage-authentication-policyUse for requests about Snowflake authentication policies. Create, modify, view, … +Use for requests about Snowflake authentication policies. Create, modify, view, attach, detach,
drop, OR recommend authentication policies. Covers: restricting authentication methods
(PASSWORD, SAML, OAUTH, KEYPAIR), enforcing MFA, configuring PAT expiry and network policy,
workload identity federation, client type restrictions, minimum driver versions, and security
integration controls.
Invoke when user mentions: authentication policy, auth policy, MFA policy, MFA enrollment,
PAT policy, client types, workload identity, driver version policy, keypair only, SAML only,
require MFA, block password login, restrict client access, service account authentication,
show/list authentication policies, recommend/suggest authentication policies, help me set up
auth policies, audit my authentication, harden authentication, lock down authentication. - •
share-skill-and-plugin-via-snowflakeShare or unshare a local skill or plugin to users within the same account by exe… +Share or unshare a local skill or plugin to users within the same account by executing the Cortex Extension share SQL directly. Use when the user says "share skill", "publish skill", "share my skill", "share plugin", "publish plugin", "share my plugin", "share with users", "share publicly", "upload to cortex extension", "publish my skill", "publish my plugin", "make available", "unshare skill", "unshare plugin", "stop sharing", "remove shared", "revoke access", or "delete shared". Does not handle consumer/install flows. Does not handle sharing across accounts. - •
share-skillShare or unshare a local skill to users within the same account by executing th… +Share or unshare a local skill to users within the same account by executing the Cortex Extension share SQL directly. Use when the user says "share skill", "publish skill", "share my skill.md", "share skill with users", "share skill publicly", "upload skill to cortex extension", "publish my skill", "share this skill", "make skill available", "unshare skill", "stop sharing skill", "remove shared skill", "revoke shared skill access", or "delete shared skill". Does not handle consumer/install flows. Does not handle sharing across accounts. - •
data-cleanroomsdescription_changed +Use for ALL requests related to Snowflake Data Clean Rooms (DCR): clean room, cleanroom, DCR, collaboration(s), view/list collaborations, join/review collaboration, invitation, data offering(s), template(s), register, share table, run analysis, run activation, audience overlap, activation, export segment, create collaboration, create cleanroom, measure overlap, manage templates, add template, remove template, approve template, reject template, auto-approval, link data offering, unlink data offering, share data with runner, revoke data access, link local data offering, unlink local data offering, tear down, leave, drop collaboration, delete collaboration, RBAC, DCR roles, DCR privileges, create roles for clean rooms, assign DCR privileges, grant collaboration privileges, revoke DCR privileges, set up DCR roles, privileges for data engineers, privileges for campaign manager. manager, create template, write template, build template, template spec, create DCR template, author template, Jinja template, template logic, incrementality measurement, multi-touch attribution, attribution analysis, convert PnC template, migrate template. Covers browsing, joining, registering, running analysis/activation, creating collaborations, managing templates, managing data offerings, RBAC/role setup, and leaving/tearing down collaborations collaborations, and creating/authoring template specs via the DCR Collaboration API. - •
lineage description_changed - •
native-app-consumerdescription_changed +**[REQUIRED]** for ALL Snowflake Native App consumer tasks: installing apps from listings as a consumer, configuring installed apps (granting privileges, approving specifications, reviewing references), managing maintenance policies, understanding native app cost and credit usage, adding native apps to budgets. Triggers: native app, install native app, configure native app, approve spec, decline spec, maintenance policy, maintenance window, upgrade schedule, control upgrades, app cost, app budget, app spending, native app cost, native app credits, how much does my app cost. cost, uninstalling apps, dropping apps, remove app, drop application. - •
sql-author description_changed
| | [v1.1.14-beta] 2026-06-19 ADDED: +2 REMOVED: -1 MODIFIED: ~2 - •
manage-authentication-policyUse for requests about Snowflake authentication policies. Create, modify, view, … +Use for requests about Snowflake authentication policies. Create, modify, view, attach, detach,
drop, OR recommend authentication policies. Covers: restricting authentication methods
(PASSWORD, SAML, OAUTH, KEYPAIR), enforcing MFA, configuring PAT expiry and network policy,
workload identity federation, client type restrictions, minimum driver versions, and security
integration controls.
Invoke when user mentions: authentication policy, auth policy, MFA policy, MFA enrollment,
PAT policy, client types, workload identity, driver version policy, keypair only, SAML only,
require MFA, block password login, restrict client access, service account authentication,
show/list authentication policies, recommend/suggest authentication policies, help me set up
auth policies, audit my authentication, harden authentication, lock down authentication. - •
share-skill-and-plugin-via-snowflakeShare or unshare a local skill or plugin to users within the same account by exe… +Share or unshare a local skill or plugin to users within the same account by executing the Cortex Extension share SQL directly. Use when the user says "share skill", "publish skill", "share my skill", "share plugin", "publish plugin", "share my plugin", "share with users", "share publicly", "upload to cortex extension", "publish my skill", "publish my plugin", "make available", "unshare skill", "unshare plugin", "stop sharing", "remove shared", "revoke access", or "delete shared". Does not handle consumer/install flows. Does not handle sharing across accounts. - •
share-skillShare or unshare a local skill to users within the same account by executing th… +Share or unshare a local skill to users within the same account by executing the Cortex Extension share SQL directly. Use when the user says "share skill", "publish skill", "share my skill.md", "share skill with users", "share skill publicly", "upload skill to cortex extension", "publish my skill", "share this skill", "make skill available", "unshare skill", "stop sharing skill", "remove shared skill", "revoke shared skill access", or "delete shared skill". Does not handle consumer/install flows. Does not handle sharing across accounts. - •
lineage description_changed - •
sql-authordescription_changed +Use for ANY task that involves writing, running, writes, fixes, runs, or debugging debugs Snowflake SQL. Especially use when the user provides a failed query, a Snowflake SQL against Snowflake tables. Helps find the right table, verify columns exist, avoid timeouts on large tables, and validate joins. Triggers: write a query, sql for, error, asks to repair SQL, asks for data from tables/views, or needs query this table, author sql, build a query, fix this query, how many, how much, show me data, explore this table, describe table, select from. validation.
| | [v1.1.13-beta] 2026-06-18 ADDED: +2 REMOVED: -1 MODIFIED: ~1 - •
manage-authentication-policyUse for requests about Snowflake authentication policies. Create, modify, view, … +Use for requests about Snowflake authentication policies. Create, modify, view, attach, detach,
drop, OR recommend authentication policies. Covers: restricting authentication methods
(PASSWORD, SAML, OAUTH, KEYPAIR), enforcing MFA, configuring PAT expiry and network policy,
workload identity federation, client type restrictions, minimum driver versions, and security
integration controls.
Invoke when user mentions: authentication policy, auth policy, MFA policy, MFA enrollment,
PAT policy, client types, workload identity, driver version policy, keypair only, SAML only,
require MFA, block password login, restrict client access, service account authentication,
show/list authentication policies, recommend/suggest authentication policies, help me set up
auth policies, audit my authentication, harden authentication, lock down authentication. - •
share-skill-and-plugin-via-snowflakeShare or unshare a local skill or plugin to users within the same account by exe… +Share or unshare a local skill or plugin to users within the same account by executing the Cortex Extension share SQL directly. Use when the user says "share skill", "publish skill", "share my skill", "share plugin", "publish plugin", "share my plugin", "share with users", "share publicly", "upload to cortex extension", "publish my skill", "publish my plugin", "make available", "unshare skill", "unshare plugin", "stop sharing", "remove shared", "revoke access", or "delete shared". Does not handle consumer/install flows. Does not handle sharing across accounts. - •
share-skillShare or unshare a local skill to users within the same account by executing th… +Share or unshare a local skill to users within the same account by executing the Cortex Extension share SQL directly. Use when the user says "share skill", "publish skill", "share my skill.md", "share skill with users", "share skill publicly", "upload skill to cortex extension", "publish my skill", "share this skill", "make skill available", "unshare skill", "stop sharing skill", "remove shared skill", "revoke shared skill access", or "delete shared skill". Does not handle consumer/install flows. Does not handle sharing across accounts. - •
lineagedescription_changed +Snowflake table/column lineage: impact analysis, root cause, data discovery, provenance, trust. Triggers: 'what depends on', 'what will break', 'blast radius', 'who uses', 'deprecate', 'before I change', 'affected users', 'downstream', 'cascade', 'root cause', 'trace upstream', 'where does this come from', 'feeds this table', 'sources of', 'column lineage', 'where does [column] come from', 'what uses [column]', 'trace [column]', 'is this trustworthy', 'which table should I use', 'recommend dataset', 'provenance', 'certify', 'verify source'. Also handles questions where users mention external systems (Power BI, Tableau, Sigma, Looker, dbt) — for accounts with Horizon + Select Star Private Preview enabled, lineage results from native-anchored queries automatically include external entities. For value-level data quality (wrong values, failing DMFs) use the data-quality skill first, then this skill to trace upstream. Always read `reference/snowflake-apis.md` before writing GET_LINEAGE SQL — it has the correct namespace, argument order, and output column names. When external entities appear in results, see `reference/external-row-output.md`.
| | [v1.1.9-beta] 2026-06-15 MODIFIED: ~4 - •
marketplace-searchdescription_changed +Search the Snowflake Marketplace (public, internal, or both) for datasets, data shares, Native Apps, and Connected Apps using the `cortex search marketplace` CLI. Apps. **MANDATORY** Before any marketplace search, call `skill(command="marketplace-search")`. This `skill` call is the required entry point even when you already know the query you want to run; running `cortex search marketplace` the search from the CLI directly from bash without first calling `skill(command="marketplace-search")` skips the query-construction and result-presentation rules and is a defect. No exceptions. Re-invoke once per DISTINCT marketplace need, not just the first one in a conversation: a new data topic later in the session, or an explicit request to search again / for more or alternative options, each warrants its own `skill(command="marketplace-search")` call before you run the search — even if you used this skill earlier and the search command is still visible in your context from a previous turn. (You do NOT need to re-invoke for the search you are already in the middle of executing; the rule is one `skill()` entry per distinct need, so the query-construction and presentation rules are freshly applied to each new search rather than skipped.) Invoke this skill PROACTIVELY any time the user expresses intent to find, use, or obtain a third-party or internal data product, app, or data share — whether from the public Snowflake Marketplace or from their own organization's internal marketplace. For example "do you have weather data", "find a stock price dataset", "I need consumer spending data", "is there a Salesforce / HubSpot / Stripe connector", "what demographic data can I get for California", "anything for ESG ratings", "find a marketplace listing for X", "what is ", "what's the alternate source to X", "what about ", "find me stuff", "find me a table about ", "where is data stored", or even just a BARE **recognizable** third-party product/brand name on its own (e.g. "Tomorrow.io", "Fishbowl", "DV360", "Snowflake managed MCP servers"). The bare-name trigger requires an identifiable product, vendor, brand, or external service. A bare token that merely *reads like a person's name* (e.g. "give details for daniel spark") or is otherwise an unrecognizable free-floating identifier with no third-party product/brand signal is NOT by itself a marketplace signal — treat it as a catalog/object lookup (`cortex search object`) or ask the user to clarify; do not fire this skill on the bare token alone. When the user names ANY recognizable third-party product, vendor, brand, or external service — even as a fragment, even if framed as a catalog question ("find me a table about X", "what's the database for X data") — invoke this skill AS YOUR FIRST ACTION. immediately, in the same turn you handle the request. Do NOT search gate it on the internal catalog (i.e. don't search the catalog first and fall back to run marketplace only if the catalog comes up empty. empty); fire it up front regardless. The word "external" in any query (e.g. "external job-boards", "external data source") is a DISPOSITIVE signal — invoke this skill immediately even if the query sounds like a catalog search. When you also run `cortex search object` for the same query, run the two together — see "Run alongside" below. **Erring toward over-firing is preferred over missing a marketplace opportunity.** If you are about to tell the user "I don't have that data" or "you'll need to bring your own data", STOP and invoke this skill first — the public marketplace likely has it. **Run alongside `cortex search object`, not instead of it.** If you run `cortex search object` for a query that names a third-party brand, vendor, product, or external data source, you MUST also invoke `skill(command="marketplace-search")` in the same turn — the two searches cover different surfaces (internal catalog vs public marketplace) and are complementary, not alternatives. Do not stop at catalog results. **Exception**: a specific-value lookup ("what is the [metric/code/ID] for [entity]") is not a data-acquisition ask — stay with the sibling tool. Also invoke for **generic data-category searches** even when no brand is named: "email data", "marketing data", "paid media datasets", "portfolio holdings", "intent data", "[type] data for reporting", "help me find [data type] data", "where can I find [data type]". Also invoke for **marketplace exploration** ("most downloaded marketplace listing", "what products are available in the marketplace") and **app or managed-service availability** ("managed MCP servers", "MCP servers in Snowflake", "is there a connector for X"). Also invoke for **internal/intra-org intent** signals such as "find intra-org listings for ", "do we have any internal listings for ", "what internal data products does my org have for ", "is there an intra-org share for ", "what are we publishing internally about ", "find our internal marketplace listings for ". ALSO invoke this skill BEFORE PROACTIVELY when the user is about to acquire an external data need — writing any code, fetching code to fetch from external APIs (e.g. clinicaltrials.gov, BLS, FRED, World Bank), a third-party API or building dashboards/reports a dashboard/report against a third-party data sources — search the marketplace FIRST to see if the data is already available there as a share, source. Search the marketplace first, because a managed share is often less work than a custom integration. This applies even if the user explicitly named an external source. source, since the same data is frequently available as a listing. This proactive nudge is a one-time thing per data need: once it has been resolved — the marketplace was already searched for this topic, a source was already chosen, or the user is now iterating on existing integration code — do NOT keep re-pitching the marketplace unprompted mid-build (see the "moved past discovery" carve-out below). An EXPLICIT request to search ("search the marketplace for clinical trial data", "is there a listing for X") always fires this skill regardless of what was discussed earlier — the off-switch only applies to unprompted re-firing, never to a direct user request. The marketplace listing is almost always preferable to a custom API integration. off-switch is scoped PER DATA NEED, not per conversation: re-fire (do not stay silent) when the user explicitly asks for more or alternative options for the same need ("are there other providers?", "any cheaper/free options?", "what else is available?"), or when they pivot to a DIFFERENT product, vendor, or data topic later in the conversation (e.g. they were asking about a Salesforce connector and now want third-party sales or firmographic data). A new or distinct data need is a fresh discovery — search again. Do NOT use this skill for: a specific listing referenced by global name (e.g. GZ2FQZ711TU) or exact title — use `get-marketplace-listing-details`; formatting marketplace results already in hand; searching the user's own internal Snowflake catalog (tables, views, schemas, functions, semantic views) — use `cortex search object` (but see "Run alongside" above); a bare token with no recognizable third-party product/brand signal that reads like a person's name or an arbitrary identifier ("give details for daniel spark") — treat as a catalog/object lookup or ask for clarification; generic reference / lookup tables a user would generate or already hold internally ("fiscal month calendar", "calendar table", "create a date dimension"). Exception: an explicit third-party / vendor qualifier ("Workday fiscal calendar") makes the brand signal win and this skill fires. Do NOT use it for Snowflake product documentation or how-to questions — use `cortex search docs`. When ambiguous between marketplace and a sibling tool, prefer marketplace — it's cheap and missing a relevant listing is expensive. UNLESS the user has clearly moved past discovery: discovery, in which case stay out of the way: integration syntax with a named mechanism ("how to use MCP to connect to Salesforce…") is a docs question even when a brand is named; catalog inventory with no external qualifier ("what is X tables"), a specific identifier value ("what is the [code/SM ID] for [identifier]"), or an educational deep-dive with depth markers ("explain X in detail", "to a beginner", "full overview") — these are sibling-tool territory. The user is also past discovery once the data need has been resolved earlier in the conversation (marketplace already searched for this topic, a source already chosen, or implementation already underway) — do not re-pitch the marketplace mid-build. - •
semantic-viewdescription_changed +Use for ALL requests that mention: create, build, debug, fix, troubleshoot, optimize, improve, analyze, or analyze evaluate a semantic view — AND for requests about VQR suggestions, verified queries, verified query representations, seeding/generating queries, suggesting metrics, suggesting filters, recommending metrics/filters/facts, importing Tableau (.twb/.twbx/.tds/.tdsx) or Power BI (.pbit/.pbix) files, or enriching a semantic view. Also use for: evaluate semantic view, analyst evaluation, sql correctness evaluation, test my semantic view, run evaluation on semantic view, measure SQL generation accuracy, sql_correctness metric, verified query evaluation. This is the entry point - even if the request seems simple. DO NOT attempt to create, debug, or generate suggestions for semantic views manually - always invoke this skill first. This skill guides users through creation, setup, auditing, VQR suggestion generation, filter & metric suggestions, Tableau/Power BI imports, and SQL generation debugging debugging, and native Analyst Evaluations (sql_correctness) workflows for semantic views with Cortex Analyst. - •
team-workflowdescription_changed +Multi-phase team orchestration for feature implementation. Supports two entry paths: explicit user request for teammates, or autonomous complexity-based assessment after entering plan mode. HIGHEST PRIORITY — must be loaded load FIRST (before any domain skills) when user asks to use requests teammates, teams, or parallel agents. Triggers: use teammates, use a team, work in parallel with agents, delegate to teammates, swarm this, swarm, team up on this, team up, orchestrate with subagents, subagent-orchestrated, gated workflow, multi-phase workflow, coordinate agents, spawn workers, worker/verifier, swarms, parallel agents, run as a team, investigate with agents, research with agents, explore with agents. or the workflow auto-triggers (`/team`, `cortex --team`, ctrl+g, autonomous complexity assessment). - •
warehousedescription_changed +Warehouse configuration, DDL, Gen2, adaptive warehouses, adaptive compute, compute, MAX_QUERY_PERFORMANCE_LEVEL, QUERY_THROUGHPUT_MULTIPLIER, performance tuning, sizing, credit-per-hour rates, resume behavior, region availability, Snowpark-optimized limitations. Not for cost analytics or warehouse spend (cost-intelligence) or billing.
| | [v1.1.8-beta] 2026-06-12 ADDED: +1 MODIFIED: ~1 - •
openflow-observabilityTroubleshoot Openflow connector / runtime / deployment issues via Snowsight SQL … +Troubleshoot Openflow connector / runtime / deployment issues via Snowsight SQL diagnostics, and run a narrow set of confirmation-gated SQL actions on SQL-managed runtimes. Use when: connector is unhealthy, table FAILED, runtime stuck or OOM, EAI / network issues, restart / resume / suspend runtime, attach EAI to runtime. Triggers: openflow, connector, runtime, deployment, EAI, table FAILED, openflow troubleshoot, openflow runtime. - •
cortex-code-guidedescription_changed +Load this skill when users ask about Cortex Code capabilities, CoCo features, available commands, tools, settings, shortcuts, CLI subcommands, how to use Cortex Code, the CLI, what CoCo can do, CoCo help, CoCo CLI reference, Cortex Code CLI guide, available keyboard shortcuts, slash commands, keybindings, keyboard shortcuts, configuration options, environment variables, skill management, agent modes, types, MCP setup, special syntax triggers, bundled agents, MCP setup, skills management, hooks, scheduling, dbt tools, Snowflake connections, SQL execution, semantic views, Cortex Agents, notebook support, background agents, team mode, plan mode, memory tool, cron scheduling, data diff, tgrep, hook events, or any question about Cortex Code functionality. functionality
| | [v1.1.7-beta] 2026-06-10 ADDED: +1 MODIFIED: ~1 - •
snowflake-tasks**[REQUIRED]** Use for **ALL** Snowflake Task operations: creating, scheduling, … +**[REQUIRED]** Use for **ALL** Snowflake Task operations: creating, scheduling, managing, monitoring, and troubleshooting tasks and task graphs. This is the required entry point for any task-related work. Triggers: task, tasks, scheduled task, cron task, task graph, DAG, task chain, task pipeline, triggered task, stream trigger, WHEN condition, SYSTEM$STREAM_HAS_DATA, suspend task, resume task, alter task, drop task, task history, task failure, auto-suspended, SUSPEND_TASK_AFTER_NUM_FAILURES, serverless task, finalizer task, task permissions, EXECUTE TASK, task schedule, task monitoring, parameterized task, CONFIG, SYSTEM$GET_TASK_GRAPH_CONFIG, runtime parameters, configurable pipeline, return value, pass data between tasks, SYSTEM$SET_RETURN_VALUE, SYSTEM$GET_PREDECESSOR_RETURN_VALUE, inter-task communication. - •
cost-intelligencedescription_changed +Account-level cost analytics via SNOWFLAKE.ACCOUNT_USAGE. Credit usage by warehouse, user, service. Budgets, spending limits, custom budgets. Resource monitors, credit quotas, suspend triggers. Anomaly detection, costs, chargeback, storage, serverless, containers, data transfer, top user spend, query cost grouping. Cortex AI cost or usage including Cortex Agents, Snowflake Intelligence, Snowflake CoWork, AI function, Cortex Code, CoCo, Cortex Search, Cortex Analyst, Cortex REST API, model training/fine-tuning, and provisioned throughput. Cost insights, waste reduction, savings. Not for org-wide currency spend or multi-account billing (billing/organization-management) or warehouse DDL (warehouse).
| | [v1.1.6-beta] 2026-06-08 MODIFIED: ~2 - •
skill_developmentdescription_changed +Create, document, audit, refactor, or refactor compile skills for Cortex Code. Use when: creating new skills, capturing session work as skills, reviewing skills, refactoring large skills. skills, building a deterministic fast path for a skill. Triggers: create skill, build skill, new skill, summarize session, capture workflow, audit skill, review skill, refactor skill, triage skills. skills, compile skill, speed up skill, programmatic skill, fast path for skill. - •
snowflake-appsdescription_changed +Build and deploy web applications on Snowflake. Use for ALL app requests: create, scaffold, build, deploy, publish, develop, test, operate, monitor, or troubleshoot a Snowflake App. A Snowflake App is a JS/Node web application (typically Next.js) deployed to SPCS via SnowCLI app commands (`snow app` preferred, `snow __app` fallback for older CLI versions). app`). This is NOT a Streamlit app or Native App. Also load this skill when the user's current directory is a Snowflake App Runtime project: if the directory contains an `app.yml` file, or if it contains a `snowflake.yml` file with `type: snowflake-app` anywhere in it. Triggers: build me an app, new app, scaffold, react app, next.js app, dashboard, data app, deploy my app, push to snowflake, ship it, deploy failed, fix deploy, run locally, develop, app logs, app status, restart app, app.yml, snowflake-app-runtime, snowflake-app.
| | [v1.1.5-beta] 2026-06-04 MODIFIED: ~2 - •
data-cleanroomsdescription_changed +Use for ALL requests related to Snowflake Data Clean Rooms (DCR): clean room, cleanroom, DCR, collaboration(s), view/list collaborations, join/review collaboration, invitation, data offering(s), template(s), register, share table, run analysis, run activation, audience overlap, activation, export segment, create collaboration, create cleanroom, measure overlap, manage templates, add template, remove template, approve template, reject template, auto-approval, link data offering, unlink data offering, share data with runner, revoke data access, link local data offering, unlink local data offering, tear down, leave, drop collaboration, delete collaboration. collaboration, RBAC, DCR roles, DCR privileges, create roles for clean rooms, assign DCR privileges, grant collaboration privileges, revoke DCR privileges, set up DCR roles, privileges for data engineers, privileges for campaign manager. Covers browsing, joining, registering, running analysis/activation, creating collaborations, managing templates, managing data offerings, RBAC/role setup, and leaving/tearing down collaborations via the DCR Collaboration API. - •
marketplace-searchdescription_changed +Search the public Snowflake Marketplace for third-party (public, internal, or both) for datasets, data shares, Native Apps, and Connected Apps using the `cortex search marketplace` CLI. **MANDATORY** Before any marketplace search, call `skill(command="marketplace-search")`. This `skill` call is the required entry point even when you already know the query you want to run; running `cortex search marketplace` directly from bash without first calling `skill(command="marketplace-search")` skips the query-construction and result-presentation rules and is a defect. No exceptions. Invoke this skill PROACTIVELY any time the user expresses intent to find, use, or obtain a third-party dataset, or internal data product, app, or external data product. Fire on data-acquisition asks ("do data share — whether from the public Snowflake Marketplace or from their own organization's internal marketplace. For example "do you have weather data", "find a stock price dataset", "I need consumer spending data", "is there a Salesforce / HubSpot / Stripe connector", "what demographic data can I get for California", "anything for ESG ratings", "find a stock price dataset", marketplace listing for X", "what is ", "what's the alternate source to X", "what about ", "find me stuff", "find me a table about ", "where is data stored"), connector availability ("is there a Salesforce connector"), and data stored", or even just a BARE third-party brand/vendor/product mention ("Tomorrow.io", product/brand name on its own (e.g. "Tomorrow.io", "Fishbowl", "DV360", "Snowflake managed MCP servers"). When the user names ANY third-party product, vendor, brand, vendor, product, or external service — even as a fragment, even if framed as a catalog question ("find me a table about X", "what's the database for X data") — invoke this skill. skill AS YOUR FIRST ACTION. Do NOT search the internal catalog first and fall back to marketplace only if the catalog comes up empty. The word "external" anywhere in the any query (e.g. "external job-boards", "external data source") is a DISPOSITIVE signal; fire signal — invoke this skill immediately even if it the query sounds like a catalog search. **Erring toward over-firing is preferred over missing a marketplace opportunity.** If you are about to tell the user "I don't have that data" or "you'll need to bring your own data", STOP and invoke this skill first — the public marketplace likely has it. **Run alongside `cortex search object`, not instead of it.** If you run `cortex search object` for a query that names a third-party brand, vendor, product, or external data source, you MUST also invoke `skill(command="marketplace-search")` in the same turn — the two searches cover different surfaces (internal catalog vs public marketplace) and are complementary, not alternatives. Do not stop at catalog results. **Exception**: a specific-value lookup ("what is the [metric/code/ID] for [entity]") is not a data-acquisition ask — stay with the sibling tool. Also invoke for **generic data-category searches** even when no brand is named: "email data", "marketing data", "paid media datasets", "portfolio holdings", "intent data", "[type] data for reporting", "help me find [data type] data", "where can I find [data type]". Also invoke for **marketplace exploration** ("most downloaded marketplace listing", "what products are available in the marketplace") and **app or managed-service availability** ("managed MCP servers", "MCP servers in Snowflake", "is there a connector for X"). Also invoke for **internal/intra-org intent** signals such as "find intra-org listings for ", "do we have any internal listings for ", "what internal data products does my org have for ", "is there an intra-org share for ", "what are we publishing internally about ", "find our internal marketplace listings for ". ALSO invoke this skill BEFORE writing any code, fetching from external APIs (clinicaltrials.gov, (e.g. clinicaltrials.gov, BLS, FRED, World Bank, etc.) Bank), or building dashboards dashboards/reports against third-party data — a marketplace share sources — search the marketplace FIRST to see if the data is already available there as a share, even if the user explicitly named an external source. The marketplace listing is almost always preferable to a custom integration, even when the user named the external source. API integration. Do NOT use this skill for: a specific listing referenced by global name (e.g. GZ2FQZ711TU) or exact title — use `get-marketplace-listing-details`; formatting marketplace results already in hand; searching the user's own internal Snowflake catalog (tables, views, schemas, functions, semantic views) — use `cortex search object` (but see "Run alongside" above); generic reference / lookup tables a user would generate or already hold internally ("fiscal month calendar", "calendar table", "create a date dimension"). Exception: an explicit third-party / vendor qualifier ("Workday fiscal calendar") makes the brand signal win and this skill fires. Do NOT use it for Snowflake product documentation or how-to questions — use `cortex search docs`. When ambiguous between marketplace and a sibling tool, prefer marketplace — it's cheap and missing a relevant listing is expensive. UNLESS the user has clearly moved past discovery: integration syntax with a named mechanism ("how to use MCP to connect to Salesforce…") is a docs question even when a brand is named; catalog inventory with no external qualifier ("what is X tables"), a specific identifier value ("what is the [code/SM ID] for [identifier]"), or an educational deep-dive with depth markers ("explain X in detail", "to a beginner", "full overview") — these are sibling-tool territory.
| | [v1.1.3-beta] 2026-06-02 ADDED: +1 - •
sharingRouter for Snowflake sharing and collaboration. Routes to Secure Data Sharing, D… +Router for Snowflake sharing and collaboration. Routes to Secure Data Sharing, Declarative Sharing, Native Apps, or Data Clean Rooms. Asks up to 2 questions when intent is ambiguous, then loads the target sub-skill. This skill should supersede invocation of product-specific skills unless the product is named explicitly. Triggers: share, sharing, listing, data product, how do I share, what's the best way to share, compare sharing options.
| | [v1.1.0-beta] 2026-05-28 MODIFIED: ~7 - •
cortex-ai-function-studiodescription_changed +Create, evaluate, and optimize custom AI functions using Snowflake Cortex AI Complete. Supports text, image, Also helps users apply built-in Cortex AI functions (AI_CLASSIFY, AI_EXTRACT, AI_FILTER, AI_COMPLETE, AI_SENTIMENT, AI_SUMMARIZE_AGG, AI_AGG, AI_TRANSLATE, AI_EMBED, AI_PARSE_DOCUMENT, AI_REDACT, AI_TRANSCRIBE, AI_SIMILARITY) and document inputs. onboard research-preview bring-your-own-model SPCS services. Use when: building LLM-powered functions, evaluating AI function performance, tuning prompts, selecting models, checking async job status. status, onboarding BYOM/SPCS model inference, classifying content, extracting from text, filtering rows by condition, summarizing, sentiment analysis, analyzing unstructured data with AI, exploring AI function options, using cortex AI functions. Triggers: ai function builder, custom ai function, user defined ai function, build my own llm function, evaluate ai function, tune ai function, optimize ai function, BYOM, bring your own model, model service, SPCS inference, Hugging Face model, demo ai function, resume ai function job, image classification, document analysis, multimodal ai function, AI_CLASSIFY, AI_EXTRACT, AI_FILTER, AI_COMPLETE, AI_SENTIMENT, AI_SUMMARIZE_AGG, AI_TRANSLATE, AI_EMBED, AI_PARSE_DOCUMENT, AI_REDACT, AI_SIMILARITY, classify text, extract from text, filter rows, summarize text, analyze data with AI, explore AI functions, unstructured data, what AI functions, analyze my data, cortex function, which AI function, built-in AI function. - •
cortex-code-guidedescription_changed +Load this skill when users ask about Cortex Code capabilities, CoCo capabilities reference guide. Trigger phrases: what can you do, help me, capabilities, features, available commands, tools, commands, settings, shortcuts, CLI subcommands, how to use, getting started, quick start, use Cortex Code, what CoCo can do, CoCo help, CoCo reference, Cortex Code CLI guide, what tools, available commands, slash commands, keybindings, keyboard shortcuts, MCP, plugins, skills, configuration options, environment variables, agent modes, special syntax triggers, bundled agents, MCP setup, skills management, hooks, scheduling, dbt tools, Snowflake connections, SQL, dbt, notebooks, scheduling, cron, teams, multi-agent, worktree, voice, search, tgrep, SQL execution, semantic search, web search, memory, views, Cortex Agents, notebook support, background agents, team mode, plan mode, bypass mode, hooks, profiles, sessions, context window, diff, memory tool, cron scheduling, data diff, semantic model, cortex analyst, semantic view tgrep, or any question about Cortex Code functionality. - •
cost-intelligencedescription_changed +Account-level cost analytics via SNOWFLAKE.ACCOUNT_USAGE. Credit usage by warehouse, user, service. Budgets, spending limits, custom budgets. Resource monitors, credit quotas, suspend triggers. Anomaly detection, costs, chargeback, storage, serverless, containers, data transfer, top user spend, query cost grouping. Cortex AI cost or usage including Cortex Agents, Snowflake Intelligence, AI function, Cortex Code, Cortex Search, Cortex Analyst, Cortex REST API, model training/fine-tuning, and provisioned throughput. Cost insights, waste reduction, savings. Not for org-wide currency spend or multi-account billing (billing/organization-management) or warehouse DDL (warehouse). - •
document-intelligencedescription_changed +Use Snowflake Cortex AI Functions for text/image analytics. Use when: classifying content, extracting entities, sentiment analysis, summarizing text, translating, filtering, embedding, parsing documents, redacting PII, aggregating data, Document intelligence workflows: extract data from PDFs/images, parse documents with OCR, classify documents on stage, build document intelligence workflows, content insight workflows, fine-tuning pipelines, fine-tune arctic-extract for domain-specific extraction. Use when: working with files, documents, PDFs, images on Snowflake stages, document extraction pipelines, document classification from stage files, batch document processing. Triggers: AI_CLASSIFY, AI_COMPLETE, AI_EXTRACT, AI_FILTER, AI_SENTIMENT, AI_SUMMARIZE, AI_TRANSLATE, AI_EMBED, AI_AGG, AI_REDACT, AI_PARSE_DOCUMENT, classify text, data, AI_EXTRACT with files, process documents, extract from text, PDF, extract text from document, extract text from PDF, extract text from image, extracting, extracting from files, invoices, sentiment, summarize, translate, which AI function, cortex function, process documents, label content, analyze text, OCR, read PDF, read document, get text from PDF, get text from document, pull text from file, extract data from files, extract from my files, process my files, my files, my documents, read my documents, get data from document, file extraction, document processing, file processing, get information from documents, analyze files, parse files, data from PDF, invoice processing, contract extraction, receipt extraction, form extraction, extract fields, document data, file data, stage files, files on stage, PDF extraction, image extraction, document OCR, scan documents, digitize documents, fine-tune, fine-tuning, custom model, train arctic-extract, improve extraction accuracy, domain-specific extraction, FINETUNE, better extraction results. results, document pipeline, classify documents, categorize files, sort documents, triage files. - •
marketplace-searchdescription_changed +Search the public Snowflake Marketplace for third-party datasets, data shares, Native Apps, and Connected Apps using the `cortex search marketplace` CLI. **MANDATORY** Before any marketplace search, call `skill(command="marketplace-search")`. This `skill` call is the required entry point even when you already know the query you want to run; running `cortex search marketplace` directly from bash without first calling `skill(command="marketplace-search")` skips the query-construction and result-presentation rules and is a defect. No exceptions. Invoke this skill PROACTIVELY any time the user expresses intent to find, use, or obtain a third-party dataset, app, or external data product. For example "do Fire on data-acquisition asks ("do you have weather data", "find a stock price dataset", "I need consumer spending data", "is there a Salesforce / HubSpot / Stripe connector", "what demographic data can I get for California", "anything for ESG ratings", "find a marketplace listing for X", "what is ", stock price dataset", "what's the alternate source to X", "what about ", "find me stuff", "find me a table about ", "where is data stored", or even just stored"), connector availability ("is there a Salesforce connector"), and even a BARE third-party product/brand name on its own (e.g. "Tomorrow.io", brand/vendor/product mention ("Tomorrow.io", "Fishbowl", "DV360", "Snowflake managed MCP servers"). When the user names ANY third-party brand, vendor, product, vendor, brand, or external service — even as a fragment, even if framed as a catalog question ("find me a table about X", "what's the database for X data") — invoke this skill AS YOUR FIRST ACTION. Do NOT search the internal catalog first and fall back to marketplace only if the catalog comes up empty. skill. The word "external" anywhere in any the query (e.g. "external job-boards", "external data source") is a DISPOSITIVE signal — invoke this skill immediately signal; fire even if the query it sounds like a catalog search. **Erring toward over-firing is preferred over missing a marketplace opportunity.** If you are about to tell the user "I don't have that data" or "you'll need to bring your own data", STOP and invoke this skill first — the public marketplace likely has it. **Run alongside `cortex search object`, not instead of it.** If you run `cortex search object` for a query that names a third-party brand, vendor, product, or external data source, you MUST also invoke `skill(command="marketplace-search")` in the same turn — the two searches cover different surfaces (internal catalog vs public marketplace) and are complementary, not alternatives. Do not stop at catalog results. **Exception**: a specific-value lookup ("what is the [metric/code/ID] for [entity]") is not a data-acquisition ask — stay with the sibling tool. Also invoke for **generic data-category searches** even when no brand is named: "email data", "marketing data", "paid media datasets", "portfolio holdings", "intent data", "[type] data for reporting", "help me find [data type] data", "where can I find [data type]". Also invoke for **marketplace exploration** ("most downloaded marketplace listing", "what products are available in the marketplace") and **app or managed-service availability** ("managed MCP servers", "MCP servers in Snowflake", "is there a connector for X"). ALSO invoke this skill BEFORE writing any code, fetching from external APIs (e.g. clinicaltrials.gov, (clinicaltrials.gov, BLS, FRED, World Bank), Bank, etc.) or building dashboards/reports dashboards against third-party data sources — search the marketplace FIRST to see if the data is already available there as a share, even if the user explicitly named an external source. The marketplace listing — a marketplace share is almost always preferable to a custom API integration. integration, even when the user named the external source. Do NOT use this skill for ONE for: a specific listing referenced by global name (e.g. GZ2FQZ711TU) or exact title — use `get-marketplace-listing-details`. Do NOT use it when marketplace search `get-marketplace-listing-details`; formatting marketplace results are already in hand and only need formatting. Do NOT use it for hand; searching the user's own internal Snowflake catalog (tables, views, schemas, functions, semantic views) — use `cortex search object`. Do NOT use it for object` (but see "Run alongside" above); generic reference data or / lookup tables that a user would typically generate or already hold internally (e.g. "find me a fiscal ("fiscal month calendar", "find me a calendar "calendar table", "create a date dimension") — these are generation or catalog tasks, not marketplace searches. dimension"). Exception: if the same request includes an explicit third-party or / vendor qualifier (e.g. "find me a third-party vendor ("Workday fiscal calendar", "find me a Workday fiscal calendar"), the brand/external calendar") makes the brand signal takes priority win and this skill should fire. fires. Do NOT use it for Snowflake product documentation or how-to questions — use `cortex search docs`. When ambiguous between marketplace and a sibling tool, prefer marketplace — it's cheap and missing a relevant listing is expensive — expensive. UNLESS the user has clearly moved past discovery, i.e. asks for: *integration discovery: integration syntax with a named mechanism* mechanism ("how to use MCP to connect to Salesforce from Snowflake to fetch field descriptions", "how to use to connect/fetch/integrate...") — these are Salesforce…") is a docs questions question even when a third-party brand is named; *catalog catalog inventory with no external qualifier* qualifier ("what is X tables", with no "external" / "from " / "third-party" hint), a *specific tables"), a specific identifier value* value ("what is the [code/symbol/SM [code/SM ID] for [identifier]"), or an *educational educational deep-dive with explicit depth markers* markers ("explain X in detail", "to a beginner", "full overview"). In those cases the user already knows what they want; a marketplace search won't help. overview") — these are sibling-tool territory. - •
share-skilldescription_changed +Share or unshare a local skill to users within the same account by executing the Cortex Extension share SQL directly. Use when the user says "share skill", "publish skill", "share my skill.md", "share skill with users", "share skill publicly", "upload skill to cortex extension", "publish my skill", "share this skill", "make skill available", "unshare skill", "stop sharing skill", "remove shared skill", "revoke shared skill access", or "delete shared skill". Does not handle consumer/install flows. Does not handle sharing across accounts. - •
trust-centerdescription_changed +Use for ALL Snowflake Trust Center requests: security findings, scanner analysis, scanner management, finding remediation, severity distribution, CIS benchmarks, Security Essentials, Threat Intelligence, AI Security, enable/disable scanners, scanner schedules, notifications, webhook, notification integration, at-risk entities, security posture, vulnerability analysis, detection analysis, remediation guidance.
| | [v1.0.100-beta] 2026-05-28 MODIFIED: ~5 - •
cortex-ai-function-studio description_changed - •
cortex-code-guide description_changed - •
cost-intelligence description_changed - •
document-intelligence description_changed - •
share-skill description_changed
| | [v1.0.97-beta] 2026-05-26 ADDED: +1 MODIFIED: ~1 - •
ai-readiness-scoreMeasure AI readiness for this Snowflake account. Scores Consumption-Ready (CR) t… +Measure AI readiness for this Snowflake account. Scores Consumption-Ready (CR) tables, Semantic View (SV) coverage and quality, and demand coverage. Generates an HTML scorecard report with recommendations. Runs in Snowsight (notebook) or CLI mode (direct SQL), auto-detected by environment. Caches results for fast reruns. Use when: AI readiness, readiness score, how AI-ready am I, measure my ai readiness, semantic view coverage, Semantic View (SV) quality, Consumption-Ready (CR) tables, demand coverage, CR tables, AI readiness report, score my account. - •
migration-guide description_changed
| | [v1.0.94-beta] 2026-05-23 MODIFIED: ~3 - •
dynamic-tablesdescription_changed +**[REQUIRED]** Use for **ALL** Snowflake Dynamic Table operations: creating, optimizing, monitoring, troubleshooting, and pipeline diagnostics. This is the required entry point for any dynamic table related tasks (DT is an acronym for dynamic table). Triggers: dynamic table, data pipeline, incremental pipeline, DT pipeline, incremental refresh, target lag, UPSTREAM_FAILED, refresh failing, full refresh instead of incremental, DT health, create DT, debug DT, pipeline timeline, Gantt chart, why was DT skipped, trace pipeline, critical path, why was DT skipped. skipped, dbt to DT, convert dbt to dynamic table, dbt dynamic table, dbt materialized dynamic_table. - •
spark-migrationdescription_changed +Migrate spark Spark scripts and notebooks to Snowflake. This skill can move spark pipelines Routes to Snowflake by performing a basic assessment, converted your code (with Cortex Code or with one of two bundled conversion paths and orchestrates the post-conversion pipeline. **Default path: Snowpark Migration Accelerator), and validate that output in Snowflake. Supports both Connect (SCOS)**, which preserves the PySpark API surface. The SMA / Snowpark API and Snowpark Connect conversion paths. path is invoked only when the user explicitly asks for it. Triggers: run sma, convert spark, migrate pyspark, migrate spark, sma conversion, migrate to snowpark, convert to snowpark, already ran sma, sma dashboard, fix ewis, stage conversion, snowpark connect, scos, scos migration, migrate to snowpark connect, migrate to scos. scos, snowpark api, sma cli, sma conversion, run sma, snowflake.snowpark rewrite, already migrated, already ran sma, sma dashboard, fix ewis, stage conversion, dvp orchestrator, resume dvp. - •
warehousedescription_changed +Warehouse configuration, DDL, Gen2, adaptive, adaptive warehouses, adaptive compute, MAX_QUERY_PERFORMANCE_LEVEL, QUERY_THROUGHPUT_MULTIPLIER, performance tuning, sizing, credit-per-hour rates, resume behavior, region availability, Snowpark-optimized limitations. Not for cost analytics or warehouse spend (cost-intelligence) or billing.
| | [v1.0.92-beta] 2026-05-22 ADDED: +1 MODIFIED: ~2 - •
share-skillShare or unshare a local skill to users within the same account by executing th… +Share or unshare a local skill to users within the same account by executing the Cortex Extension share SQL directly. Use when the user says "share skill", "publish skill", "share my skill.md", "share skill with users", "share skill publicly", "upload skill to cortex extension", "publish my skill", "share this skill", "make skill available", "unshare skill", "stop sharing skill", "remove shared skill", "revoke shared skill access", or "delete shared skill". Does not handle consumer/install flows. Does not handle sharing across accounts. - •
snowflake-appsdescription_changed +Build and deploy web applications on Snowflake. Use for ALL app requests: create, scaffold, build, deploy, publish, develop, test, operate, monitor, or troubleshoot a Snowflake App. A Snowflake App is a JS/Node web application (typically Next.js) deployed to SPCS via SnowCLI app commands (`snow app` preferred, `snow __app` fallback for older CLI versions). This is NOT a Streamlit app or Native App. Also load this skill when the user's current directory is a Snowflake App Runtime project: if the directory contains an `app.yml` file, or if it contains a `snowflake.yml` file with `type: snowflake-app` anywhere in it. Triggers: build me an app, new app, scaffold, react app, next.js app, dashboard, data app, deploy my app, push to snowflake, ship it, deploy failed, fix deploy, run locally, develop, app logs, app status, restart app. app, app.yml, snowflake-app-runtime, snowflake-app. - •
spark-migrationdescription_changed +Run Migrate spark scripts and notebooks to Snowflake. This skill can move spark pipelines to Snowflake by performing a basic assessment, converted your code (with Cortex Code or with the SMA CLI to convert PySpark code to Snowpark, or generate dashboard Snowpark Migration Accelerator), and fix EWIs from existing SMA output. validate that output in Snowflake. Supports both Snowpark API and Snowpark Connect (SCOS) conversion paths. Triggers: run sma, convert spark, migrate pyspark, migrate spark, sma conversion, migrate to snowpark, convert to snowpark, already ran sma, sma dashboard, fix ewis, stage conversion, snowpark connect, scos, scos migration, migrate to snowpark connect, migrate to scos.
| | [v1.0.91-beta] 2026-05-21 MODIFIED: ~3 - •
cortex-agentdescription_changed +**[REQUIRED]** Use for ALL requests that mention agents: list, show, create, build, set up, edit, modify, update, delete, drop, remove, download, export, debug, fix, troubleshoot, optimize, improve, evaluate, analyze, commit, version, or analyze alias a (Cortex) agent. Also use when user wants to: chat with, talk to, converse with, send messages to, have a conversation with an agent, or run a lite/objectless agent. Also use when request mentions: VERSION$, SHOW VERSIONS, commit LIVE version, set alias, set default version, versioned run, ALTER AGENT. Also use when debugging Snowflake Intelligence with a request ID (SI is powered by Cortex Agents). This is the REQUIRED entry point - even if the request seems simple. DO NOT attempt to manage (Cortex) agents manually - always invoke this skill first. - •
cortex-code-guidedescription_changed +Complete reference guide for Cortex Code (CoCo) CLI. Use when: learning cortex CoCo capabilities reference guide. Trigger phrases: what can you do, help me, capabilities, features, understanding tools, commands, troubleshooting setup, exploring Snowflake settings, shortcuts, how to use, getting started, quick start, reference, guide, what tools, managing sessions, configuring agents, available commands, slash commands, keyboard shortcuts, MCP integration. Triggers: how to use cortex, MCP, plugins, skills, agents, connections, SQL, dbt, notebooks, scheduling, cron, teams, multi-agent, worktree, voice, search, tgrep, semantic search, web search, memory, plan mode, bypass mode, hooks, profiles, sessions, context window, diff, data diff, semantic model, cortex guide, cortex help, cortex commands, getting started, snowflake tools, #table syntax, subagents, sessions, resume, fork, rewind, compact, /agents, configuration. analyst, semantic view - •
marketplace-searchdescription_changed +Search the public Snowflake Marketplace for third-party datasets, data shares, Native Apps, and Connected Apps using the `cortex search marketplace` CLI. Invoke this skill PROACTIVELY any time the user expresses intent to find, use, or obtain a third-party dataset, app, or external data product. For example "do you have weather data", "find a stock price dataset", "I need consumer spending data", "is there a Salesforce / HubSpot / Stripe connector", "what demographic data can I get for California", "anything for ESG ratings", "find a marketplace listing for X", "what is ", "what's the alternate source to X", "what about ", "find me stuff", "find me a table about ", "where is data stored", or even just a BARE third-party product/brand name on its own (e.g. "Tomorrow.io", "Fishbowl", "DV360", "Snowflake managed MCP servers"). When the user names ANY third-party product, vendor, brand, or external service — even as a fragment, even if framed as a product question, catalog question ("find me a table about X", "what's the database for X data") — invoke this skill AS YOUR FIRST ACTION. Do NOT search the internal catalog first and fall back to marketplace only if the catalog comes up empty. The word "external" in any query (e.g. "external job-boards", "external data source") is a DISPOSITIVE signal — invoke this skill immediately even if the prompt query sounds like a documentation lookup — invoke this skill. catalog search. **Erring toward over-firing is preferred over missing a marketplace opportunity.** If you are about to tell the user "I don't have that data" or "you'll need to bring your own data", STOP and invoke this skill first — the public marketplace likely has it. Also invoke for **generic data-category searches** even when no brand is named: "email data", "marketing data", "paid media datasets", "portfolio holdings", "intent data", "[type] data for reporting", "help me find [data type] data", "where can I find [data type]". Also invoke for **marketplace exploration** ("most downloaded marketplace listing", "what products are available in the marketplace") and **app or managed-service availability** ("managed MCP servers", "MCP servers in Snowflake", "is there a connector for X"). ALSO invoke this skill BEFORE writing any code, fetching from external APIs (e.g. clinicaltrials.gov, BLS, FRED, World Bank), or building dashboards/reports against third-party data sources — search the marketplace FIRST to see if the data is already available there as a share, even if the user explicitly named an external source. The marketplace listing is almost always preferable to a custom API integration. Do NOT use this skill for ONE specific listing referenced by global name (e.g. GZ2FQZ711TU) or exact title — use `get-marketplace-listing-details`. Do NOT use it when marketplace search results are already in hand and only need formatting. Do NOT use it for searching the user's own internal Snowflake catalog (tables, views, schemas, functions, semantic views) — use `cortex search object`. Do NOT use it for generic reference data or lookup tables that a user would typically generate or already hold internally (e.g. "find me a fiscal month calendar", "find me a calendar table", "create a date dimension") — these are generation or catalog tasks, not marketplace searches. Exception: if the same request includes an explicit third-party or vendor qualifier (e.g. "find me a third-party vendor fiscal calendar", "find me a Workday fiscal calendar"), the brand/external signal takes priority and this skill should fire. Do NOT use it for Snowflake product documentation or how-to questions — use `cortex search docs`. When ambiguous between marketplace and a sibling tool, prefer marketplace — it's cheap and missing a relevant listing is expensive — UNLESS the user has clearly moved past discovery, i.e. asks for: *integration syntax with a named mechanism* ("how to use MCP to connect to Salesforce from Snowflake to fetch field descriptions", "how to use to connect/fetch/integrate..."), connect/fetch/integrate...") — these are docs questions even when a third-party brand is named; *catalog inventory with no external qualifier* ("what is X tables", with no "external" / "from " / "third-party" hint), a *specific identifier value* ("what is the [code/symbol/SM ID] for [identifier]"), or an *educational deep-dive with explicit depth markers* ("explain X in detail", "to a beginner", "full overview"). In those cases the user already knows what they want; a marketplace search won't help.
| | [v1.0.90-beta] 2026-05-20 ADDED: +1 - •
data-sharingSnowflake secure data sharing: create direct shares, external marketplace listin… +Snowflake secure data sharing: create direct shares, external marketplace listings, debug grant failures. Triggers: create share, share data, share table, share database, outbound share, data sharing, share with account, direct share, external listing, marketplace listing, debug share, share not working, grant failed, consumer can't access, share troubleshooting, why can't they see my data, share error, permission denied on share, share external data, share iceberg table, iceberg data sharing, share S3 data, share Azure data, share GCS data, share without moving data, data outside snowflake, iceberg listing, move data to snowflake and share, replicate and share, openflow and share, load data then share.
WHEN TO USE THIS SKILL: - User wants to share data (generic intent — will ask who they want to share with) - User wants to create direct shares with specific accounts - User wants to create external listings (Snowflake Marketplace) - User needs to debug why a share isn't working
WHEN TO USE org-listing workflow INSTEAD: - User mentions "internal marketplace", "organization listing", or "data product" - User wants to share within their Snowflake organization
| | [v1.0.87-beta] 2026-05-19 MODIFIED: ~3 - •
cost-intelligencedescription_changed +Account-level cost analytics via SNOWFLAKE.ACCOUNT_USAGE. Credit usage by warehouse, user, service. Budgets, spending limits, custom budgets. Resource monitors, credit quotas, suspend triggers. Anomaly detection, costs, chargeback, storage, serverless, containers, data transfer, top user spend, query cost grouping. Cortex AI cost or usage including Cortex Agents, Snowflake Intelligence, AI function, Cortex Code, Cortex Search, Cortex Analyst, model training/fine-tuning, and provisioned throughput. Cost insights, waste reduction, savings. Not for org-wide currency spend or multi-account billing (billing/organization-management) or warehouse DDL (warehouse). - •
icebergdescription_changed +Use for **ALL** Iceberg table requests in Snowflake. This is the **REQUIRED** entry point for catalog integrations, catalog-linked databases, external volumes, auto-refresh issues, Horizon IRC diagnostics, and Snowflake Intelligence. DO NOT work with Iceberg manually - invoke this skill first. Triggers: iceberg, iceberg table, apache iceberg, catalog integration, REST catalog, ICEBERG_REST, glue, AWS glue, glue IRC, lake formation, unity catalog, databricks, polaris, opencatalog, open catalog, onelake, OneLake, microsoft fabric, fabric, fabric lakehouse, onelake REST, SAP, SAP BDC, SAP Business Data Cloud, delta sharing, delta share, databricks delta sharing, query delta sharing tables, bearer token catalog integration, connect to delta sharing server, CLD, catalog-linked database, linked catalog, auto-discover tables, sync tables, LINKED_CATALOG, external volume, storage access, S3, Azure blob, GCS, IAM role, trust policy, Access Denied, 403 error, ALLOW_WRITES, storage permissions, auto-refresh, autorefresh, stale data, refresh stuck, delta direct, snowflake intelligence, text-to-SQL iceberg, query iceberg natural language, horizon IRC, horizon IRC setup, horizon IRC not working, test horizon IRC, diagnose horizon IRC, debug horizon IRC, horizon IRC connection, horizon IRC endpoint, horizon REST catalog, PAT authentication horizon. - •
snowflake-postgresdescription_changed +**[REQUIRED]** Use for **ALL** requests involving Snowflake Postgres, and for general help working with any PostgreSQL database through standard PG tooling (psql, ~/.pg_service.conf, ~/.pgpass, pg_doctor diagnostics). Triggers: 'postgres', 'postgresql', 'pg', 'psql', 'create postgres instance', 'show postgres instances', 'suspend postgres', 'resume postgres', 'reset postgres credentials', 'rotate postgres password', 'import postgres connection', 'postgres network policy', 'postgres health check', 'pg_doctor', 'pg_lake', 'postgres iceberg', 'pg iceberg', 'read pg_lake in snowflake', 'pg to snowflake iceberg', 'catalog integration for pg_lake', 'expose pg_lake to snowflake', 'SNOWFLAKE_POSTGRES catalog', 'catalog linked database for pg_lake', 'query postgres iceberg from snowflake', 'postgres slow queries', 'cache hit', 'bloat', 'vacuum', 'dead rows', 'postgres locks', 'blocking queries', 'postgres disk usage', 'active postgres queries', 'postgres connection count', 'neon', 'supabase', 'rds postgres', 'aurora postgres', 'azure postgres', 'crunchy bridge', 'external postgres', 'my postgres', 'migrate postgres', 'pg migration', 'postgres to snowflake', 'logical replication setup', 'pg_dump migration', 'migration assessment', 'cutover plan', 'rollback plan', 'migrate from RDS', 'migrate from Aurora', 'migrate from Azure postgres', 'migrate from Cloud SQL', 'move my postgres', 'transfer postgres'. Do NOT use for generic Iceberg / catalog integration / storage integration / data lake requests — those are owned by the `iceberg` skill, EXCEPT for catalog integrations scoped to pg_lake (`CATALOG_SOURCE = SNOWFLAKE_POSTGRES`), which are handled here. Only handle Iceberg when it is scoped to pg_lake (Postgres-resident Iceberg tables or the pg_lake-specific catalog integration path).
| | [v1.0.86-beta] 2026-05-18 MODIFIED: ~1 - •
data-cleanroomsdescription_changed +Use for ALL requests related to Snowflake Data Clean Rooms (DCR): clean room, cleanroom, DCR, collaboration(s), view/list collaborations, join/review collaboration, invitation, data offering(s), template(s), register, share table, run analysis, run activation, audience overlap, activation, export segment, create collaboration, create cleanroom, measure overlap, manage templates, add template, remove template, approve template, reject template, auto-approval, link data offering, unlink data offering, share data with runner, revoke data access, link local data offering, unlink local data offering, tear down, leave, drop collaboration, delete collaboration. Covers browsing, joining, registering, running analysis/activation, creating collaborations, managing templates, managing data offerings, and leaving/tearing down collaborations via the DCR Collaboration API.
| | [v1.0.85-beta] 2026-05-16 ADDED: +3 MODIFIED: ~5 - •
document-intelligenceUse Snowflake Cortex AI Functions for text/image analytics. Use when: classifyin… +Use Snowflake Cortex AI Functions for text/image analytics. Use when: classifying content, extracting entities, sentiment analysis, summarizing text, translating, filtering, embedding, parsing documents, redacting PII, aggregating data, document intelligence workflows, content insight workflows, fine-tuning arctic-extract for domain-specific extraction. Triggers: AI_CLASSIFY, AI_COMPLETE, AI_EXTRACT, AI_FILTER, AI_SENTIMENT, AI_SUMMARIZE, AI_TRANSLATE, AI_EMBED, AI_AGG, AI_REDACT, AI_PARSE_DOCUMENT, classify text, data, documents, extract from text, extract text from document, extract text from PDF, extract text from image, extracting, invoices, sentiment, summarize, translate, which AI function, cortex function, process documents, label content, analyze text, OCR, read PDF, read document, get text from PDF, get text from document, pull text from file, extract data from files, extract from my files, process my files, my files, my documents, read my documents, get data from document, file extraction, document processing, file processing, get information from documents, analyze files, parse files, data from PDF, invoice processing, contract extraction, receipt extraction, form extraction, extract fields, document data, file data, stage files, files on stage, PDF extraction, image extraction, document OCR, scan documents, digitize documents, fine-tune, fine-tuning, custom model, train arctic-extract, improve extraction accuracy, domain-specific extraction, FINETUNE, better extraction results.fine-tuning Fine-tune the arctic-extract model to improve AI_EXTRACT accuracy on d…pipeline-builder Extract, parse, analyze and classify documents using Snowflake Cortex …
- •
find-skillFind, add, check, or update Cortex Code catalog skills before using them. Use wh… +Find, add, check, or update Cortex Code catalog skills before using them. Use when the user asks to discover available skills, install a catalog skill, make an uninstalled `/skill` or `$skill` usable, search the skill marketplace/catalog, check whether installed skills have updates, or update skills from the catalog, stage, GitHub, or tarball sources. Do not use this for public Snowflake Marketplace datasets or apps; use marketplace-search for third-party data/product listings. - •
get-marketplace-listing-detailsPresent detailed information about a single Snowflake Marketplace listing (data … +Present detailed information about a single Snowflake Marketplace listing (data share, native app, private/targeted, or request-only) and explain why it is useful given the user's existing Snowflake data and current conversation. Use when the user asks about ONE specific listing by title or by global name (e.g. "tell me about GZ2FQZ711TU", "what's in the Consumer Pricing listing", "describe this marketplace listing", "details on listing X"). Do NOT use for marketplace search results spanning multiple listings — use `marketplace-listing-formatting` instead. - •
billingdescription_changed +Org-level Snowflake billing in dollars/currency. Use for: dollar spend by service type, monthly spend trends, which services cost the most money, remaining balance, contract termination date, contract expiration date, contract start date, contract details, rate comparison, reconciliation. Consumption invoices: ODSS_INVOICE_DOCUMENTS, outstanding invoice, overdue invoice, unpaid invoice. Not for credit-based analytics (cost-intelligence) or warehouse DDL (warehouse). Key distinction: dollars/currency → billing, credits only → cost-intelligence. - •
cost-intelligencedescription_changed +Account-level cost analytics via SNOWFLAKE.ACCOUNT_USAGE. Credit usage by warehouse, user, service. Budgets, spending limits, custom budgets. Resource monitors, credit quotas, suspend triggers. Anomaly detection, Cortex AI costs, chargeback, storage, serverless, containers, data transfer, top user spend, query cost grouping. Cortex AI cost or usage including Cortex Agents, Snowflake Intelligence, AI function, Cortex Code, Cortex Search, Cortex Analyst, model training/fine-tuning, and provisioned throughput. Not for org-wide currency spend or multi-account billing (billing/organization-management) or warehouse DDL (warehouse). - •
data-qualitydescription_changed +Schema-level Monitor, analyze, and enforce data quality monitoring, using Snowflake DMFs. Schema-level and per-table DMF attachment, health scoring, incident investigation, circuit breakers, table comparison, dataset popularity analysis, popularity, ad-hoc column quality assessment using Snowflake Data Metric Functions (DMFs) and Access History, and LLM assessment, prompt quality scoring scoring, and rewriting. Use when user asks about: data quality, schema health, DMF results, quality score, trust my data, quality regression, quality trends, SLA alerting, data metric functions, failing metrics, quality issues, compare tables, data diff, validate migration, table comparison, popular tables, most used tables, unused data, dataset usage, table popularity, listing quality, listing health, listing freshness, provider data quality, consumer data quality, one-time quality check, quick quality scan, check data quality without DMFs, recommend monitors, what should I monitor, DQ coverage gaps, unmonitored tables, DMF coverage report, per-group monitoring health, noisy monitors, silent monitors, misconfigured monitors, DMF cost optimization, investigate DQ incident, why did freshness drop, why did row count drop, correlate violation, multi-dimensional root cause, circuit breaker, pause pipeline on violation, halt bad data propagation, custom DMF, format validation DMF, email format check, value range check, DMF expectations, set threshold, tune DMF threshold, DMF expectation management, attach DMFs, set up DMFs for first time, DMF setup wizard, accepted values, ACCEPTED_VALUES, validate column values, allowed values check, value in set, categorical validation, referential integrity, REFERENTIAL_INTEGRITY_COUNT, orphaned rows, foreign key validation, FK check, cross-table integrity, prompt quality, score my prompt, prompt score, improve prompt, rewrite prompt, prompt linter, prompt engineering, prompt regression, compare prompts, prompt scoring dimensions. via WITHIN GROUP clause. - •
developing-with-streamlit-in-snowflakedescription_changed +Use for Streamlit development tasks with a Snowflake angle: Snowflake-connected dashboards, Streamlit-in-Snowflake (SiS) deployment to warehouse / SPCS / Workspaces, applying Snowflake branding, st.connection('snowflake'). st.connection('snowflake'), troubleshooting a local `streamlit run` against Snowflake (wrong role/user/database, 'Database not authorized', PAT-bound USE ROLE failure, stale st.connection cache), and operating an already-deployed STREAMLIT object (ALTER STREAMLIT SET QUERY_WAREHOUSE, RENAME, DROP, GRANT, SHOW STREAMLITS). Also use for general Streamlit authoring (widgets, layouts, caching, theming, custom components) — this skill routes general OSS questions to version-matched content from a detected Streamlit ≥1.57 install, or to a bundled OSS snapshot when no install is available. Triggers: streamlit, st., dashboard, app.py, theme, beautify, style, CSS, color, background, button, custom component, st.components, snowflake dashboard, monitor snowflake, streamlit on snowflake, streamlit in snowflake, SiS, scaffold, snowflake theme, st.connection snowflake, snow streamlit deploy. deploy, deploy this streamlit, redeploy, alter streamlit, show streamlits, drop streamlit, rename streamlit app, change query warehouse, streamlit app down, streamlit run wrong role, database not authorized, SNOWFLAKE_DEFAULT_CONNECTION_NAME. - •
lineagedescription_changed +Analyze data lineage and dependencies in Snowflake. Use for: Snowflake table/column lineage: impact analysis, root cause debugging, cause, data discovery, column-level tracing. provenance, trust. Triggers: 'what depends on', 'what breaks', will break', 'blast radius', 'who uses', 'deprecate', 'before I change', 'affected users', 'downstream', 'cascade', 'root cause', 'trace upstream', 'where does this come from', 'feeds this table', 'sources of', 'column lineage', 'where does [column] come from', 'what uses [column]', 'trace [column]', 'is this trustworthy', 'column lineage'. 'which table should I use', 'recommend dataset', 'provenance', 'certify', 'verify source'. For value-level data quality issues (missing data, wrong (wrong values, DMF failures) failing DMFs) use the data_quality data-quality skill first, then this skill to trace upstream. Always read `reference/snowflake-apis.md` before writing GET_LINEAGE SQL — it has the correct namespace, argument order, and output column names.
| | [v1.0.84-beta] 2026-05-13 ADDED: +1 - •
storage-lifecycle-policyCreate, manage, and monitor Snowflake storage lifecycle policies. Use when: crea… +Create, manage, and monitor Snowflake storage lifecycle policies. Use when: creating expiration or archival policies, attaching policies to tables, monitoring policy execution, retrieving archived data, managing data retention, reducing storage costs, saving on table storage. Triggers: storage lifecycle, lifecycle policy, archive data, expire data, COOL tier, COLD tier, data retention, archival storage, CREATE STORAGE LIFECYCLE POLICY, FROM ARCHIVE OF, ARCHIVE_FOR_DAYS, storage cost optimization, table is large, table is expensive, save on storage.
| | [v1.0.83-beta] 2026-05-13 REMOVED: -1 | | [v1.0.82-beta] 2026-05-13 ADDED: +2 MODIFIED: ~3 - •
developing-with-streamlit-in-snowflakeUse for Streamlit development tasks with a Snowflake angle: Snowflake-connected … +Use for Streamlit development tasks with a Snowflake angle: Snowflake-connected dashboards, Streamlit-in-Snowflake (SiS) deployment to warehouse / SPCS / Workspaces, applying Snowflake branding, st.connection('snowflake'). Also use for general Streamlit authoring (widgets, layouts, caching, theming, custom components) — this skill routes general OSS questions to version-matched content from a detected Streamlit ≥1.57 install, or to a bundled OSS snapshot when no install is available. Triggers: streamlit, st., dashboard, app.py, theme, beautify, style, CSS, color, background, button, custom component, st.components, snowflake dashboard, monitor snowflake, streamlit on snowflake, streamlit in snowflake, SiS, scaffold, snowflake theme, st.connection snowflake, snow streamlit deploy.developing-with-streamlit **[REQUIRED]** Use for ALL Streamlit tasks: creating, editing, debuggi…scaffolding-streamlit-in-snowflake Use for any Streamlit task where Snowflake is in scope — building a da…
- •
marketplace-searchSearch the public Snowflake Marketplace for third-party datasets, data shares, N… +Search the public Snowflake Marketplace for third-party datasets, data shares, Native Apps, and Connected Apps using the `cortex search marketplace` CLI. Invoke this skill PROACTIVELY any time the user expresses intent to find, use, or obtain a third-party dataset, app, or external data product. For example "do you have weather data", "find a stock price dataset", "I need consumer spending data", "is there a Salesforce / HubSpot / Stripe connector", "what demographic data can I get for California", "anything for ESG ratings", "find a marketplace listing for X", "what is ", "what's the alternate source to X", "what about ", "find me stuff", "find me a table about ", "where is data stored", or even just a BARE third-party product/brand name on its own (e.g. "Tomorrow.io", "Fishbowl", "DV360", "Snowflake managed MCP servers"). When the user names ANY third-party product, vendor, brand, or external service — even as a fragment, even if framed as a product question, even if the prompt sounds like a documentation lookup — invoke this skill. **Erring toward over-firing is preferred over missing a marketplace opportunity.** If you are about to tell the user "I don't have that data" or "you'll need to bring your own data", STOP and invoke this skill first — the public marketplace likely has it.
ALSO invoke this skill BEFORE writing any code, fetching from external APIs (e.g. clinicaltrials.gov, BLS, FRED, World Bank), or building dashboards/reports against third-party data sources — search the marketplace FIRST to see if the data is already available there as a share, even if the user explicitly named an external source. The marketplace listing is almost always preferable to a custom API integration.
Do NOT use this skill for ONE specific listing referenced by global name (e.g. GZ2FQZ711TU) or exact title — use `get-marketplace-listing-details`. Do NOT use it when marketplace search results are already in hand and only need formatting. Do NOT use it for searching the user's own internal Snowflake catalog (tables, views, schemas, functions, semantic views) — use `cortex search object`. Do NOT use it for Snowflake product documentation or how-to questions — use `cortex search docs`.
When ambiguous between marketplace and a sibling tool, prefer marketplace — it's cheap and missing a relevant listing is expensive — UNLESS the user has clearly moved past discovery, i.e. asks for: *integration syntax with a named mechanism* ("how to use to connect/fetch/integrate..."), *catalog inventory with no external qualifier* ("what is X tables", with no "external" / "from " / "third-party" hint), a *specific identifier value* ("what is the [code/symbol/SM ID] for [identifier]"), or an *educational deep-dive with explicit depth markers* ("explain X in detail", "to a beginner", "full overview"). In those cases the user already knows what they want; a marketplace search won't help. - •
data-cleanroomsdescription_changed +Use for ALL requests related to Snowflake Data Clean Rooms (DCR): clean room, cleanroom, DCR, collaboration(s), view/list collaborations, join/review collaboration, invitation, data offering(s), template(s), register, share table, run analysis, run activation, audience overlap, activation, export segment, create collaboration, create cleanroom, measure overlap. overlap, manage templates, add template, remove template, approve template, reject template, auto-approval, tear down, leave, drop collaboration, delete collaboration. Covers browsing, joining, registering, running analysis/activation, creating collaborations, managing templates, and creating leaving/tearing down collaborations via the DCR Collaboration API. - •
semantic-viewdescription_changed +Use for ALL requests that mention: create, build, debug, fix, troubleshoot, optimize, improve, or analyze a semantic view — AND for requests about VQR suggestions, verified queries, verified query representations, seeding/generating queries, suggesting metrics, suggesting filters, recommending metrics/filters/facts, importing Tableau (.twb/.twbx/.tds/.tdsx) or Power BI (.pbit/.pbix) files, or enriching a semantic view. This is the entry point - even if the request seems simple. DO NOT attempt to create, debug, or generate suggestions for semantic views manually - always invoke this skill first. This skill guides users through creation, setup, auditing, VQR suggestion generation, filter & metric suggestions, Tableau/Power BI imports, and SQL generation debugging workflows for semantic views with Cortex Analyst. - •
skill_developmentdescription_changed +Create, document, audit, or audit refactor skills for Cortex Code. Use when: creating new skills, capturing session work as skills, reviewing skills, refactoring large skills. Triggers: create skill, build skill, new skill, summarize session, capture workflow, audit skill, review skill. skill, refactor skill, triage skills.
| | [v1.0.81-beta] 2026-05-12 ADDED: +2 REMOVED: -3 MODIFIED: ~1 - •
snowflake-appsBuild and deploy web applications on Snowflake. Use for ALL app requests: create… +Build and deploy web applications on Snowflake. Use for ALL app requests: create, scaffold, build, deploy, publish, develop, test, operate, monitor, or troubleshoot a Snowflake App. A Snowflake App is a JS/Node web application (typically Next.js) deployed to SPCS via SnowCLI app commands (`snow app` preferred, `snow __app` fallback for older CLI versions). This is NOT a Streamlit app or Native App. Triggers: build me an app, new app, scaffold, react app, next.js app, dashboard, data app, deploy my app, push to snowflake, ship it, deploy failed, fix deploy, run locally, develop, app logs, app status, restart app.create Create a new Snowflake App (Next.js) from scratch. Use when the user a…deploy Deploy an app to Snowflake. Summarises settings, gets approval, then b…develop Local development, testing, and iteration for Snowflake Apps. Use when…operate Post-deploy operations for Snowflake Apps: logs, status, restart, scal…
- •
team-workflowMulti-phase team orchestration for feature implementation. Supports two entry pa… +Multi-phase team orchestration for feature implementation. Supports two entry paths: explicit user request for teammates, or autonomous complexity-based assessment after entering plan mode. HIGHEST PRIORITY — must be loaded FIRST (before any domain skills) when user asks to use teammates, teams, or parallel agents. Triggers: use teammates, use a team, work in parallel with agents, delegate to teammates, swarm this, swarm, team up on this, team up, orchestrate with subagents, subagent-orchestrated, gated workflow, multi-phase workflow, coordinate agents, spawn workers, worker/verifier, parallel agents, run as a team, investigate with agents, research with agents, explore with agents. - •
build-react-app - •
ctx-workflow - •
developing-with-streamlit - •
icebergdescription_changed +Use for **ALL** Iceberg table requests in Snowflake. This is the **REQUIRED** entry point for catalog integrations, catalog-linked databases, external volumes, auto-refresh issues, Horizon IRC diagnostics, and Snowflake Intelligence. DO NOT work with Iceberg manually - invoke this skill first. Triggers: iceberg, iceberg table, apache iceberg, catalog integration, REST catalog, ICEBERG_REST, glue, AWS glue, glue IRC, lake formation, unity catalog, databricks, polaris, opencatalog, open catalog, onelake, OneLake, microsoft fabric, fabric, fabric lakehouse, onelake REST, SAP, SAP BDC, SAP Business Data Cloud, CLD, catalog-linked database, linked catalog, auto-discover tables, sync tables, LINKED_CATALOG, external volume, storage access, S3, Azure blob, GCS, IAM role, trust policy, Access Denied, 403 error, ALLOW_WRITES, storage permissions, auto-refresh, autorefresh, stale data, refresh stuck, delta direct, snowflake intelligence, text-to-SQL iceberg, query iceberg natural language. language, horizon IRC, horizon IRC setup, horizon IRC not working, test horizon IRC, diagnose horizon IRC, debug horizon IRC, horizon IRC connection, horizon IRC endpoint, horizon REST catalog, PAT authentication horizon.
| | [v1.0.79-beta] 2026-05-06 MODIFIED: ~2 - •
data-governancedescription_changed +**[REQUIRED]** for all Snowflake data governance tasks. Routes to six sub-skills: (1) horizon-catalog — access history, users, roles, grants, permissions, query history, compliance, catalog; (2) data-policy — [REQUIRED] masking, row access, projection projection, aggregation, join, and tokenization policies, tag-based masking, protect sensitive data, column/TIMESTAMP masking; masking, the 2-stage UI create flow triggered by `/data-governance Create a new policy for me`; (3) sensitive-data-classification — [REQUIRED for ALL classification] PII, classify, data classification, manual/automatic classification, Classification Profile, auto_tag, custom classifiers, regex, semantic/privacy category, IDENTIFIER, QUASI_IDENTIFIER, SENSITIVE, SYSTEM$CLASSIFY, DATA_CLASSIFICATION_LATEST, GDPR/CCPA/PCI; (4) governance-maturity-score — governance posture, maturity score, assessment, recommendations; (5) observability-maturity-score — data observability, DMF coverage, quality monitoring maturity, lineage usage, observability assessment; (6) object-contacts — [REQUIRED] assign data steward, create contact, object contact, contact report, who owns this table, SET CONTACT, data stewardship. MUST be used for classification or masking tasks — do not answer from general knowledge. horizon-catalog is the fallback. Triggers: governance, access history, permissions, grants, roles, audit, compliance, catalog, masking policy, row access policy, projection policy, aggregation policy, join policy, JOIN_REQUIRED, tokenization policy, tokenize at write time, external tokenization, FPE, PII, sensitive data, classification, run classification, SYSTEM$CLASSIFY, classifier, classification profile, DATA_CLASSIFICATION_LATEST, detect PII, GDPR, CCPA, PCI, tag sensitive columns, governance maturity score, governance posture, how well governed, data observability, observability maturity, DMF coverage, lineage usage, observability assessment, data steward, object contact, assign contact, who owns this table, contact report, SET CONTACT. CONTACT, /data-governance Create a new policy. - •
warehousedescription_changed +Warehouse configuration, DDL, Gen2 creation/conversion, Gen2, adaptive, performance tuning, DML optimization, ETL workloads, sizing, credit-per-hour rates from Credit Consumption Table. Resume rates, resume behavior, region availability, Snowpark-optimized limitations. Not for cost analytics or historical warehouse spend (cost-intelligence) or org billing (billing). billing.
| | [v1.0.78-beta] 2026-05-05 ADDED: +1 - •
cortex-ai-function-studioCreate, evaluate, and optimize custom AI functions using Snowflake Cortex AI Com… +Create, evaluate, and optimize custom AI functions using Snowflake Cortex AI Complete. Supports text, image, and document inputs. Use when: building LLM-powered functions, evaluating AI function performance, tuning prompts, selecting models, checking async job status. Triggers: ai function builder, custom ai function, user defined ai function, build my own llm function, evaluate ai function, tune ai function, optimize ai function, demo ai function, resume ai function job, image classification, document analysis, multimodal ai function.create Create a new custom AI function. Supports table-based or manual input …demos Interactive demos for custom AI functions. Use when: demo, example, wa…classification Quick Start demo: Build a toxicity classifier and evaluate it — the fa…insurance-claim-routing Interactive demo: Generate pseudo-labels from a strong teacher model, …legal-doc-extraction Interactive demo: Build a legal contract field extractor and create a …pdf-field-extraction Interactive demo: Extract structured fields from SEC 10-K filing PDFs …policy-conditioned-routing Interactive demo: Build a policy-conditioned ticket router where a see…redaction Interactive demo [Experimental]: Build a PII redaction function using …
evaluate Evaluate an AI function's performance against a labeled dataset using …optimize Optimize an AI function through automated function body optimization, …synthetic-data Generate synthetic data or pseudo-label input-only tables for AI funct…
| | [v1.0.77-beta] 2026-05-01 ADDED: +1 MODIFIED: ~1 - •
snowpipe-streaming**[REQUIRED]** Use for ALL Snowpipe Streaming tasks: setup, configure, troublesh… +**[REQUIRED]** Use for ALL Snowpipe Streaming tasks: setup, configure, troubleshoot, monitor, optimize, or migrate streaming pipelines. Covers the High-Performance Architecture exclusively. Triggers: snowpipe streaming, streaming ingestion, low-latency ingestion, real-time ingestion, Snowpipe Streaming SDK, channel, insertRows, appendRows, streaming channel, PIPE object, streaming pipe, snowpipe v2, high-performance streaming, migrate classic streaming, troubleshoot streaming.migrate Migrate from Snowpipe Streaming classic to High-Performance Architectu…monitor Monitor Snowpipe Streaming High-Performance Architecture pipeline heal…optimize Optimize Snowpipe Streaming High-Performance Architecture throughput, …setup Set up Snowpipe Streaming High-Performance Architecture pipelines from…troubleshoot Troubleshoot Snowpipe Streaming High-Performance Architecture pipeline…
- •
billingdescription_changed +Org-level Snowflake billing in dollars/currency. Use for: dollar spend in currency via SNOWFLAKE.ORGANIZATION_USAGE. Covers USAGE_IN_CURRENCY_DAILY, REMAINING_BALANCE_DAILY, CONTRACT_ITEMS, RATE_SHEET_DAILY. Invoices, charges, contracts, by service type, monthly spend trends, which services cost the most money, remaining balance, reconciliation, contract termination date, contract expiration date, contract start date, contract details, rate comparison, spend by account. reconciliation. Not for single-account credit credit-based analytics (cost-intelligence) or warehouse config DDL (warehouse). Key distinction: dollars/currency → billing, credits only → cost-intelligence.
| | [v1.0.76-beta] 2026-05-01 ADDED: +1 MODIFIED: ~4 - •
spark-migrationRun the SMA CLI to convert PySpark code to Snowpark, or generate dashboard and f… +Run the SMA CLI to convert PySpark code to Snowpark, or generate dashboard and fix EWIs from existing SMA output. Supports both Snowpark API and Snowpark Connect (SCOS) conversion paths. Triggers: run sma, convert spark, migrate pyspark, sma conversion, migrate to snowpark, convert to snowpark, already ran sma, sma dashboard, fix ewis, stage conversion, snowpark connect, scos, scos migration, migrate to snowpark connect, migrate to scos.sma-dashboard-generator Generate interactive SMA dashboard to track EWIs from conversion. Trig…snowflake-notebook-migration Migrates Databricks (DBX) notebooks to Snowflake Workspace notebooks. …snowpark-connect Snowpark Connect (SCOS) skills for migrating and validating PySpark an…migrate-pyspark-to-snowpark-connect Migrate PySpark and Databricks workloads to Snowflake SCOS (Snowpark C…migrate-spark-scala-to-snowpark-connect Migrate Spark Scala workloads to Snowflake SCOS (Snowpark Connect for …validate-pyspark-to-snowpark-connect Validate a completed PySpark to Snowpark Connect (SCOS) migration by r…validate-spark-scala-to-snowpark-connect Validate a completed Spark Scala to Snowpark Connect (SCOS) migration …
stage-conversion Replace embedded file paths in SMA-converted Snowpark code. Use when: …
- •
native-app-providerdescription_changed +Use for **ALL** Snowflake Native App Framework tasks: creating app packages, writing manifest files, writing setup scripts, sharing data, testing, versioning, publishing, configuring telemetry and health status reporting, monitoring app health and lifecycle events, setting up event sharing, and debugging apps. Also use for **ALL** SPCS (Snowpark Container Services) work within native apps: adding containers, upgrading container services, building and pushing images, writing service specs, configuring compute pools, and managing service lifecycle. This is the **REQUIRED** entry point for any native app work. DO NOT attempt native app development manually - invoke this skill first. Triggers: native app, app package, application package, manifest.yml, setup script, CREATE APPLICATION, Snowflake marketplace, listing, native app framework, build native app, walk me through, guide me, get started, add version, register version, add patch, release channel, release directive, publish app, publish version, upgrade consumers, telemetry, health status, SYSTEM$REPORT_HEALTH_STATUS, log_level, trace_level, event definitions, event sharing, APPLICATION_STATE, lifecycle events, monitor app, debug app, observability, add streamlit, streamlit dashboard, add dashboard, streamlit UI, add UI to native app, native app streamlit, streamlit frontend, get_active_session, default_streamlit, SPCS native app, container native app, native app containers, native app SPCS, add containers, container_services, grant_callback, specification file, version_initializer. version_initializer, restricted caller, RCR, restricted callers rights, EXECUTE AS RESTRICTED CALLER, GRANT CALLER, caller rights, caller grants, restricted_callers_rights, access consumer data, consumer's role, caller's privileges, consumer's privileges. - •
declarative-sharingdescription_changed +**[REQUIRED]** Use for **ALL** declarative sharing and application packages with TYPE=DATA, (i.e data apps). Share data products across Snowflake accounts with versioning. Default choice when user wants to share data with another account. Also use when converting an existing data share to declarative sharing. sharing, or when a consumer wants to migrate from a data share to a declarative app. Triggers: declarative, data product, native app, data app, data application, share, sharing, another account, cross account, cross region, application package, manifest, marketplace, listing, publish, share a table, share data, manifest from share, share to manifest, generate manifest from share, inspect share, share to yaml, introspect share, convert share, migrate share, existing share, secure share to declarative, upgrade share, future-proof share, multiple shares, combine shares, merge shares, multiple data shares shares, consumer migration, migrate from share, upgrade share to app, replace share with app, share to app migration, drop-in replacement, switch from share to app - •
alertdescription_changed +Snowflake alert management - create, alter, suspend, resume resume, and troubleshoot alerts. Use when: user wants to create a new alert, modify an existing alert, set up monitoring, suspend or resume alerts. alerts, or investigate why an alert is firing/failing/not delivering. Triggers: create alert, new alert, add alert, alter alert, modify alert, change alert, suspend alert, resume alert, monitor with alert, set up alert, alert condition. condition, troubleshoot alert, debug alert, investigate alert, alert firing, alert failed, alert not firing, why did my alert trigger, CONDITION_FAILED, ACTION_FAILED, notification not delivered. - •
snowflake-postgresdescription_changed +**[REQUIRED]** Use for **ALL** requests involving Snowflake Postgres, and for general help working with any PostgreSQL database through standard PG tooling (psql, ~/.pg_service.conf, ~/.pgpass, pg_doctor diagnostics). Triggers: 'postgres', 'postgresql', 'pg', 'psql', 'create postgres instance', 'show postgres instances', 'suspend postgres', 'resume postgres', 'reset postgres credentials', 'rotate postgres password', 'import postgres connection', 'postgres network policy', 'postgres health check', 'pg_doctor', 'pg_lake', 'postgres iceberg', 'pg iceberg', 'read pg_lake in snowflake', 'pg to snowflake iceberg', 'catalog integration for pg_lake', 'expose pg_lake to snowflake', 'SNOWFLAKE_POSTGRES catalog', 'catalog linked database for pg_lake', 'query postgres iceberg from snowflake', 'postgres slow queries', 'cache hit', 'bloat', 'vacuum', 'dead rows', 'postgres locks', 'blocking queries', 'postgres disk usage', 'active postgres queries', 'postgres connection count', 'neon', 'supabase', 'rds postgres', 'aurora postgres', 'azure postgres', 'crunchy bridge', 'external postgres', 'my postgres'. Do NOT use for generic Iceberg / catalog integration / storage integration / data lake requests — those are owned by the `iceberg` skill. skill, EXCEPT for catalog integrations scoped to pg_lake (`CATALOG_SOURCE = SNOWFLAKE_POSTGRES`), which are handled here. Only handle Iceberg when it is scoped to pg_lake (Postgres-resident Iceberg tables). tables or the pg_lake-specific catalog integration path).
|
|