TypingMindTypingMindThe best frontend for AI
Data Lake And Zone Architecture logo

Data Lake And Zone Architecture

Community
vaquarkhan
data-lake-and-zone-architecture

Guides agents through data lake and zone architecture design. Use when defining raw, refined, curated, or publish layers; storage organization; retention; and operational boundaries for a data lake.

Overview

Publishervaquarkhan
Repositorydata-engineering-agent-skills
Skill namedata-lake-and-zone-architecture
Stars
60
Forks
8
Bundled files
Instructions only
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • 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 Data Lake And Zone Architecture AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/data-lake-and-zone-architecture
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

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/data-lake-and-zone-architecture .claude/skills/data-lake-and-zone-architecture
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Data Lake And Zone Architecture 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 Data Lake And Zone Architecture 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 Data Lake And Zone Architecture 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.

Data Lake And Zone Architecture

Overview

Use this skill when the storage platform needs structure before pipelines scale into chaos. It helps agents design clear lake zones, dataset boundaries, ownership, lifecycle rules, and publish-safe storage conventions.

When to Use

  • designing a new data lake
  • reorganizing raw, staging, refined, or curated zones
  • defining object storage layout and lifecycle rules
  • separating landing, transformation, and publish responsibilities
  • reducing data swamp behavior in shared lake storage

Do not use this to justify creating extra layers with no operational purpose.

Workflow

  1. Define the lake purpose and consumers. Clarify:

    • source landing needs
    • internal producer teams
    • publish consumers
    • compliance and retention expectations

  2. Define the zone model intentionally. Typical zones include:

    • raw or landing
    • standardized or staging
    • refined or modeled
    • publish or serving

  3. Assign responsibilities to each zone. Decide:

    • who writes to it
    • who reads from it
    • what quality guarantees exist
    • whether mutation is allowed

  4. Design storage conventions. Include:

    • path or catalog naming
    • partition strategy
    • retention lifecycle
    • file-size expectations
    • ownership tags and metadata

  5. Keep publish rules separate from lake convenience. Not every dataset in the lake is ready for shared consumption.

Cross-Cloud Architecture

Use references/cloud-data-engineering-architecture-patterns.md when the task is not only zone design, but choosing the overall cloud architecture pattern across lake, warehouse, lakehouse, streaming, and hybrid shapes.

Common Rationalizations

RationalizationReality
"We can dump everything into one bucket or container and organize later."That is how data lakes turn into data swamps.
"More zones always means better governance."Extra layers without distinct purpose add complexity and slow teams down.
"If the file exists in the lake, it is available for analytics."Raw landing data rarely has the quality or contract guarantees needed for shared use.

Red Flags

  • zone meanings overlap or are undocumented
  • ownership is unclear at the dataset or zone level
  • publish and landing data are mixed together
  • retention, cleanup, or lifecycle policy is absent

Verification

  • The zone model has clear purposes and boundaries
  • Ownership, read/write expectations, and quality guarantees are explicit
  • Storage conventions and lifecycle rules are documented
  • Shared publish datasets are separated from raw landing data

Frequently asked questions

What does the Data Lake And Zone Architecture AI skill do?

Guides agents through data lake and zone architecture design. Use when defining raw, refined, curated, or publish layers; storage organization; retention; and operational boundaries for a data lake.

Why use Data Lake And Zone Architecture on TypingMind?

Because you install it once and use it with any model. Data Lake And Zone Architecture 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 Data Lake And Zone Architecture in TypingMind?

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

Which AI models can use Data Lake And Zone Architecture?

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 Data Lake And Zone Architecture?

As many as you like. As long as a model supports skills, you can use Data Lake And Zone Architecture with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Data Lake And Zone Architecture 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.

Related AI Skills

View all
NousResearch logo

Huggingface Hub

NousResearch
OrganizationPopular

HuggingFace hf CLI: search/download/upload models, datasets.

53.5K
250.4K
Instructions
View
NousResearch logo

Pytorch Lightning

NousResearch
OrganizationPopular

Clean training loops with built-in distributed support.

53.5K
250.4K
3 files
View
microsoft logo

Troubleshoot

microsoft
OrganizationPopular

Investigate unexpected behavior in the current Copilot agent session by analyzing its event log. Use when the user asks why something happened, why a request was slow, why a tool was or was not used,…

42.7K
192.7K
Instructions
View
anthropics logo

Pdf

anthropics
OrganizationPopular

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart,…

21.8K
184K
10 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇