mcpField
D
data-governance

data-governance

github.com/gtmagentsData & databases42892 installsUpdated 30w ago
Repository

About data-governance

data-governance is a data governance skill for automation initiatives involving cross-system sharing, consent, and data quality. It provides a framework and templates covering data contracts, identity resolution, monitoring, and change management.

Key features

  1. 01Define data fields, events, and owners
  2. 02Track consent, compliance, and audit records
  3. 03Align identities across systems
  4. 04Monitor data latency and schema changes
  5. 05Plan versioning, rollback, and communication

Use cases

  1. 01Design cross-system data-sharing journeys
  2. 02Audit consent logic across email, SMS, and in-app channels
  3. 03Investigate data quality issues affecting automation

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill data-governance

After installing, type/data-governancein Claude Code to confirm it loaded.

Details

From the project README

Automation Data Governance Skill

When to Use

  • Launching new journeys requiring cross-system data sharing.
  • Auditing consent/suppression logic across email/SMS/in-app.
  • Investigating data quality incidents impacting automation.

Framework

  1. Data Contracts – document required fields/events, owners, freshness SLAs, fallback behavior.
  2. Consent & Compliance – track opt-in types, regional consent, TTL, audit trails.
  3. Identity Resolution – ensure consistent IDs across product, CRM, MAP, CDP.
  4. Monitoring – dashboards/alerts for data latency, schema changes, null spikes.
  5. Change Management – versioning, rollback, and communication paths.

Templates

  • Data requirements matrix (journey → fields/events → source → owner → SLA).
  • Consent policy doc (channel, region, legal basis, suppression rules).
  • Incident log + RCA template.

Tips

  • Set automated kill switches when critical fields are stale or missing.
  • Collaborate with security/legal on retention + privacy impact assessments.
  • Align governance cadences with quarterly automation retros.

Comments

Markdown supported