How do I install the Migrate Object skill?

Run npx skillmds@latest add snowflake-labs/migrate-object in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Migrate Object safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Migrate Object?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Migrate Object free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Proprietary.

Who published Migrate Object?

snowflake-labs (@snowflake-labs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Migrate Object by snowflake-labs — Agent Skill

Name: Migrate Object
Author: snowflake-labs

File contents

Migrate Object — Reference

This document describes the conceptual flow for migrating a single object. The state machine drives execution — you do not follow these steps manually. Each task in the machine points to a specific guide via its skill field.

Overview

Each object goes through a pipeline managed by the state machine:

Claim — claimObject reserves the object for this user.
Checkout — checkoutBranch creates or switches to a git branch.
Convert — convert runs SnowConvert to produce initial Snowflake SQL.
Test prep — procedures/functions with a source side: createTests + captureBaseline generate test YAML and capture source-side baselines. Procedures/functions with no source (UDF helpers) skip this and go straight to deploy. BTEQ scripts: seedScript (binding values + import fixtures resolved from the shell script that runs it via scai test seed --bindings-from, hand-filled otherwise — see ../baseline-capture/seed-script/SKILL.md) then captureBaseline.
Deploy — deploy pushes the SQL to Snowflake. See DEPLOY.md.
Validate — depending on object type:
- Tables: migrateData → validateData
- Views: validateView
- Procedures/functions with a source side: runTests. See RUN_TESTS.md.
- Procedures/functions with no source: verify. See VERIFY.md.
- BTEQ scripts: runTests (deploy is skipped — the converted script is run by the test). See RUN_TESTS.md.
Fix loop — if deployment or validation fails, the machine enters a cycle:
- applyRules — apply known migration rules from the rule engine.
- fixCode — diagnose the failure and make targeted fixes. See DIAGNOSE_FIX.md.
- Loop back to deploy.
Extract rules — extractRules captures reusable rules from successful fixes. See DEDUCE_RULE.md.
Finalize — finalizeBranch commits and pushes, markDone closes the claim.

Task guides

Task	Guide	Purpose
`deploy`	DEPLOY.md	Pre-deploy checks, error table, file-update rules
`runTests`	RUN_TESTS.md	Interpreting results, dependency failure detection
`fixCode`	DIAGNOSE_FIX.md	Root cause analysis, minimal fix strategy
`extractRules`	DEDUCE_RULE.md	Capturing reusable rules from fixes

Complexity check

If the source SQL file has 200+ non-empty lines, consider the decompose-convert-assemble approach described in references/LONG_PROCEDURE.md instead of the standard fix loop.

Escalation criteria

Do NOT iterate blindly. Escalate to the user when:

Condition	Trigger
Same error persists	Same primary error for 3 consecutive iterations
Errors churning	Errors keep changing but never resolve after 5 total iterations

On escalation, present iteration history and offer: provide guidance, decompose and retry, skip, mark as needs human repair, or mark done.

---name: migrate-objectdescription: Core migration loop for a single stored procedure, function, or BTEQ script. Iterates deploy -> test -> diagnose -> fix until Snowflake output matches source.license: Proprietary. See License-Skills for complete terms---# Migrate Object — ReferenceThis document describes the conceptual flow for migrating a single object. The state machine drives execution — you do not follow these steps manually. Each task in the machine points to a specific guide via its `skill` field.## OverviewEach object goes through a pipeline managed by the state machine:1. **Claim** — `claimObject` reserves the object for this user.2. **Checkout** — `checkoutBranch` creates or switches to a git branch.3. **Convert** — `convert` runs SnowConvert to produce initial Snowflake SQL.4. **Test prep** — procedures/functions **with a source side**: `createTests` + `captureBaseline` generate test YAML and capture source-side baselines. Procedures/functions **with no source** (UDF helpers) skip this and go straight to deploy. BTEQ scripts: `seedScript` (binding values + import fixtures resolved from the shell script that runs it via `scai test seed --bindings-from`, hand-filled otherwise — see [../baseline-capture/seed-script/SKILL.md](../baseline-capture/seed-script/SKILL.md)) then `captureBaseline`.5. **Deploy** — `deploy` pushes the SQL to Snowflake. See [DEPLOY.md](DEPLOY.md).6. **Validate** — depending on object type: - Tables: `migrateData` → `validateData` - Views: `validateView` - Procedures/functions with a source side: `runTests`. See [RUN_TESTS.md](RUN_TESTS.md). - Procedures/functions with no source: `verify`. See [VERIFY.md](VERIFY.md). - BTEQ scripts: `runTests` (deploy is skipped — the converted script is run by the test). See [RUN_TESTS.md](RUN_TESTS.md).7. **Fix loop** — if deployment or validation fails, the machine enters a cycle: - `applyRules` — apply known migration rules from the rule engine. - `fixCode` — diagnose the failure and make targeted fixes. See [DIAGNOSE_FIX.md](DIAGNOSE_FIX.md). - Loop back to deploy.8. **Extract rules** — `extractRules` captures reusable rules from successful fixes. See [DEDUCE_RULE.md](DEDUCE_RULE.md).9. **Finalize** — `finalizeBranch` commits and pushes, `markDone` closes the claim.## Task guides| Task | Guide | Purpose ||------|-------|---------|| `deploy` | [DEPLOY.md](DEPLOY.md) | Pre-deploy checks, error table, file-update rules || `runTests` | [RUN_TESTS.md](RUN_TESTS.md) | Interpreting results, dependency failure detection || `fixCode` | [DIAGNOSE_FIX.md](DIAGNOSE_FIX.md) | Root cause analysis, minimal fix strategy || `extractRules` | [DEDUCE_RULE.md](DEDUCE_RULE.md) | Capturing reusable rules from fixes |## Complexity checkIf the source SQL file has **200+ non-empty lines**, consider the decompose-convert-assemble approach described in [references/LONG_PROCEDURE.md](references/LONG_PROCEDURE.md) instead of the standard fix loop.## Escalation criteriaDo NOT iterate blindly. Escalate to the user when:| Condition | Trigger ||-----------|---------|| Same error persists | Same primary error for 3 consecutive iterations || Errors churning | Errors keep changing but never resolve after 5 total iterations |On escalation, present iteration history and offer: provide guidance, decompose and retry, skip, mark as needs human repair, or mark done.

Frequently asked questions

Migrate Object