smithery.ai

identity-resolution

Use to match accounts, contacts, and opportunities across enrichment sources with governed rules.

First seen May 1, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,316 B
  • docs SUMMARY.md 124 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

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, accountid, email, personid).
  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.