Lakehouse Table Format Engineering

Community

vaquarkhan

lakehouse-table-format-engineering

Guides agents through lakehouse table design and open table format decisions. Use when designing or changing Iceberg, Delta, Hudi, partitioning, schema evolution, compaction, or batch and streaming interoperability.

Overview

Publisher	vaquarkhan
Repository	`data-engineering-agent-skills`
Skill name	`lakehouse-table-format-engineering`
Stars	60
Forks	8
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by vaquarkhan on GitHub. Read the source before you install it.

Installation

Install the Lakehouse Table Format Engineering AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/lakehouse-table-format-engineering
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/lakehouse-table-format-engineering

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/vaquarkhan/data-engineering-agent-skills.git /tmp/data-engineering-agent-skills
mkdir -p .claude/skills
cp -r /tmp/data-engineering-agent-skills/skills/lakehouse-table-format-engineering .claude/skills/lakehouse-table-format-engineering

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Lakehouse Table Format Engineering in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Lakehouse Table Format Engineering on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Lakehouse Table Format Engineering is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Lakehouse Table Format Engineering

Overview

Use this skill when the storage layer itself is an architecture decision. It helps agents reason about Iceberg, Delta, Hudi, table evolution, partitioning, compaction, snapshot behavior, and how batch and streaming jobs interact with shared lakehouse tables.

When to Use

choosing between Iceberg, Delta, and Hudi
designing lakehouse datasets with update or merge behavior
changing partition strategy, snapshot retention, or compaction behavior
integrating Spark, Flink, or warehouse readers with shared table formats
implementing CDC-style or incremental lakehouse pipelines

Do not use this for unmanaged flat-file datasets that are not intended to behave like governed tables.

Workflow

Define the table contract. Include:
- grain and keys
- mutation model
- read patterns
- retention and snapshot policy
- compatibility requirements across engines
Pick the table format intentionally.
- Iceberg: strong open-table interoperability and metadata-driven planning
- Delta: strong lakehouse ergonomics and transactional patterns in Databricks-centered stacks
- Hudi: strong incremental and record-level update use cases
Design physical layout for lifecycle, not only day-one queries. Consider:
- partition evolution
- small-file control
- compaction
- metadata growth
- merge and delete behavior
Align compute engines with the table behavior. Batch and streaming writers must not conflict silently on checkpoints, commits, or schema changes.
Define maintenance and recovery operations. Table formats require operational housekeeping, not just one-time creation.

Common Rationalizations

Rationalization	Reality
"A table format is just a storage detail."	Format choice affects interoperability, maintenance, mutation semantics, and long-term cost.
"We can decide compaction later."	Small files and metadata bloat become operational pain quickly.
"Any engine can read and write the table the same way."	Cross-engine support varies, especially for advanced write and mutation behavior.

Red Flags

format selection is based only on familiarity
mutation and delete semantics are undefined
snapshot retention and cleanup are ignored
batch and stream writers target the same table without coordination
interoperability requirements are discovered after adoption

Verification

Table format choice is tied to interoperability and workload needs
Mutation, partitioning, retention, and compaction rules are explicit
Engine compatibility assumptions are documented
Maintenance and recovery procedures exist for the table lifecycle

Frequently asked questions

What does the Lakehouse Table Format Engineering AI skill do?

Why use Lakehouse Table Format Engineering on TypingMind?

Because you install it once and use it with any model. Lakehouse Table Format Engineering is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Lakehouse Table Format Engineering in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/lakehouse-table-format-engineering. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Lakehouse Table Format Engineering?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Lakehouse Table Format Engineering?

As many as you like. As long as a model supports skills, you can use Lakehouse Table Format Engineering with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Lakehouse Table Format Engineering AI skill free?

Yes. It is published on GitHub by vaquarkhan under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

1password

openclaw

OrganizationPopular

Set up and use 1Password CLI for sign-in, desktop integration, and reading or injecting secrets.

Apple Reminders

List, add, edit, complete, or delete Apple Reminders and reminder lists via remindctl.

Clawhub

Search ClawHub for skills when a requested capability is not already available; install, verify, update, uninstall, publish, or sync skills.

Diagnosing Superpowers

obra

CommunityPopular

Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Lakehouse Table Format Engineering

Overview

When to Use

Workflow

Common Rationalizations

Red Flags

Verification

Frequently asked questions

Related AI Skills

Set up your own AI workspace now