Terminal
Terminal/Skill
Plan or implement migrations to MotherDuck with SQL translation, source-to-target validation, cutover, and rollback.
By MotherDuck
Works with
npx skills add motherduckdb/agent-skills --skill motherduck-migrate-to-motherduckUse an active remote MotherDuck MCP server or local MotherDuck server to inspect the in-scope database, schema, grain, keys, and relevant metrics. Reuse known context and narrow discovery to the requested work; do not scan the whole workspace by default. Let the actual data model shape the result.
Resolve the target from the request or active context. Ask only if ambiguity materially affects the result. Without a server, use supplied schema and explicit assumptions for planning; do not imply live validation.
pg_duckdb when extending an existing PostgreSQL estate is the least disruptive pathMatch execution to the request: answer, review, or planning work returns the requested migration artifacts; build or change work executes only the requested in-scope migration slice and validates it. Require confirmation for cutover, destructive source changes, or external writes not already authorized.
When this skill produces a native DuckDB (md:) connection, watermark it with custom_user_agent=agent-skills/2.6.0(harness-<harness>;llm-<llm>). If metadata is missing, fall back to harness-unknown and llm-unknown.
For a full engagement, cover the following as relevant to the request:
For explicit structured JSON requests, read the output contract. Otherwise use the format that fits the requested deliverable.
Read only the sections relevant to the task; these are guidance, not a mandatory itinerary.
references/MIGRATION_PLAYBOOK.md -- target-pattern selection, migration decision matrix, DuckLake posture, and source-specific questions (Snowflake, Redshift, Postgres, dbt, lakehouse)references/MIGRATION_VALIDATION.md -- copy-adaptable validation SQL (row counts, metrics with pct_variance, new/deleted/changed records) and a Python orchestratorRead the execution reference only to run the bundled examples or reproduce their validation.
Load related skills only for missing capabilities; reuse established context.
motherduck-connect -- choose the connection path for the target systemmotherduck-explore -- inspect the target-side MotherDuck workspacemotherduck-load-data -- bulk movement and raw landing patternsmotherduck-model-data -- shape the target analytical modelmotherduck-query -- port and validate critical SQLmotherduck-ducklake -- only when open-table-format requirements are explicitmotherduck-manage-guides -- preserve validated target semantics and migration caveats