exasollisted

# Exasol Router Skill Use this skill whenever the user asks about Exasol. The user does not need to know internal skill names. Treat `/exasol <task>` and natural-language Exasol requests as the public interface. Choose the narrowest skill whose front-matter `description` matches the request. When several match, apply the precedence rules below; when several genuinely apply, load them in dependency order. ## Precedence Rules **Cloud Storage Extension over native import and export.** When a request mentions `FROM SCRIPT CLOUD_STORAGE_EXTENSION`, `INTO SCRIPT CLOUD_STORAGE_EXTENSION`, `CLOUD_STORAGE_EXTENSION.IMPORT_PATH`, or `CLOUD_STORAGE_EXTENSION.EXPORT_PATH`, prefer **exasol-cloud-storage-extension** over **exasol-import** or **exasol-export**. **Object-storage formats that only the extension reads.** When a request mentions importing `Avro`, `ORC`, or `Delta` from object storage such as S3, Azure Blob Storage, Azure Data Lake, Google Cloud Storage, HDFS, or Alluxio, prefer **exasol-cloud-storage-extension** unless the user clearly asks for native `IMPORT`. Native import handles CSV, FBV, and Parquet; it does not read those three formats, so a description match on "import from S3" alone routes the request wrongly. **Import and export over general database work.** When a request mentions `IMPORT`, `IMPORT INTO`, or `exapump upload`, prefer **exasol-import** over **exasol-database** even if the wording also contains generic terms such as `SQL` or `query`. When it mentio