data-lake-and-zone-architecture

data-lake-and-zone-architecture is a skill for Claude Code, Codex from vaquarkhan/data-engineering-agent-skills. It costs 45 tokens per session (589 once invoked), scanned A, original, MIT.

A planning guide for organizing a data lake, which is shared storage for large collections of data. It helps define zones such as raw, refined, curated, and publish layers, along with ownership, storage layout, quality rules, and retention.

In plain words
What is it for?
Use it to design a new data lake, reorganize existing storage zones, set naming and partition rules, and separate data landing, transformation, and publishing responsibilities.
Why use it?
It prevents shared data storage from becoming a disorganized data swamp. Clear boundaries make it easier to know where data belongs and what users can rely on.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to design a new data lake, reorganize existing storage zones, set naming and partition rules, and separate data landing, transformation, and publishing responsibilities.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vaquarkhan/data-engineering-agent-skills/data-lake-and-zone-architecture
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add vaquarkhan/data-engineering-agent-skills --skill data-lake-and-zone-architecture
Clone the repo
git clone --depth 1 https://github.com/vaquarkhan/data-engineering-agent-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for data-lake-and-zone-architecture

README.md
[![agentmods](https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/data-lake-and-zone-architecture/github.svg)](https://agentmods.dev/skills/vaquarkhan/data-engineering-agent-skills/data-lake-and-zone-architecture)
Your own site
<a href="https://agentmods.dev/skills/vaquarkhan/data-engineering-agent-skills/data-lake-and-zone-architecture"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/data-lake-and-zone-architecture/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for data-lake-and-zone-architecture

Your own site · 80×15
<a href="https://agentmods.dev/skills/vaquarkhan/data-engineering-agent-skills/data-lake-and-zone-architecture"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/data-lake-and-zone-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 589 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.00589
Opus 5 $0.00023 $0.00295
Sonnet 5 $0.00009 $0.00118
Haiku 4.5 $0.00005 $0.00059

Measured 11d ago against content hash bc631b8c98d1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

data-lake-and-zone-architecture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/data-lake-and-zone-architecture/SKILL.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

Rationalization Reality
"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.

Read the full file on GitHub · 81 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 81 lines · 45 tokens per session scan A bc631b8c98d1

Subscribe to this mod's changes

data-lake-and-zone-architecture is a skill published in the GitHub repository vaquarkhan/data-engineering-agent-skills (45 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 589 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

kafka-shadowtraffic

Generate a ShadowTraffic configuration to populate a Kafka topic with realistic synthetic data. Discovers the target topic, its key and value schemas, and the correct serializers from the live cluster via any attached Kafka MCP server, then writes a ready-to-run shadowtraffic-config.json and Docker command. Use when…

lensesio/agentic-engineering-for-apache-kafka · 134 tokens

spark-training-gotchas

Preflight and diagnose the ten known failure modes for ML training on NVIDIA DGX Spark. Use when a training run on DGX Spark fails to start, OOMs below the 128GB limit, slows down mid-run, or before any multi-hour training job on GB10.

wshobson/agents · 63 tokens

9router

Entry point for 9Router — local/remote AI gateway with OpenAI-compatible REST for chat, image, TTS, embeddings, web search, web fetch. Use when the user mentions 9Router, NINEROUTERURL, or wants AI without writing provider boilerplate. This skill covers setup + indexes capability skills; fetch the relevant capability…

decolua/9router · 84 tokens

aeon

This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard…

synthetic-sciences/openscience · 74 tokens

lookml_ingest

Map a LookML view/model/explore into ktx semantic layer sources. Covers the LookML to ktx primitive table, provenance tagging, and three worked examples (overlay, standalone from derivedtable, standalone with sqlalwayswhere). Load when the turn contains .lkml content.

Kaelio/ktx · 63 tokens

markitdown

Convert files and office documents to Markdown. Supports PDF, DOCX, PPTX, XLSX, images (with OCR), audio (with transcription), HTML, CSV, JSON, XML, ZIP, YouTube URLs, EPubs and more.

synthetic-sciences/openscience · 53 tokens