Exasol import
Skill exasol-labs/exasol-agent-skills/plugins/exasol/skills/exasol-import
Exasol skills for AI agents. Optimized for Claude Code and OpenAI Codex 🤖
npx -y skills add exasol-labs/exasol-agent-skills --skill exasol-importAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use Exasol IMPORT SQL plus exapump local file upload workflows for moving data into Exasol. Covers CSV, FBV, Parquet, connection objects, cloud credential patterns, reject handling, and staging-based import workflows.
SKILL.md
2.6 KB, as published. Nobody here has run it
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:
- If the user mentions a specific profile name, test it with
exapump sql --profile <name> "SELECT 1"; always place--profileafter the subcommand. - Otherwise, test the default profile with
exapump sql "SELECT 1". - If the check fails, run
exapump profile list. - If profiles exist, ask which one to use and retry with
exapump sql --profile <name> "SELECT 1"; keep--profileafter the subcommand. - If a non-default profile is selected, include the same
--profile <name>after the subcommand on subsequentexapumpcommands, such asexapump upload --profile <name> <file> --table <schema.table>. - If no profiles exist, tell the user to run
exapump profile add defaultand retry. - Never read or reference the exapump configuration file.
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
-
Local files on the user machine
- Trigger phrases:
upload csv,upload parquet,exapump upload,from local - Load:
references/import.md
- Trigger phrases:
-
Remote or cloud files reachable by Exasol
- Trigger phrases:
IMPORT,IMPORT INTO,S3,Azure Blob,GCS,FTP,SFTP,HTTP,HTTPS,CREATE CONNECTIONwith import or object-store loading intent - Load:
references/import.md
- Trigger phrases:
-
Parquet-specific behavior
- Trigger phrases:
parquet,SOURCE COLUMN NAMES,SkipCols,MaxConnections,MaxConcurrentReads - Load:
references/import.md
- Trigger phrases:
Notes
- Use this skill only for direct data movement into Exasol.
- Use exasol-export for native
EXPORT, local export workflows, andCREATE CONNECTIONquestions tied to export target setup. - Use exasol-database for general
CREATE CONNECTIONquestions, SQL, schema inspection, and table design. - Use exasol-extension-catalog when the user is asking for extension-based object-storage loading workflows or federated-read alternatives rather than direct
IMPORT.