home / skills / omer-metin / skills-for-antigravity / data-governance

data-governance skill

safe

This skill helps you implement data governance frameworks, build data catalogs, and enforce quality and compliance across metadata and lineage.

npx playbooks add skill omer-metin/skills-for-antigravity --skill data-governance

Review the files below or copy the command above to add this skill to your agents.

Files (4)

SKILL.md

1.1 KB

---
name: data-governance
description: Use when implementing data governance frameworks, building data catalogs, establishing data lineage, defining data quality rules, or setting up data stewardship programs - covers metadata management, data quality, and complianceUse when ", " mentioned. 
---

# Data Governance

## Identity



## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Overview

This skill helps teams design and implement pragmatic data governance: frameworks, data catalogs, lineage, data quality rules, metadata management, and stewardship programs. It enforces a reference-first approach so outputs stay consistent with established patterns, risk guidance, and validation rules. The goal is fast, auditable governance work that reduces compliance risk and improves trust in data.

How this skill works

When creating artifacts, the skill consults references/patterns.md to apply approved structures and templates. For diagnosing issues it uses references/sharp_edges.md to identify common failure modes and explain root causes. For reviews and final checks it runs validations against references/validations.md and reports objective pass/fail feedback and remediation steps.

When to use it

Designing or updating a data governance framework or policy set
Building or curating a data catalog and metadata model
Establishing or documenting data lineage for critical datasets
Defining and testing data quality rules and metrics
Setting up data stewardship roles, responsibilities, and operating cadence
Preparing governance artifacts for audits or compliance reviews

Best practices

Always start with references/patterns.md to standardize deliverables and minimize rework
Map governance requirements to concrete controls and validation checks from validations.md
Use sharp_edges.md during post-mortem or diagnostic tasks to prioritize high-risk fixes
Define measurable SLAs for data quality and enforce them via automated validations
Assign clear data steward owners and maintain an accessible catalog of responsibilities

Example use cases

Create a company-wide data governance framework aligned to business domains using pattern templates
Produce a searchable data catalog with standardized metadata fields and lineage diagrams
Implement data quality rules for customer records and automate daily validation checks
Diagnose repeated failures in ETL pipelines using the sharp edges guidance and produce mitigation steps
Run a governance review before an external audit and generate a validation report with remediation items

FAQ

What files does this skill rely on as the source of truth?

Creation follows references/patterns.md, diagnosis uses references/sharp_edges.md, and review/validation uses references/validations.md.

What if my request conflicts with referenced guidance?

The skill corrects the request and recommends compliant alternatives based on the referenced files, explaining the rationale and remediation steps.