OpenSkillIndex← back to search
claude-codedata

Claude-skill-registry identity-resolution

Use to match accounts, contacts, and opportunities across enrichment

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/identity-resolution" ~/.claude/skills/majiayu000-claude-skill-registry-identity-resolution && rm -rf "$T"
manifest: skills/data/identity-resolution/SKILL.md
tags
#data-matching#identity-management#data-governance#data-normalization#crm#cdp
source content

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.