data-medallion-architecture

Designs end-to-end medallion data pipelines from source selection to gold-layer dashboards.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/manusabbath-arch/hermes-skills --skill data-medallion-architecture-manusabbath-arch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-medallion-architecture
Source: https://github.com/manusabbath-arch/hermes-skills/tree/main/skills/data-medallion-architecture
Command: npx skills add https://github.com/manusabbath-arch/hermes-skills --skill data-medallion-architecture-manusabbath-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires deltalake, duckdb, pyarrow.

What problem does it solve? Data pipelines often grow into ad-hoc stacks where layers have no clear role, sources are chosen by habit, and dashboards drift from the tables they claim to show. This Skill provides a disciplined design method for building a medallion architecture (Bronze/Silver/Gold) where each layer has a single auditable role, the source is chosen by explicit criteria, and consumption (AI/ML/MCP/dashboards) reads the same tables the system writes. ## Core Features & Use Cases - Layer role definitions: Bronze is raw append-only audit storage, Silver handles dedup, type coercion, and explicit NULL policy, Gold answers a fixed business question as an aggregated Delta table or DuckDB query. - Source selection framework: Compare API, database, and SFTP sources on reliability, freshness, latency, quota, cost, and format before building, and record the decision. - Scenario dashboards: Turn Gold-layer queries into parameterized hypothetical scenarios rendered in dashboards via DuckDB delta_scan, measured at real production data volume. - Use Case: You ingest market data from an external API, store raw events in a Bronze Delta table, clean and dedup into Silver, aggregate edge-by-market into Gold, and serve a dashboard comparing conservative vs aggressive edge thresholds from the same parameterized query. ## Quick Start Ask the agent to design a medallion architecture for your data source, defining the Bronze, Silver, and Gold layers and a parameterized scenario dashboard on top of the Gold table.

Frequently Asked Questions about data-medallion-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a medallion architecture with Delta Lake and DuckDB?

Define three layers with single roles: Bronze stores raw append-only events, Silver dedups by primary key and coerces types with an explicit NULL policy, and Gold aggregates to answer one business question. Use deltalake for writes and DuckDB delta_scan for queries.

What is the difference between Bronze, Silver, and Gold data layers?

Bronze is the immutable raw audit layer with no cleaning or dedup. Silver is the cleaned, deduplicated, typed layer that analyses consume by default. Gold is the aggregated layer materialized to answer a specific business question or feed dashboards.

How do I choose between API, database, and SFTP as a data source?

Compare sources on explicit criteria: reliability and freshness, latency, quota, cost, availability, and format. A silent-failing external API is worse than a slow but honest local source. Record the decision in an infrastructure decision memo before building.

Can DuckDB query Delta Lake tables directly for dashboards?

Yes, DuckDB reads Delta tables in memory using delta_scan without a server. Dashboards should run the same parameterized query against the Gold table rather than a copy, so the displayed numbers never drift from the source table.

How should NULL values be handled in the Silver layer?

NULLs must be declared, never silent: bad values map to a documented sentinel such as 0.0, borderline values stay NULL. The rule is NULL is a defect to fix while 0 is a legitimately measured value, so the two are never conflated.

When is a medallion architecture not the right approach?

The layered design adds overhead that may not pay off for one-off exploratory analysis or trivial single-file datasets. It fits projects needing auditability, reprocessing from raw data, and multiple downstream consumers of the same tables.