data-governance
Establish data governance — ownership, policies, decision rights, and accountability — so data is trusted, compliant, and usable across the organization. Use when designing governance operating models, assigning data owners, or fixing chronic trust and access problems.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- data-governance
- description
- Establish data governance — ownership, policies, decision rights, and accountability — so data is trusted, compliant, and usable across the organization. Use when designing governance operating models, assigning data owners, or fixing chronic trust and access problems.
03 SKILL.md 正文
Data Governance
Overview
Data governance is the system of decision rights and accountabilities for data assets. It answers who decides standards, who owns quality, and how conflicts are resolved.
When to Use
- Standing up or maturing a governance program
- Assigning data domain owners and stewards
- Resolving conflicting metrics or access rules
- Aligning data use with privacy and regulatory obligations
Core Practices
- Define governance scope by data domains (customer, product, finance, etc.)
- Assign owners (accountability) and stewards (day-to-day care)
- Set policies for quality, access, retention, and acceptable use
- Create decision forums for standards and exceptions
- Tie governance to real pain (conflicting numbers, audit findings, blocked projects)
- Measure adoption: owned domains, certified datasets, issue closure rates
Principles
- Governance without business ownership becomes bureaucracy
- Start with critical domains, not a universal catalog fantasy
- Policies must be enforceable in tools and processes
- Trust is the product; paperwork is only a means
Verification
- [ ] Critical domains have named owners
- [ ] Decision rights for standards are clear
- [ ] Policies connect to operational controls
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.