Data Data Lakehouse

Use when the user asks about lakehouse architecture, choosing Iceberg or Delta for our lakehouse, medallion bronze/silver/gold layers, Databricks Unity Catalog, Delta Sharing, Apache Paimon or multi-engine catalogs (Polaris, Glue). Produces layer design, catalog and access model and format commitment. Not for single-table operations (use data-data-lake).

45 stars 6 forksAI, LLMs & Agents

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill data-data-lakehouse
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/data/data-lakehouse ~/.claude/skills/data-data-lakehouse

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Data Data Lakehouse

## Purpose
Design lakehouse architectures that merge data lake flexibility with warehouse reliability. Implement medallion architecture for data quality progression, Unity Catalog for governance, Delta Sharing for data collaboration, and multi-cloud deployment patterns.

## Agent Protocol

### Trigger
Exact user phrases: "lakehouse", "medallion architecture", "bronze", "silver", "gold", "Databricks", "Unity Catalog", "Delta Sharing", "Apache Paimon", "multi-cloud lakehouse", "open formats", "lakehouse governance", "data mesh lakehouse".

### Input Context
Before activating, verify:
- Cloud provider (AWS, Azure, GCP, multi-cloud)
- Lakehouse platform (Databricks, AWS EMR, Azure Synapse, GCP Dataproc)
- Table format (Delta, Iceberg, Paimon)
- Data sources volume and types
- Number of data producers and consumers
- Security requirements (RBAC, column mask, row filter)
- Data sharing requirements (internal teams, external partners)

### Output Artifact
Lakehouse architecture with medallion layers, Unity Catalog configuration, and platform deployment specs.

### Response Format
```
Lakehouse Platform: {Databricks | EMR + Iceberg | Synapse + Delta | Dataproc + Iceberg}
Catalog: {Unity Catalog | Hive Metastore | AWS Glue | Nessie}
Table Format: {Delta | Iceberg | Paimon}
Medallion Layers: Bronze (raw), Silver (cleaned), Gold (aggregated)
Sharing: {Delta Sharing | open | proprietary}
```
```yaml
# Unity Catalog metastore config
# Medallion pipeline YAML
```
Read the full skill on GitHub

Details

Skill name
data-data-lakehouse
Path
skills/data/data-lakehouse/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Data Data Lakehouse skill do?

Use when the user asks about lakehouse architecture, choosing Iceberg or Delta for our lakehouse, medallion bronze/silver/gold layers, Databricks Unity Catalog, Delta Sharing, Apache Paimon or multi-engine catalogs (Polaris, Glue). Produces layer design, catalog and access model and format commitment. Not for single-table operations (use data-data-lake).

How do I install the Data Data Lakehouse skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill data-data-lakehouse. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Data Data Lakehouse popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Data Data Strategy

45

j4flmao/agent-skills

Use when the user asks about data strategy, data vision, data maturity assessment, data operating model (centralized, federated, hybrid), data culture or data literacy. Produces a maturity assessment, strategic pillars and a governance roadmap. Not for data mesh implementation (use data-data-mesh) or governance policy (use enterprise-data-governance).

AI, LLMs & Agents

AI Multi Agent Systems

45

j4flmao/agent-skills

Use when the user asks about a multi-agent system in LangGraph, AutoGen, CrewAI or OpenAI Agents SDK handoffs, shared blackboard state, A2A, checkpointing or human approval in an agent graph. Produces a runtime design: typed state, nodes, routing, durable checkpointer, interrupts, budgets and tracing. Not for choosing the topology (use multi-agent-topology).

AI, LLMs & Agents

Data Data Virtualization

45

j4flmao/agent-skills

Use when the user asks about Trino, Presto, Starburst, Dremio, query federation, cross-source joins or connector pushdown. Produces federation architecture, connector config and pushdown and join tuning. Not for warehouse modeling (use data-data-warehouse) or lake table formats (use data-data-lake).

AI, LLMs & Agents

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.