From copy-connections
Use this skill AFTER copy-connections-execute has successfully created connection shells, to help the user attach credentials to their newly-created connections. Identifies what auth each connection uses, offers flexible credential collection (bulk file, one-by-one, or UI self-service), and provides Fivetran UI links for anything the user prefers to handle themselves. Invoke from the copy-connections coordinator after execute reports success.
How this skill is triggered — by the user, by Claude, or both
Slash command
/copy-connections:copy-connections-credentialsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill runs **after** execute has created the connection shells. It helps the user get credentials attached to their connections so the schema skill can run next.
This skill runs after execute has created the connection shells. It helps the user get credentials attached to their connections so the schema skill can run next.
The direct link to a connection's setup page is:
https://fivetran.com/dashboard/connections/<connection_id>
Where <connection_id> is the target connection ID returned by create_connection during execute (recorded in .copy-connections/results.md).
Be flexible and user-friendly. Different users will want to handle credentials differently — some will hand you a file with everything, some will want to go connection-by-connection, some will just want links to the Fivetran UI. Adapt to the user rather than forcing a specific flow.
During scope, get_connection_details returned the full config for each connection. Credential fields came back masked as "********". The plan records which fields are masked and classifies each connection's auth style:
modify_connection.Use this information to tell the user what each connection needs and what their options are.
Start by showing the user what's needed. For each connection, explain what kind of auth it uses and what fields need to be filled. Group by auth type so the picture is clear.
For OAuth connections, always provide the Fivetran UI link. There's no API path for OAuth — be upfront about this. Make it easy: give them the direct link to each connection's setup page.
For credential-based connections, let the user choose how to provide them. Options include:
If they provide a file or bulk credentials, check for gaps. If any connections are missing, ask about the remaining ones rather than silently skipping them.
Don't be rigid about the collection method. If they start giving you credentials inline, don't stop them to ask about a mode. If they say "here's a file," read it. If they say "just give me the links," give links. Match their energy.
Patch credentials via modify_connection with the credential field values. Always use run_setup_tests: false — setup tests are the schema skill's job, and only run_connection_setup_tests (not modify_connection with run_setup_tests: true) triggers schema discovery. Process and report results.
After patching, report what succeeded and what failed. If something fails, let them know they can fix it in the UI or retry.
.copy-connections/results.md doesn't exist, tell the user to run execute first.Prompt the user about the next step: running setup tests and applying schema config via the copy-connections-schema skill. If some connections still need credentials (OAuth not done yet, some skipped), mention those and suggest coming back after they're handled.
These are non-negotiable.
.gitignore protection. If in a git repo and credentials.yaml isn't in .gitignore, add it and tell the user. Prompt for cleanup when done — don't auto-delete.Users may run this multiple times. On re-run, check results.md to see what still needs credentials and focus on those. Offer to re-patch already-done ones too (e.g., rotated key).
Credentials don't make a connection exist; they make it connectable. The connection shells are already real connections in Fivetran — just paused and untested.
OAuth truly cannot be done from the CLI. It requires a browser redirect. Provide the link and move on.
Setup tests are NOT part of this skill. They happen in the schema skill after credentials are in place.
run_setup_tests: true on modify_connection.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub fivetran/copy-connections