A code-conversion workflow that changes SQL from supported source systems into Snowflake SQL, the SQL dialect used by Snowflake's cloud data platform. It can also repoint Power BI reports and Tableau workbooks to the new environment.

Use it to convert source SQL files, save the Snowflake-compatible output, and generate review reports for unsupported or uncertain parts of the conversion.

It reduces the manual work of rewriting database code during a move to Snowflake. Reports identify conversion items that still need human review.

convert — Skill for Claude Code by sfc-gh-dflippo

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add sfc-gh-dflippo/snowflake-dbt-demo --skill convert

Clone the repo

git clone --depth 1 https://github.com/sfc-gh-dflippo/snowflake-dbt-demo

Made for: Claude Code.

Or install snowflake-migration, the plugin that ships this one along with the rest of its 72 skills, 7 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/convert/github.svg)](https://agentmods.dev/skills/sfc-gh-dflippo/snowflake-dbt-demo/convert)

Your own site

<a href="https://agentmods.dev/skills/sfc-gh-dflippo/snowflake-dbt-demo/convert"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/convert/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sfc-gh-dflippo/snowflake-dbt-demo/convert"><img src="https://agentmods.dev/badge/skills/sfc-gh-dflippo/snowflake-dbt-demo/convert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,257 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00064	$0.03257
Opus 5	$0.00032	$0.01629
Sonnet 5	$0.00013	$0.00651
Haiku 4.5	$0.00006	$0.00326

Measured 2d ago against content hash 22b15d0c4d82, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

convert scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/snowflake-migration/skills/migration/convert/SKILL.md · 243 lines

How it starts

The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Conversion

On Entry

Tell the user:

Code Conversion.

Here's what I'll do:

Run SnowConvert against your source SQL files, transforming each into Snowflake SQL syntax (optionally tailoring conversion settings to your source first, or going with defaults).

Generate reports flagging anything that needs manual review (EWIs, FDMs, performance remarks, out-of-scope items).

Save converted code under snowflake/ and reports under reports/SnowConvert/.

Convert source code to Snowflake SQL using SnowConvert.

Report the result from the --json envelope and hand off. Reading the generated reports, counting EWIs by severity or judging what needs fixing is the assessment's job — do that here only if the user asks a direct question.

Prerequisites

Migration project initialized (scai init)
Source SQL in source/ or Tableau repointing with TABLEAU_PATH set (Tableau-only is allowed with an empty source/; Step 3.5 applies the dialect gate)

Workflow

Step 1: Verify Source Code Exists

Confirm source/ contains .sql files (use whichever portable form fits the host). Note whether SQL is present; do not stop yet.

If source/ is empty, continue to Steps 2–3.5. After those steps, if there is still no SQL and TABLEAU_PATH is unset and PBIT_PATH is unset, return to the parent setup skill so it can re-query progress_setup(). Tableau-only conversions (Step 3.5 sets TABLEAU_PATH) are allowed with an empty source/.

Step 2: Check for ETL Code

Any ETL in this project was imported during register (scai code add), which arranges the packages into source/_etl/. That is where convert reads them from.

Check whether source/_etl/ exists and contains ETL files — .dtsx for SSIS, .xml for Informatica PowerCenter (use whichever portable form fits the host).

If it is missing or empty, there is no ETL to convert; proceed to Step 3.
If it contains SSIS packages only, no conversion-target prompt is needed; proceed to Step 3.
If it contains Informatica PowerCenter XML, ask the remaining ETL questions up front, in one sequence, before running the conversion:
1. Conversion target, via ask_user_question (multiSelect = false):
  "How should Informatica mappings be converted?
  1. dbt (default): each mapping becomes a dbt model orchestrated by Snowflake Tasks. Supports ETL stabilization and deploy.
  2. Snowflake Scripting (preview): each mapping becomes a standalone Snowflake stored procedure the Task graph calls. Stabilization and deploy are skipped for this preview flavor."
2. If the answer is dbt, also ask (multiSelect = false): "Consolidate dbt model chains to reduce the number of generated model files?". On yes, set CONSOLIDATE_DBT = true for Step 4.
3. If the answer is Snowflake Scripting, set SCRIPTING_MODE = true for Step 4.

Read the full file on GitHub · 243 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 243 lines · 0 tokens per session scan A 22b15d0c4d82

Subscribe to this mod's changes

convert is a skill published in the GitHub repository sfc-gh-dflippo/snowflake-dbt-demo (33 stars, last pushed 3d ago), licensed Apache-2.0. It adds 64 tokens to every session and 3,257 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-10.

Databases

create-pr

Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.

prisma/orm · 48 tokens

schema-exploration

Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.

langchain-ai/deepagents · 57 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens

nornicdb-cypher-queries

Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.

orneryd/NornicDB · 79 tokens

supabase

Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…

PentesterFlow/agent · 120 tokens

volcengine-rds-postgresql

A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.

bytedance/agentkit-samples · 63 tokens