Exasol itde

Skill exasol-labs/exasol-agent-skills/plugins/exasol/skills/exasol-itde

Exasol skills for AI agents. Optimized for Claude Code and OpenAI Codex 🤖

Install

npx -y skills add exasol-labs/exasol-agent-skills --skill exasol-itde

Assembled 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 notebook-connector's itde_manager to run a local Docker-based Exasol database. Covers bring_itde_up, get_itde_status, restart_itde, take_itde_down, and how ITDE populates notebook-connector configuration automatically.

SKILL.md

2.2 KB, as published. Nobody here has run it

Exasol ITDE Skill

Trigger when the user mentions ITDE, docker-db, local Exasol Docker database, bring_itde_up, restart_itde, take_itde_down, or local notebook-connector database setup.

Routing Algorithm

Start local Docker DB
- Trigger phrases: bring_itde_up, start local exasol, docker-db
- Load: references/itde-lifecycle.md
- Use scripts from: scripts/
Check status / restart / tear down
- Trigger phrases: get_itde_status, restart_itde, take_itde_down, container status
- Load: references/itde-lifecycle.md
- Use scripts from: scripts/
Config not present yet
- Activate exasol-ai-setup

Validation

Use the lifecycle scripts to validate the stored ITDE setup:

run scripts/check_itde_status.py after setup changes
after bring_itde_up, expect ItdeContainerStatus.READY
if the next step is the shared exasol-ai-setup validation flow, save storage_backend=onprem first because bring_itde_up(...) does not populate that key itself
set db_schema yourself before handing off to schema-dependent workflows such as SQLAlchemy, Ibis, TE, or TXAIE validation
after teardown, expect ABSENT or a clean no-container state

Expected failure mode:

scripts/restart_itde.py should raise a runtime error if the Docker-DB container does not exist yet
shared setup validation can fail with missing storage_backend or db_schema even when ITDE itself is healthy, because those keys are not written by bring_itde_up(...)
if status checks fail because the store is missing, switch back to exasol-ai-setup

Notes

ITDE is the easiest local development database path for notebook-connector.
bring_itde_up populates the secure config store with the generated DB and BucketFS connection details automatically.
bring_itde_up does not populate storage_backend or db_schema.
After ITDE is ready, other notebook-connector connection APIs can be used without manual DB/BucketFS entry.