master-data-management

Design master data management architectures with matching, survivorship, and governance rules.

1|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/SSiertsema/claude-code-plugins --skill master-data-management-ssiertsema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: master-data-management
Source: https://github.com/SSiertsema/claude-code-plugins/tree/main/master-data-management/skills/master-data-management
Command: npx skills add https://github.com/SSiertsema/claude-code-plugins --skill master-data-management-ssiertsema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Master data inconsistencies across systems lead to duplicate records, conflicting values, and poor governance. This Skill helps you design a governance framework and architecture to create a trusted, unified view of core entities.

Core Features & Use Cases

  • Identify master entities (e.g., Customer, Product, Location) and determine which should be centrally managed.
  • Choose an MDM architecture (Registry, Consolidation, Coexistence, Centralized) and justify the selection.
  • Define matching, survivorship, and stewardship rules to maintain a golden record across sources.
  • Integrate with source systems and support data quality monitoring and audit trails.

Quick Start

Define master entities for your organization and specify the survival and matching rules for the golden record of each entity.

Frequently Asked Questions about master-data-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a single source of truth for inconsistent customer and product data across CRM and ERP systems?

Master data management resolves inconsistent records across CRM, ERP, and HRIS systems by applying deterministic and probabilistic matching rules to create a trusted golden record. It defines survivorship strategies and governance workflows to maintain data consistency across multiple source systems.

What is the best way to choose an MDM architecture for my organization?

The best way to choose an MDM architecture is to evaluate registry, consolidation, coexistence, and centralized patterns based on your integration needs. This Skill helps justify the selection by specifying matching rules, stewardship responsibilities, and hub-spoke integration patterns for your master data.

How do survivorship rules work when consolidating duplicate records from multiple source systems?

Survivorship rules resolve conflicting attribute values from duplicate records by determining which source system data survives into the golden record. You specify these strategies alongside deterministic and probabilistic matching rules to maintain trusted master data across your organization.

When do I need master data governance workflows for entity resolution?

You need master data governance workflows for entity resolution when managing multiple source systems like CRM, ERP, and procurement that require consistent customer, product, and location data. These workflows define stewardship responsibilities to maintain data quality and audit trails for the golden record.

How do I define matching rules for a golden record across different platforms?

You define matching rules for a golden record by specifying deterministic and probabilistic criteria to identify and link duplicate entities across platforms. This process includes mapping integration patterns like hub-spoke or coexistence to consistently consolidate core data from source systems.