Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Tool guide
Snowflake
Defines source-aware cloud data platform analysis and administration, evidence handling, and action boundaries.
Read the fileOverview
Snowflake overview
Use this bundle to structure cloud data platform analysis and administration while keeping official-source context separate from account, organization, project, document, or environment.
Read the fileWorkflow
Snowflake source-aware triage
1. State the requested decision or deliverable. 2. Inventory evidence: account, region, edition, and version context, database, schema, object, and ownership metadata, warehouse and.
Read the fileTemplate
Snowflake analysis and change brief
Review-ready brief for cloud data platform analysis and administration, evidence quality, verification, and controlled next actions.
Read the fileIs this bundle right for your task?
Who it is for
- People who configure, operate, integrate, govern, or review work performed in Snowflake
- Teams working in Data and analytics, Software, Financial services
When to use it
- A proposed Snowflake configuration or workflow change needs current IDs, permissions, dependencies, tests, and rollback evidence.
- A report, export, integration, or automation result needs to be reconciled against actual workspace state and current product documentation.
What you need to provide
- The product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner.
- Current IDs, settings, records, logs, screenshots, integration details, and test evidence needed to verify the requested change.
Tasks and expected outputs
Questions it helps answer
- Prepare a snowflake analysis and change brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce review-ready decisions with explicit verification and approval boundaries.
What it helps produce
- Snowflake analysis and change brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner. Ask the agent to review Snowflake and produce Snowflake analysis and change brief that maps configuration evidence, dependencies, permissions, tests, rollback, and actions that still require approval. Begin with docs.snowflake.com, then confirm that the reference is current and applicable. Inspect Snowflake before drafting.
Context path: bundles/tools/snowflake
What the bundle includes
Tools
- Snowflake
Frameworks
- source-evidence matrix
- cloud-data-platform-analysis-and-administration evidence matrix
- qualified-review gate
Evaluations
- Snowflake source-awareness check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Changing live configuration, records, permissions, automations, integrations, or shared data without verified scope, testing, rollback, and approval.
Known limitations
- Use official Snowflake sources for general context; local cloud data platform analysis and administration, configuration, records, values, states, and permissions require inspected evidence.
- Task-specific work requires current evidence for account, region, edition, and version context, database, schema, object, and ownership metadata, warehouse and resource-monitor configuration, roles, grants, policies, and data classification, SQL text, parameters, query profile, and history, freshness, lineage, quality, and source-of-record checks, and cost, change, and approval evidence.
- Do not infer objects, columns, data, roles, grants, warehouse state, query results, cost.
Safety notes
- Minimize personal, customer, employee, financial, credential, and other sensitive data.
- Require explicit confirmation before running state-changing SQL, changing objects, warehouses, roles, grants, policies, integrations, shares, or production data.
- Route legal, privacy, security, compliance, financial, employment, and other qualified judgments to accountable reviewers.