Individual skill
identity-resolution
Use to match accounts, contacts, and opportunities across enrichment sources with governed rules.
plugins/data-signal-enrichment/skills/identity-resolution/SKILL.md
Source commit 78e0419f4440bcb43bc80127e174ecf5adef1753
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 438
- Repository last updated
- Apr 3, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,316 bytes
Read excerpt
# 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.
