Exasol Import Skill

This skill covers only workflows that move data into Exasol.

Step 0: Establish Connection

Ensure a working exapump profile before giving terminal workflows that use exapump upload:

1. If the user names a profile, test it with exapump sql --profile <name> "SELECT 1"; always place --profile after the subcommand. Otherwise test the default profile with exapump sql "SELECT 1".
2. On success, proceed — and keep the same --profile <name> after the subcommand on every later command, such as exapump upload --profile <name> <file> --table <schema.table>.
3. On failure, run exapump profile list to see which profiles exist.
4. If profiles exist, present them and ask which to use, then inspect that one with exapump profile show <name> — it masks credentials — to confirm the required fields are set. Never read, cat, or print ~/.exapump/config.toml; it stores credentials in clear text. If a credential value does appear in any command output, do not repeat it in the conversation.
5. If no usable profile exists, have the user create one locally with exapump profile add <name> (omit --password and exapump prompts on a hidden line) or exapump profile init, then retry step 1. Never ask the user to paste a password into the conversation, and never pass one as a command-line argument.

Trigger when the user mentions IMPORT, IMPORT INTO, upload CSV, upload Parquet, local file load, exapump upload, S3 import, Azure Blob import, GCS import, Parquet import, or CREATE CONNECTION together with import or object-store loading intent.

Routing Algorithm