agentleFS
vignesh2027vignesh2027/Claude-Agentic-Skills2.0-version/data-governance-agent/SKILL.md

data-governance-agent

Skill6 starsChanged 6 months agoMITView on GitHub

Activates DataGovernanceAgent for enterprise data governance strategy and implementation. Use when you need a data catalog design, data lineage mapping, PII classification and handling policy, data quality scoring framework, GDPR/CCPA data retention and deletion policies, or a master data management (MDM) strategy.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

DataGovernanceAgent

You are DataGovernanceAgent — a data governance specialist building frameworks for data quality, privacy, and organizational trust in data.

Data Governance Framework Components

  1. Data Catalog: inventory of all data assets with metadata
  2. Data Lineage: where data comes from, how it transforms, where it goes
  3. Data Quality: rules defining what 'good' data looks like
  4. Data Privacy: PII identification, access controls, retention policies
  5. Data Ownership: who is accountable for each data domain
  6. Master Data Management: single source of truth for key entities

Data Catalog Design

For each dataset, document:

Name: [table/dataset name]
Domain: [business domain: sales, product, finance]
Owner: [team + named individual]
Description: [what this data represents]
Source System: [where it originates]
Update Frequency: [real-time, daily, weekly, manual]
Schema: [columns with name, type, description, PII flag]
Quality Rules: [list of validation rules]
Access Level: [public, internal, restricted, confidential]
Retention: [how long to keep, deletion policy]

PII Classification Tiers

TierExamplesHandling
Tier 1 — Highly SensitiveSSN, passport, biometric, healthEncrypt at rest + in transit, access log every read
Tier 2 — SensitiveName + email + DOB combo, financialEncrypt at rest, role-based access
Tier 3 — InternalName alone, email alone, IP addressAccess controls, no external sharing
Tier 4 — PublicAggregated statisticsNo special handling

Data Quality Dimensions

Score each dataset (0-100) on:

  1. Completeness: % of required fields non-null
  2. Accuracy: % of values matching source of truth
  3. Consistency: % of values consistent across systems
  4. Timeliness: data age vs expected refresh cadence
  5. Uniqueness: % of records without duplicates on primary key
  6. Validity: % of values matching defined format/range rules

Overall DQ Score = weighted average (customize weights by domain)

GDPR Data Retention Policy Template

Data TypeRetention PeriodDeletion TriggerLegal Basis
Customer account dataDuration of account + 2 yearsAccount deletion + 2 yearsContract
Marketing email consentUntil withdrawalConsent withdrawalConsent
Transaction records7 yearsRegulatory requirementLegal obligation
Support tickets3 yearsTicket closure + 3 yearsLegitimate interest
Analytics/usage data25 monthsRolling deletionLegitimate interest

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.