菜单
Capture the data migration + validation strategy (migration type, sync strategy, extraction strategy, target table type; validation type + sync strategy) by driving the data-migration-setup and data-validation-setup wizards to completion.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Snowflake-Labs/cortex-code-migrations --skill data-strategy命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Shared infrastructure setup for data migration and data validation — prerequisites, compute pool, worker config, and source database/schema capture.
Setup, run, and report on cloud data migration — workflow YAML, migrate_data run, background Monitor (or poll fallback), and end-of-run summary for the user.
Core migration loop for a single stored procedure, function, or BTEQ script. Iterates deploy -> test -> diagnose -> fix until Snowflake output matches source.
正在显示 SKILL.md
| name | data-strategy |
| description | Capture the data migration + validation strategy (migration type, sync strategy, extraction strategy, target table type; validation type + sync strategy) by driving the data-migration-setup and data-validation-setup wizards to completion. |
| parent_skill | migration |
| license | Proprietary. See License-Skills for complete terms |
Capture the project's data migration and validation strategy by driving the existing
data-migration-setup and data-validation-setup wizards to completion. This skill only drives
those two wizards — it asks no new questions of its own (the questions live in those machines) and makes
no assumptions about who invoked it. Deciding whether to capture the strategy is the caller's job; when
this skill runs, it runs the wizards.
Drive the data-migration-setup machine to completion: call progress_setup(mode="data_migration") in a
loop until the response's completed is true — ask each response's next_prompt (plus any then_ask,
in the same turn) and send the answers back with progress_setup(mode="data_migration", answers={...}).
If the strategy was already chosen (e.g. a prior migration set it lazily), the first call returns
completed: true immediately — do not re-prompt.
Then drive the data-validation-setup machine the same way: progress_setup(mode="data_validation") in
a loop until completed. An already-chosen strategy returns completed: true at once.
The choices persist to plugin.yml as data_migration_type, data_migration_sync_strategy,
data_migration_extraction_strategy, data_migration_target_table_type (Redshift), data_validation_type,
and data_validation_sync_strategy.
Infrastructure readiness (compute pool / orchestrator service) is not covered here — that is the shared
../../data-infrastructure/SKILL.md. This skill only captures the data strategy.
Return control to the caller.
