lake-catalog
Engine-agnostic oleander lake catalog conventions: catalog.namespace.table naming, hierarchy, and catalog-qualified reads/writes without raw storage paths. Use when naming tables, choosing namespaces, or referencing the lake catalog from Spark, Polars, SQL, or another engine.
Install
With your agent
Install OMGSkills skill "oleanderhq/claude-plugin:skills/lake-catalog" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/OleanderHQ/claude-plugin /tmp/claude-plugin && ln -s /tmp/claude-plugin/skills/lake-catalog ~/.claude/skills/lake-catalog
From README
oleander Lake Catalog Use this skill when reading from or writing to the oleander lake catalog from Spark, Polars, SQL, or another engine. Catalog hierarchy Tables are addressed as catalog.namespace.table: catalog: always oleander for the managed Lakekeeper-backed catalog namespace: a logical grouping (e.g., default, sanfrancisco, myorg) table: the table name By default, default and telemetry namespaces are available out of the box. The telemetry namespace contains oleander-managed data you can query directly (for example oleander.telemetry.runevents, oleander.telemetry.traces, and oleander.telemetry.logs). These tables are partitioned on their time column and are reachable over MCP with queryrun — see the lake-query skill. Examples: Referencing tables Always use fully qualified table names through the engine's catalog integration. Do not build raw storage paths such as S3 URIs when reading or writing Iceberg tables.
More from this repo
lake-query
Runs lake SQL through oleander's query router: query_run for reads, query_submit for writes, spark_sql_submit for named...
polars-submit
Runs Polars queries or scripts on oleander via the CLI, in local or distributed mode, and saves results to the lake...
spark-best-practices
General Apache Spark best practices for scalable, maintainable DataFrame jobs: avoid driver materialization, reduce...
