delta-lake-and-medallion-architecture — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited delta-lake-and-medallion-architecture (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill when a Delta Lake-based lakehouse needs more than generic table-format guidance. It helps agents design medallion-style layers, transactional update behavior, CDC merges, and publish-safe transformation paths for Delta-centric platforms.
bronze, silver, and gold layeringDelta Lake merges, upserts, or deletesDatabricks-centered batch and streaming lakehouse flowsDo not use medallion terminology as decoration if the layers do not carry distinct responsibilities.
Typical pattern:
Capture:
Raw survival and publish trust need different operating rules.
Checkpoints, merges, and small-file behavior must support recovery and maintenance.
Include:
| Rationalization | Reality |
|---|---|
| "Bronze, silver, and gold are enough architecture by themselves." | Layer names without contracts and rules create confusion, not design clarity. |
| "We can merge everything directly into gold." | Business-facing layers need stronger validation and stability than raw ingestion paths. |
| "Delta transactions solve every operational problem." | You still need thoughtful layering, maintenance, and replay design. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.