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. ## Routing Algorithm Choose the narrowest matching route. If multiple routes apply, load them in dependency order. 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 native import or export routes. 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`. When a request mentions `IMPORT`, `IMPORT INTO`, `exapump upload`, or other import-specific phrases, prefer **exasol-import** over the broader database route even if the wording also contains generic terms such as `SQL` or `query`. When a request mentions `EXPORT`, `EXPORT INTO`, or `exapump export`, prefer **exasol-export** over the broader database route. When a request mentions custom virtual schema adapter implementation, source-specific JDBC dialect code, custom document-file adapter code, `virtual-schema-common-jdbc`, adapter JAR packaging, custom adapter properties, type mapping, pushdown capabilities, metadata reader behavior,