agentleFS
joaoguirunasjoaoguirunas/team-os/.claude/skills/data-lake-platform/SKILL.md

data-lake-platform

Skill6 starsChanged 2 days agoMITView on GitHub

Padrões de data lake e lakehouse — ingestão, CDC, Iceberg/Delta/Hudi, Trino/DuckDB, orquestração e governança, self-hosted ou em nuvem. Use ao desenhar ou operar uma plataforma de dados.

  • Installs packages

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add governance, lineage, data quality, and cost controls

    line 21
  2. Very specific:

    Add governance, lineage, and quality gates: references/governance-catalog.md (use assets/cross-platform/template-data-quality-governance.md …

    line 47
  3. Distinctive:

    Add quality gates (freshness, volume, schema, distribution) per tier

    line 79
  4. Distinctive:

    Treat access control and audit logging as first-class requirements

    line 81
  5. Distinctive:

    Use web search/web fetch to verify current external facts, versions, pricing, deadlines, regulations, or platform behavior before final …

    line 131
  6. Distinctive:

    Prefer primary sources; report source links and dates for volatile information.

    line 132
  7. Distinctive:

    If web access is unavailable, state the limitation and mark guidance as unverified.

    line 133

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Data Lake Platform

Build and operate production data lakes and lakehouses: ingest, transform, store in open formats, and serve analytics reliably.

When to Use

  • Design data lake/lakehouse architecture
  • Set up ingestion pipelines (batch, incremental, CDC)
  • Build SQL transformation layers (SQLMesh, dbt)
  • Choose table formats and catalogs (Iceberg, Delta, Hudi)
  • Deploy query/serving engines (Trino, ClickHouse, DuckDB)
  • Implement streaming pipelines (Kafka, Flink)
  • Set up orchestration (Dagster, Airflow, Prefect)
  • Add governance, lineage, data quality, and cost controls

Triage Questions

  1. Batch, streaming, or hybrid? What is the freshness SLO?
  2. Append-only vs upserts/deletes (CDC)? Is time travel required?
  3. Primary query pattern: BI dashboards (high concurrency), ad-hoc joins, embedded analytics?
  4. PII/compliance: row/column-level access, retention, audit logging?
  5. Platform constraints: self-hosted vs cloud, preferred engines, team strengths?

Default Baseline (Good Starting Point)

  • Storage: object storage + open table format (usually Iceberg)
  • Catalog: REST/Hive/Glue/Nessie/Unity (match your platform)
  • Transforms: SQLMesh or dbt (pick one and standardize)
  • Lake query: Trino (or Spark for heavy compute/ML workloads)
  • Serving (optional): ClickHouse/StarRocks/Doris for low-latency BI
  • Governance: DataHub/OpenMetadata + OpenLineage
  • Orchestration: Dagster/Airflow/Prefect

Workflow

  1. Pick table format + catalog: references/storage-formats.md (use assets/cross-platform/template-schema-evolution.md and assets/cross-platform/template-partitioning-strategy.md)
  2. Design ingestion (batch/incremental/CDC): references/ingestion-patterns.md (use assets/cross-platform/template-ingestion-governance-checklist.md and assets/cross-platform/template-incremental-loading.md)
  3. Design transformations (bronze/silver/gold or data products): references/transformation-patterns.md (use assets/cross-platform/template-data-pipeline.md)
  4. Choose lake query vs serving engines: references/query-engine-patterns.md
  5. Add governance, lineage, and quality gates: references/governance-catalog.md (use assets/cross-platform/template-data-quality-governance.md and assets/cross-platform/template-data-quality.md)
  6. Plan operations + cost controls: references/operational-playbook.md and references/cost-optimization.md (use assets/cross-platform/template-data-quality-backfill-runbook.md and assets/cross-platform/template-cost-optimization.md)

Architecture Patterns

  • Medallion (bronze/silver/gold): references/architecture-patterns.md
  • Data mesh (domain-owned data products): references/architecture-patterns.md
  • Streaming-first (Kappa): references/streaming-patterns.md

Quick Start

dlt + ClickHouse

pip install "dlt[clickhouse]"
dlt init rest_api clickhouse
python pipeline.py

SQLMesh + DuckDB

pip install sqlmesh
sqlmesh init duckdb
sqlmesh plan && sqlmesh run

Reliability and Safety

Do

  • Define data contracts and owners up front
  • Add quality gates (freshness, volume, schema, distribution) per tier
  • Make every pipeline idempotent and re-runnable (backfills are normal)
  • Treat access control and audit logging as first-class requirements

Avoid

  • Skipping validation to "move fast"
  • Storing PII without access controls
  • Pipelines that can't be re-run safely
  • Manual schema changes without version control

Resources

ResourcePurpose
references/architecture-patterns.mdMedallion, data mesh
references/ingestion-patterns.mddlt vs Airbyte, CDC
references/transformation-patterns.mdSQLMesh vs dbt
references/storage-formats.mdIceberg vs Delta
references/query-engine-patterns.mdClickHouse, DuckDB
references/streaming-patterns.mdKafka, Flink
references/orchestration-patterns.mdDagster, Airflow
references/bi-visualization-patterns.mdMetabase, Superset
references/cost-optimization.mdCost levers and maintenance
references/operational-playbook.mdMonitoring and incident response
references/governance-catalog.mdCatalog, lineage, access control
references/data-mesh-patterns.mdDomain ownership, data products, federated governance
references/data-quality-patterns.mdQuality gates, validation frameworks, SLOs, anomaly detection
references/security-access-patterns.mdRow/column security, encryption, audit logging, compliance

Templates

TemplatePurpose
assets/cross-platform/template-medallion-architecture.mdBaseline bronze/silver/gold plan
assets/cross-platform/template-data-pipeline.mdEnd-to-end pipeline skeleton
assets/cross-platform/template-ingestion-governance-checklist.mdSource onboarding checklist
assets/cross-platform/template-incremental-loading.mdIncremental + backfill plan
assets/cross-platform/template-schema-evolution.mdSchema change rules
assets/cross-platform/template-cost-optimization.mdCost control checklist
assets/cross-platform/template-data-quality-governance.mdQuality contracts + SLOs
assets/cross-platform/template-data-quality-backfill-runbook.mdBackfill incident/runbook

Related Skills

SkillPurpose
ai-ml-data-scienceFeature engineering
data-sql-optimizationOLTP optimization

Fact-Checking

  • Use web search/web fetch to verify current external facts, versions, pricing, deadlines, regulations, or platform behavior before final answers.
  • Prefer primary sources; report source links and dates for volatile information.
  • If web access is unavailable, state the limitation and mark guidance as unverified.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.