How do I install the Copy Connections skill?

Run npx skillmds@latest add fivetran/copy-connections 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 Copy Connections 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 Copy Connections?

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 Copy Connections free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Copy Connections?

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

Copy Connections by fivetran — Agent Skill

Name: Copy Connections
Author: fivetran

Copy Connections

Use this skill when the user wants to copy, clone, migrate, or replicate their Fivetran connections from one destination to another — whether same destination type (e.g., splitting one warehouse into two) or different (e.g., Redshift to Snowflake). Handles the end-to-end workflow including scoping, validation, credential handling, and execution.

fivetran eac59d2 2.3 KB Updated Sep 17, 2026

File contents

Copy Connections (coordinator)

Purpose. This is the top-level coordinator for the Copy Connections workflow. It orchestrates five sub-skills:

copy-connections-scope — gather user intent, fetch current state, produce a structured copy plan
copy-connections-validate — check the plan for issues before execution
copy-connections-execute — create connection shells with config, install Quickstart packages
copy-connections-credentials — attach credentials (via API or direct user to Fivetran UI)
copy-connections-schema — run setup tests, then apply schema config (table/column selections, sync modes, hashing)

State lives in .copy-connections/ in the user's working directory:

copy_plan.yaml — written by scope, consumed by validate, execute, and schema
validation_report.yaml — written by validate, consumed by execute
credentials.yaml (optional) — written by the user if they chose file-based credential collection
results.md — written by execute, updated by credentials and schema

Key constraints this coordinator enforces:

Execute refuses to run without a passing validation_report.yaml
Validate refuses to run without a copy_plan.yaml
Schema config can only be applied after credentials are in place — the schema doesn't exist until then
The coordinator can re-enter scope at any phase if the user wants to change their mind; this invalidates downstream artifacts
If sub-skills detect inconsistent state (e.g., plan exists but references connections that have since been deleted), the coordinator surfaces this and asks the user how to proceed

What the coordinator does not do. It does not implement business logic itself. All product knowledge (what's copyable, what isn't, which config fields are portable across destination types, how to handle OAuth connectors) lives in the sub-skills. The coordinator is flow control.

---name: copy-connectionsdescription: Use this skill when the user wants to copy, clone, migrate, or replicate their Fivetran connections from one destination to another — whether same destination type (e.g., splitting one warehouse into two) or different (e.g., Redshift to Snowflake). Handles the end-to-end workflow including scoping, validation, credential handling, and execution.---# Copy Connections (coordinator)**Purpose.** This is the top-level coordinator for the Copy Connections workflow. It orchestrates five sub-skills:1. `copy-connections-scope` — gather user intent, fetch current state, produce a structured copy plan2. `copy-connections-validate` — check the plan for issues before execution3. `copy-connections-execute` — create connection shells with config, install Quickstart packages4. `copy-connections-credentials` — attach credentials (via API or direct user to Fivetran UI)5. `copy-connections-schema` — run setup tests, then apply schema config (table/column selections, sync modes, hashing)**State lives in `.copy-connections/`** in the user's working directory:- `copy_plan.yaml` — written by scope, consumed by validate, execute, and schema- `validation_report.yaml` — written by validate, consumed by execute- `credentials.yaml` (optional) — written by the user if they chose file-based credential collection- `results.md` — written by execute, updated by credentials and schema**Key constraints this coordinator enforces:**- Execute refuses to run without a passing `validation_report.yaml`- Validate refuses to run without a `copy_plan.yaml`- Schema config can only be applied after credentials are in place — the schema doesn't exist until then- The coordinator can re-enter scope at any phase if the user wants to change their mind; this invalidates downstream artifacts- If sub-skills detect inconsistent state (e.g., plan exists but references connections that have since been deleted), the coordinator surfaces this and asks the user how to proceed**What the coordinator does not do.** It does not implement business logic itself. All product knowledge (what's copyable, what isn't, which config fields are portable across destination types, how to handle OAuth connectors) lives in the sub-skills. The coordinator is flow control.

Frequently asked questions