mcpField
I
identity-resolution

identity-resolution

github.com/gtmagentsData & databases42871 installsUpdated 30w ago
Repository

About identity-resolution

A playbook skill for resolving identities across provider outputs before syncing data to a CRM or CDP. It defines matching, conflict handling, governance, and audit practices for linking account and contact records.

Key features

  1. 01Primary and secondary key hierarchy
  2. 02Deterministic and fuzzy matching rules
  3. 03Conflict and merge policies
  4. 04Exception queues and ownership
  5. 05Lineage, snapshots, and rollback steps

Use cases

  1. 01Normalizing data before CRM or CDP sync
  2. 02Linking intent, enrichment, and telemetry records
  3. 03Diagnosing duplicate or conflicting records

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill identity-resolution

After installing, type/identity-resolutionin Claude Code to confirm it loaded.

Details

From the project README

Identity Resolution Playbook Skill

When to Use

  • Normalizing provider outputs before syncing to CRM/CDP.
  • Tying intent, enrichment, and product telemetry to the same account/contact IDs.
  • Diagnosing duplicate or conflicting records in downstream systems.

Framework

  1. Key Hierarchy – define primary/secondary keys (domain, account_id, email, person_id).
  2. Matching Logic – configure deterministic and fuzzy rules, tie-breakers, and confidence scoring.
  3. Conflict Handling – specify precedence rules, merge policies, and exception queues.
  4. Governance – document owners, change control, and monitoring cadence.
  5. Audit Trail – capture lineage metadata, before/after snapshots, and rollback steps.

Templates

  • Matching rule matrix (field, rule type, weight, confidence threshold).
  • Exception queue workflow with owners + SLAs.
  • Audit workbook for sampling matches vs source-of-truth.

Tips

  • Start with deterministic keys (domain, CRM ID) before fuzzy logic to reduce noise.
  • Version rules so downstream teams know when behavior changes.
  • Pair with signal-taxonomy to keep IDs aligned with schema updates.

Comments

Markdown supported