How do I install the Exasol Document Virtual Schemas skill?

Run npx skillmds@latest add exasol-labs/exasol-document-virtual-schemas in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Exasol Document Virtual Schemas safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Exasol Document Virtual Schemas?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Exasol Document Virtual Schemas free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Exasol Document Virtual Schemas?

exasol-labs (@exasol-labs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Exasol Document Virtual Schemas by exasol-labs

Name: Exasol Document Virtual Schemas
Author: exasol-labs

Exasol Document Virtual Schemas

Use Exasol document-file virtual schemas for federated read-only access to object and file storage — S3, Google Cloud Storage, Azure Blob Storage, and Azure Data Lake Storage Gen2 document files. Covers document-file adapter family selection, the EDML `MAPPING` definition, `CREATE VIRTUAL SCHEMA` usage, refresh workflows, and query-side troubleshooting.

exasol-labs Updated Sep 17, 2026

File contents

Exasol Document Virtual Schemas Skill

Trigger when the user mentions document virtual schema, document virtual schemas, document files virtual schema, document-file virtual schema adapter, EXPLAIN VIRTUAL for document-file/object-storage virtual schema troubleshooting, S3 document files, Google Cloud Storage document files, Azure Blob document files, Azure Data Lake Gen2 document files, or Azure Data Lake Storage Gen2 document files.

Routing Algorithm

Create and query a virtual schema
- Trigger phrases: document files virtual schema, S3 document files, Google Cloud Storage document files, Azure Blob document files, Azure Data Lake Gen2 document files, Azure Data Lake Storage Gen2 document files, query object storage
- Load: references/document-virtual-schemas.md
Refresh, debugging, and troubleshooting
- Trigger phrases: document files virtual schema, S3 document files, Google Cloud Storage document files, Azure Blob document files, Azure Data Lake Gen2 document files, Azure Data Lake Storage Gen2 document files, REFRESH, partial refresh, connection validation, pushdown, EXPLAIN VIRTUAL for document-file/object-storage virtual schema troubleshooting
- Load: references/document-virtual-schemas.md
Choose the right document-file adapter family
- Trigger phrases: document virtual schema, document virtual schemas, document-file virtual schema, document files virtual schema, S3 document files, Google Cloud Storage document files, Azure Blob document files, Azure Data Lake Gen2 document files, Azure Data Lake Storage Gen2 document files
- Load: references/document-virtual-schemas.md

Notes

Use this skill for federated read-only access through virtual schemas.
Use exasol-import or exasol-cloud-storage-extension when the user wants to copy data into Exasol instead of querying it in place.
Use exasol-jdbc-virtual-schemas when the source is a JDBC database rather than object or file storage.
Use exasol-virtual-schema-adapter-development when maintained document-file adapters are insufficient and the user needs custom adapter code, packaging, or adapter-side debugging.
Use exasol-extension-catalog when the source or integration family is still undecided.
Use exasol-bucketfs if the task is specifically about uploading the adapter JAR into BucketFS.

---name: exasol-document-virtual-schemasdescription: Use Exasol document-file virtual schemas for federated read-only access to object and file storage — S3, Google Cloud Storage, Azure Blob Storage, and Azure Data Lake Storage Gen2 document files. Covers document-file adapter family selection, the EDML `MAPPING` definition, `CREATE VIRTUAL SCHEMA` usage, refresh workflows, and query-side troubleshooting.---# Exasol Document Virtual Schemas SkillTrigger when the user mentions **document virtual schema**, **document virtual schemas**, **document files virtual schema**, **document-file virtual schema adapter**, **EXPLAIN VIRTUAL** for document-file/object-storage virtual schema troubleshooting, **S3 document files**, **Google Cloud Storage document files**, **Azure Blob document files**, **Azure Data Lake Gen2 document files**, or **Azure Data Lake Storage Gen2 document files**.## Routing Algorithm1. **Create and query a virtual schema** - Trigger phrases: `document files virtual schema`, `S3 document files`, `Google Cloud Storage document files`, `Azure Blob document files`, `Azure Data Lake Gen2 document files`, `Azure Data Lake Storage Gen2 document files`, `query object storage` - Load: `references/document-virtual-schemas.md`2. **Refresh, debugging, and troubleshooting** - Trigger phrases: `document files virtual schema`, `S3 document files`, `Google Cloud Storage document files`, `Azure Blob document files`, `Azure Data Lake Gen2 document files`, `Azure Data Lake Storage Gen2 document files`, `REFRESH`, `partial refresh`, `connection validation`, `pushdown`, `EXPLAIN VIRTUAL` for document-file/object-storage virtual schema troubleshooting - Load: `references/document-virtual-schemas.md`3. **Choose the right document-file adapter family** - Trigger phrases: `document virtual schema`, `document virtual schemas`, `document-file virtual schema`, `document files virtual schema`, `S3 document files`, `Google Cloud Storage document files`, `Azure Blob document files`, `Azure Data Lake Gen2 document files`, `Azure Data Lake Storage Gen2 document files` - Load: `references/document-virtual-schemas.md`## Notes- Use this skill for federated read-only access through virtual schemas.- Use **exasol-import** or **exasol-cloud-storage-extension** when the user wants to copy data into Exasol instead of querying it in place.- Use **exasol-jdbc-virtual-schemas** when the source is a JDBC database rather than object or file storage.- Use **exasol-virtual-schema-adapter-development** when maintained document-file adapters are insufficient and the user needs custom adapter code, packaging, or adapter-side debugging.- Use **exasol-extension-catalog** when the source or integration family is still undecided.- Use **exasol-bucketfs** if the task is specifically about uploading the adapter JAR into BucketFS.

Frequently asked questions