What problem does it solve?
It resolves governance gaps that can cause sensitive data exposure, broken lineage traceability, and non-compliant metadata, access control, and retention handling across a data engineering lifecycle.
Core Features & Use Cases
- Governance and security decisioning for sensitive data: Reviews PII classification, masking/tokenization/encryption choices, and privacy implications before data is served or released.
- Operational lineage and metadata stewardship: Ensures column-level lineage and catalog stewardship are usable for incidents and schema changes, not just documentation.
- Access control enforcement: Validates RBAC/RLS and related audit/retention obligations so serving behavior aligns with policy and downstream risk.
Use case: Before publishing a dataset that includes PII, review whether sensitive fields have correct handling rules (masking/tokenization/access), whether column-level lineage exists for incident traceability, and whether audit and retention requirements are documented and enforceable.
Quick Start
Use this skill to review the planned serving or release of a data product for governance, privacy, access control, lineage, and retention compliance.