[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B39902JKX2YVVNP5DMTATZ":3,"skill-same:01M7B39902JKX2YVVNP5DMTATZ":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7B39902JKX2YVVNP5DMTATZ","motherduck-migrate-to-motherduck",null,"Plan a migration onto MotherDuck. Use when moving from Snowflake, BigQuery, Redshift, PostgreSQL, dbt-heavy stacks, or lakehouse tooling and the key decisions are target pattern, cutover slices, source-vs-target validation, rollback, and native-versus-DuckLake posture.","cianfhoghlaim\u002Fciandlithe","cianfhoghlaim","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F57019547?v=4","01M6DWR3GAV495PYDTZSR1FZNX","Cian Mac (an Déisigh Uí) Liatháin || Deacy-Lyons","01M7B2QN19FG7B5G3DCB73XWEK",1,"MIT","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fciandlithe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-migrate-to-motherduck\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: motherduck-migrate-to-motherduck\ndescription: Plan a migration onto MotherDuck. Use when moving from Snowflake, BigQuery, Redshift, PostgreSQL, dbt-heavy stacks, or lakehouse tooling and the key decisions are target pattern, cutover slices, source-vs-target validation, rollback, and native-versus-DuckLake posture.\nlicense: MIT\n---\n\n# Migrate to MotherDuck\n\nUse this skill when the user needs a migration plan from another warehouse, PostgreSQL estate, or mixed analytics stack onto MotherDuck.\n\nThis is a use-case skill. It orchestrates `motherduck-connect`, `motherduck-explore`, `motherduck-load-data`, `motherduck-model-data`, `motherduck-query`, and `motherduck-ducklake`.\n\n## Start Here: Is a MotherDuck Server Active?\n\nAlways determine this before writing a migration plan.\n\n- If a **remote MotherDuck MCP server** or **local MotherDuck server** is active, use it.\n- Ask which MotherDuck database or workspace will receive the migration if the user has not specified it.\n- Explore the live target side first when available:\n  - existing databases and schemas\n  - current landing zones\n  - current analytical tables\n  - naming conventions\n  - any partial migration already in place\n\nAlso capture the source-side shape:\n\n- source platform\n- source table grain\n- key metrics\n- validation keys\n- serving workloads after cutover\n\nIf no server is active, ask for representative source and target schemas before finalizing the migration plan.\n\n## Use This Skill When\n\n- The user is moving from Snowflake, Redshift, Postgres, or similar.\n- The user needs cutover sequencing and validation.\n- The user needs to decide between native MotherDuck, `pg_duckdb`, or DuckLake.\n- The migration plan needs rollback, not just a list of copy commands.\n\n## Migration Defaults\n\n- native MotherDuck storage first\n- `pg_duckdb` when extending an existing PostgreSQL estate is the least disruptive path\n- validate before cutover\n- port SQL dialect and data types deliberately before performance tuning\n- phased cutover over big-bang replacement\n\n## Workflow\n\n1. Confirm whether live MotherDuck discovery is available.\n2. Classify the source system and the target serving pattern.\n3. Inspect the target-side MotherDuck layout if available.\n4. Pick the connection and ingestion path.\n5. Inventory incompatible SQL, functions, data types, and operational assumptions.\n6. Rebuild the analytical model in DuckDB SQL.\n7. Run source-vs-target validation.\n8. Cut over one workload at a time.\n\nWhen this skill produces a native DuckDB (`md:`) connection, watermark it with `custom_user_agent=agent-skills\u002F2.3.0(harness-\u003Charness>;llm-\u003Cllm>)`. If metadata is missing, fall back to `harness-unknown` and `llm-unknown`.\n\n## Output\n\nThe output of this skill should be:\n\n- the target pattern\n- the migration sequence\n- the validation plan\n- the rollback path\n- the first cutover slice\n\nIf the caller explicitly asks for structured JSON, return raw JSON only with no Markdown fences or prose before\u002Fafter it.\nThis is mainly for automated tests, regression checks, or downstream tooling that needs a stable machine-readable shape. Normal human-facing use of the skill can stay in prose unless JSON is explicitly requested.\n\nUse this exact top-level shape when JSON is requested:\n\n```json\n{\n  \"summary\": {},\n  \"assumptions\": [],\n  \"implementation_plan\": [],\n  \"validation_plan\": [],\n  \"risks\": []\n}\n```\n\n## References\n\nRead these as reference, not as scripts to execute:\n\n- `references\u002FMIGRATION_PLAYBOOK.md` -- target-pattern selection, migration decision matrix, DuckLake posture, and source-specific questions (Snowflake, Redshift, Postgres, dbt, lakehouse)\n- `references\u002FMIGRATION_VALIDATION.md` -- copy-adaptable validation SQL (row counts, metrics with `pct_variance`, new\u002Fdeleted\u002Fchanged records) and a Python orchestrator\n\n## Runnable Artifact\n\n- `artifacts\u002Fmigration_validation_example.py` -- MotherDuck-backed Python example for source-vs-target validation and variance reporting\n- `artifacts\u002Fmigration_validation_example.ts` -- TypeScript companion artifact with the same validation output contract\n\nRun it with:\n\n```bash\nuv run --with duckdb python skills\u002Fmotherduck-migrate-to-motherduck\u002Fartifacts\u002Fmigration_validation_example.py\n```\n\nRun the same validation flow against temporary MotherDuck databases:\n\n```bash\nMOTHERDUCK_ARTIFACT_USE_MOTHERDUCK=1 \\\nuv run --with duckdb python skills\u002Fmotherduck-migrate-to-motherduck\u002Fartifacts\u002Fmigration_validation_example.py\n```\n\nValidate the TypeScript companion artifact:\n\n```bash\nuv run scripts\u002Ftest_typescript_artifacts.py\n```\n\n## Related Skills\n\n- `motherduck-connect` -- choose the connection path for the target system\n- `motherduck-explore` -- inspect the target-side MotherDuck workspace\n- `motherduck-load-data` -- bulk movement and raw landing patterns\n- `motherduck-model-data` -- shape the target analytical model\n- `motherduck-query` -- port and validate critical SQL\n- `motherduck-ducklake` -- only when open-table-format requirements are explicit\n","# Migrate to MotherDuck\n\nUse this skill when the user needs a migration plan from another warehouse, PostgreSQL estate, or mixed analytics stack onto MotherDuck.\n\nThis is a use-case skill. It orchestrates `motherduck-connect`, `motherduck-explore`, `motherduck-load-data`, `motherduck-model-data`, `motherduck-query`, and `motherduck-ducklake`.\n\n## Start Here: Is a MotherDuck Server Active?\n\nAlways determine this before writing a migration plan.\n\n- If a **remote MotherDuck MCP server** or **local MotherDuck server** is active, use it.\n- Ask which MotherDuck database or workspace will receive the migration if the user has not specified it.\n- Explore the live target side first when available:\n  - existing databases and schemas\n  - current landing zones\n  - current analytical tables\n  - naming conventions\n  - any partial migration already in place\n\nAlso capture the source-side shape:\n\n- source platform\n- source table grain\n- key metrics\n- validation keys\n- serving workloads after cutover\n\nIf no server is active, ask for representative source and target schemas before finalizing the migration plan.\n\n## Use This Skill When\n\n- The user is moving from Snowflake, Redshift, Postgres, or similar.\n- The user needs cutover sequencing and validation.\n- The user needs to decide between native MotherDuck, `pg_duckdb`, or DuckLake.\n- The migration plan needs rollback, not just a list of copy commands.\n\n## Migration Defaults\n\n- native MotherDuck storage first\n- `pg_duckdb` when extending an existing PostgreSQL estate is the least disruptive path\n- validate before cutover\n- port SQL dialect and data types deliberately before performance tuning\n- phased cutover over big-bang replacement\n\n## Workflow\n\n1. Confirm whether live MotherDuck discovery is available.\n2. Classify the source system and the target serving pattern.\n3. Inspect the target-side MotherDuck layout if available.\n4. Pick the connection and ingestion path.\n5. Inventory incompatible SQL, functions, data types, and operational assumptions.\n6. Rebuild the analytical model in DuckDB SQL.\n7. Run source-vs-target validation.\n8. Cut over one workload at a time.\n\nWhen this skill produces a native DuckDB (`md:`) connection, watermark it with `custom_user_agent=agent-skills\u002F2.3.0(harness-\u003Charness>;llm-\u003Cllm>)`. If metadata is missing, fall back to `harness-unknown` and `llm-unknown`.\n\n## Output\n\nThe output of this skill should be:\n\n- the target pattern\n- the migration sequence\n- the validation plan\n- the rollback path\n- the first cutover slice\n\nIf the caller explicitly asks for structured JSON, return raw JSON only with no Markdown fences or prose before\u002Fafter it.\nThis is mainly for automated tests, regression checks, or downstream tooling that needs a stable machine-readable shape. Normal human-facing use of the skill can stay in prose unless JSON is explicitly requested.\n\nUse this exact top-level shape when JSON is requested:\n\n```json\n{\n  \"summary\": {},\n  \"assumptions\": [],\n  \"implementation_plan\": [],\n  \"validation_plan\": [],\n  \"risks\": []\n}\n```\n\n## References\n\nRead these as reference, not as scripts to execute:\n\n- `references\u002FMIGRATION_PLAYBOOK.md` -- target-pattern selection, migration decision matrix, DuckLake posture, and source-specific questions (Snowflake, Redshift, Postgres, dbt, lakehouse)\n- `references\u002FMIGRATION_VALIDATION.md` -- copy-adaptable validation SQL (row counts, metrics with `pct_variance`, new\u002Fdeleted\u002Fchanged records) and a Python orchestrator\n\n## Runnable Artifact\n\n- `artifacts\u002Fmigration_validation_example.py` -- MotherDuck-backed Python example for source-vs-target validation and variance reporting\n- `artifacts\u002Fmigration_validation_example.ts` -- TypeScript companion artifact with the same validation output contract\n\nRun it with:\n\n```bash\nuv run --with duckdb python skills\u002Fmotherduck-migrate-to-motherduck\u002Fartifacts\u002Fmigration_validation_example.py\n```\n\nRun the same validation flow against temporary MotherDuck databases:\n\n```bash\nMOTHERDUCK_ARTIFACT_USE_MOTHERDUCK=1 \\\nuv run --with duckdb python skills\u002Fmotherduck-migrate-to-motherduck\u002Fartifacts\u002Fmigration_validation_example.py\n```\n\nValidate the TypeScript companion artifact:\n\n```bash\nuv run scripts\u002Ftest_typescript_artifacts.py\n```\n\n## Related Skills\n\n- `motherduck-connect` -- choose the connection path for the target system\n- `motherduck-explore` -- inspect the target-side MotherDuck workspace\n- `motherduck-load-data` -- bulk movement and raw landing patterns\n- `motherduck-model-data` -- shape the target analytical model\n- `motherduck-query` -- port and validate critical SQL\n- `motherduck-ducklake` -- only when open-table-format requirements are explicit\n",{"name":5,"license":15,"description":7},"main","6283bdef5afa434010d035c077fed63a4ff0c00d",".agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-migrate-to-motherduck",0,"https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fciandlithe","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim","cianfhoghlaim.ie","Irish-British teacher, mathematician, foghlaimeoir || minority-language AI researcher || Lucht Siúil ||\r\nFine Gael + Alliance Party + Liberal Democrats Member","2026-11-13 20:49:56",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add cianfhoghlaim\u002Fciandlithe --skill motherduck-migrate-to-motherduck",{"tool":39,"command":40},"bunx","bunx skills add cianfhoghlaim\u002Fciandlithe --skill motherduck-migrate-to-motherduck",{"tool":42,"command":43},"pnpm","pnpm dlx skills add cianfhoghlaim\u002Fciandlithe --skill motherduck-migrate-to-motherduck","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fciandlithe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-migrate-to-motherduck\u002FSKILL.md",true,[47,53,57,63],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"artifacts\u002Fmigration_validation_example.py","SCRIPT","脚本",2190,"https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fciandlithe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-migrate-to-motherduck\u002Fartifacts\u002Fmigration_validation_example.py",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"artifacts\u002Fmigration_validation_example.ts",2814,"https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fciandlithe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-migrate-to-motherduck\u002Fartifacts\u002Fmigration_validation_example.ts",{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002FMIGRATION_PLAYBOOK.md","REFERENCE","参考文档",12100,"https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fciandlithe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-migrate-to-motherduck\u002Freferences\u002FMIGRATION_PLAYBOOK.md",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002FMIGRATION_VALIDATION.md",14670,"https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fciandlithe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-migrate-to-motherduck\u002Freferences\u002FMIGRATION_VALIDATION.md",[68,75,82,89,96,103],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7B3BCPBW729D6XVBJK8M7WJ","pydantic-ai-harness","Extend Pydantic AI agents with batteries-included capabilities from pydantic-ai-harness -- currently Code Mode, which collapses many tool calls into one sandboxed Python execution. Use when the user mentions pydantic-ai-harness, CodeMode, Monty, code mode, or tool sandboxing, when they want an agent to run agent-written Python, or when a Pydantic AI agent would benefit from orchestrating multiple tool calls in a single sandboxed script.","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fciandlithe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpydantic\u002Fpydantic-ai-harness\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7B3AQKKPS8AFZBJADH7PR01","building-pydantic-ai-agents","Build AI agents with Pydantic AI — tools, capabilities (including on-demand loading), structured output, streaming, testing, and multi-agent patterns. Use when the user mentions Pydantic AI, imports pydantic_ai, or asks to build an AI agent, add tools\u002Fcapabilities, defer capability loading, stream output, define agents from YAML, or test agent behavior.","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fciandlithe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpydantic\u002Fbuilding-pydantic-ai-agents\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7B39YG1J49ASJBKHKGBW03C","motherduck-share-data","Create and manage MotherDuck data shares for zero-copy, read-only data distribution. Use whenever someone wants to share a database with team members, another organization, or the public — covers CREATE SHARE, access\u002Fvisibility\u002Fupdate modes, GRANT READ ON SHARE, attaching share URLs, UPDATE SHARE, and REFRESH DATABASE.","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fciandlithe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-share-data\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7B39TVXB76BAE248616DTYR","motherduck-security-governance","Explain MotherDuck security, governance, and access-control patterns. Use for any question about SOC 2, GDPR, compliance, data residency, regions, SSO, service accounts, token handling, tenant isolation, sharing boundaries, snapshots and recovery, or governance posture — including when a security_compliance_owner, technical_owner, or application_builder is evaluating MotherDuck.","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fciandlithe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-security-governance\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7B39R4FJJTPXF6TAFA11F7V","motherduck-rest-api","MotherDuck REST API control-plane reference. Use when calling api.motherduck.com to provision service accounts, create, list, rotate, or revoke access tokens, configure Duckling instance sizes and read scaling, inspect active accounts, or mint Dive embed sessions. Not for SQL or data-plane query work.","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fciandlithe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-rest-api\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7B39NW25YGBFJHP36DAK521","motherduck-query","Execute DuckDB SQL queries against MotherDuck databases. Use when running analytics, aggregations, transformations, or any SQL operation. Covers query best practices, CTEs, window functions, QUALIFY, and performance optimization.","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fciandlithe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-query\u002FSKILL.md",[],[]]