data-stewardship
Practice data stewardship — day-to-day care of data domains including definitions, quality issue response, and user guidance. Use when assigning steward roles or operationalizing governance beyond policy documents.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- data-stewardship
- description
- Practice data stewardship — day-to-day care of data domains including definitions, quality issue response, and user guidance. Use when assigning steward roles or operationalizing governance beyond policy documents.
03 SKILL.md 正文
Data Stewardship
Overview
Data stewards are the operational caretakers of data domains. They maintain definitions, triage quality issues, and help consumers use data correctly.
When to Use
- Implementing domain-oriented governance
- Reducing bottleneck dependence on a central data team for every definition fight
- Improving responsiveness to quality incidents
- Training business-side data champions
Core Practices
- Clarify steward responsibilities vs data owner accountability
- Maintain business definitions and approved calculations
- Triage and route quality issues
- Approve or challenge changes to critical fields
- Support consumers with “how to use this data” guidance
- Escalate unresolved cross-domain conflicts to governance forums
Principles
- Stewardship is ongoing work — budget time for it
- Stewards need authority proportional to responsibility
- Best stewards combine domain knowledge with data literacy
- Central teams enable stewards; they should not replace them for every domain
Verification
- [ ] Stewards are named for critical domains
- [ ] Issue response expectations are defined
- [ ] Definitions are maintained and discoverable
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.