Help us improve
Share bugs, ideas, or general feedback.
From data-architecture
Establish data ownership, quality standards, compliance policies, and metadata management. Build organizational data practices. Use when defining data strategy or improving data quality and compliance.
npx claudepluginhub sethdford/claude-skills --plugin architect-data-architectureHow this skill is triggered — by the user, by Claude, or both
Slash command
/data-architecture:data-governanceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Establish organizational data management practices, ownership, quality standards, and compliance policies.
Designs data governance policies covering ownership, classification, access control, lifecycle management, and regulatory compliance (GDPR, NIST).
Governs SAP Datasphere catalogs: enriches metadata, manages glossaries, defines KPIs, controls tags, analyzes lineage impacts. Improves discoverability and self-service analytics.
Provides database security guidance: TDE encryption at rest, TLS in transit, RBAC/ABAC access control, SQL injection prevention. SQL examples for PostgreSQL, SQL Server, Oracle.
Share bugs, ideas, or general feedback.
Establish organizational data management practices, ownership, quality standards, and compliance policies.
You are building data governance practices. Define who owns data, how quality is enforced, compliance requirements, and metadata standards. Read organizational context, regulatory requirements, and existing data practices.
Based on enterprise data management practices:
Define Data Owner Roles: Who is accountable for each data domain? Product for customer data, Finance for transaction data. Owners define quality standards and usage policies.
Establish Metadata Catalog: Inventory all data assets: databases, tables, APIs, data lakes. For each: owner, description, lineage (source), refresh frequency, classification (public/confidential/PII).
Set Quality Standards: For critical datasets, define SLAs: freshness (how recent), completeness (% non-null), accuracy (validated against source), consistency (matches across systems).
Build Data Dictionary: Business definitions of key entities and attributes. Customer means "active subscriber". Amount means "invoice total in USD". Shared vocabulary reduces confusion.
Implement Access Control: Who can access what data? Implement principle of least privilege. GDPR: individuals can request deletion; log access to sensitive data.