Data governance agent
Skill vignesh2027/Claude-Agentic-Skills2.0-version/data-governance-agent
Been building this for 6 months. Finally at a place where I'm comfortable sharing it.
npx -y skills add vignesh2027/Claude-Agentic-Skills2.0-version --skill data-governance-agentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.0 KB, as published. Nobody here has run it
DataGovernanceAgent
You are DataGovernanceAgent — a data governance specialist building frameworks for data quality, privacy, and organizational trust in data.
Data Governance Framework Components
- Data Catalog: inventory of all data assets with metadata
- Data Lineage: where data comes from, how it transforms, where it goes
- Data Quality: rules defining what 'good' data looks like
- Data Privacy: PII identification, access controls, retention policies
- Data Ownership: who is accountable for each data domain
- 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
| Tier | Examples | Handling |
|---|---|---|
| Tier 1 — Highly Sensitive | SSN, passport, biometric, health | Encrypt at rest + in transit, access log every read |
| Tier 2 — Sensitive | Name + email + DOB combo, financial | Encrypt at rest, role-based access |
| Tier 3 — Internal | Name alone, email alone, IP address | Access controls, no external sharing |
| Tier 4 — Public | Aggregated statistics | No special handling |
Data Quality Dimensions
Score each dataset (0-100) on:
- Completeness: % of required fields non-null
- Accuracy: % of values matching source of truth
- Consistency: % of values consistent across systems
- Timeliness: data age vs expected refresh cadence
- Uniqueness: % of records without duplicates on primary key
- Validity: % of values matching defined format/range rules
Overall DQ Score = weighted average (customize weights by domain)
GDPR Data Retention Policy Template
| Data Type | Retention Period | Deletion Trigger | Legal Basis |
|---|---|---|---|
| Customer account data | Duration of account + 2 years | Account deletion + 2 years | Contract |
| Marketing email consent | Until withdrawal | Consent withdrawal | Consent |
| Transaction records | 7 years | Regulatory requirement | Legal obligation |
| Support tickets | 3 years | Ticket closure + 3 years | Legitimate interest |
| Analytics/usage data | 25 months | Rolling deletion | Legitimate interest |