Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
DeepSeek
Muse+22 moreClaude CodeCursorCodex CLIDeepSeekMuse
Dots
Manus
Grok
Grok Bot+18 agentsCRM Duplicate Killer — Find & Merge Duplicate Customer
Resolve duplicate identity with contradiction checks, survivorship and safe auditable merge previews.
$9.99
CRM Duplicate Killer — Find & Merge Duplicate Customer
Example session with this skill installed
Illustrative scenario: Prepare a merge review from supplied customer records, with no writes. C1 and C2 have the same verified external customer ID X123 and email alex@example.test. C1 has a phone from a verified billing source; C2 has a different phone from an undated import. C1 has an open support ticket; C2 has an open opportunity and marketing suppression. C3 shares the email but has customer ID X999 and is a separate branch account. No global survivorship policy or backup supplied. Propose dispositions, field decisions and safeguards.
- Read your context and instructions
- Compiled the crm duplicate killer
Duplicate review
| Records | Identity evidence | Contradiction / context | Disposition |
|---|---|---|---|
| C1/C2 | Same supplied verified external ID X123 and email | Conflicting phone; connected ticket, opportunity and suppression | Strong candidate; reviewed merge plan only, pending source and policy validation |
| C1/C3 or C2/C3 | Shared email | Distinct customer ID X999 and supplied separate branch context | Do not merge on email similarity; preserve separate entity |
Proposed golden record
Proposed survivor: C1, subject to authorized policy and system validation. Retain stable source IDs and a C2 cross-reference. For phone, prefer the verified billing source over an undated import only after confirming source authority and recency; keep the alternate value and provenance in audit history where permitted. Do not invent a global rule from this single case.
Association and consent plan
Preserve C1’s support ticket and C2’s opportunity with their original identities/history. Confirm platform behavior for moving associations and avoid duplicating or losing activities. Preserve marketing suppression; a merge must not grant consent or remove a restriction. Confirm suppression scope and policy with the responsible owner. C3’s branch relationships remain separate.
Required review and dry run
Verify ID uniqueness semantics across systems and object types, compare contradictory fields and inspect the full cluster. Obtain backup/snapshot, approved survivorship policy, affected counts, rule version, sample and high-value/customer review, consent review and rollback plan. Run a preview of the proposed field and association changes before authorization.
Reconciliation checks
After an authorized merge, verify record counts, retained external IDs, opportunity and ticket links, ownership, suppression, history and downstream integrations. Monitor for false merges and repeated duplicate creation. No post-merge result is reported because no action occurred.
Decision state
C1/C2: review required; neither approved nor executed. C3: keep separate under supplied evidence. Backup, reviewer, execution permission and rollback reference are missing. No records were merged or deleted; no private enrichment or identity inference was performed.
Connects securely to your tools. The creator never sees your data.
About this skill
CRM Duplicate Killer specializes in customer identity resolution and duplicate-remediation planning. It examines contact, company, lead and explicitly scoped commercial records, determines whether they represent the same real-world entity, and prepares a reviewed golden-record and survivorship plan.
The workflow profiles identity keys, generates candidates, checks exact and fuzzy evidence, tests contradictions, resolves clusters and preserves associations, activities, consent, ownership and history. Shared mailboxes, branches, subsidiaries and moved-company cases are treated as potential false positives rather than automatic duplicates.
Outputs include confidence classifications, merge previews, field-level source decisions, reviewer requirements, rollback references and reconciliation checks. Live CRM actions depend on actual authorization and tool capability. Bulk merges/deletes require backup, snapshot, dry run, versioned rules, affected counts, reviews, rollback and validation. Similarity is never presented as certainty.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Data & Databases.
Similarity does not establish identity. Shared mailboxes/phones, branch or subsidiary relationships and source conflicts require review. Platform merge behavior and authoritative policies must be verified. No legal certification, invented identity or unreviewed destructive action; post-action success requires evidence.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Permissions
File Scopes
Read authorized CRM and source records using stable IDs and minimum personal data. Write reviewed comparison and merge-preview reports to an agreed destination. Bulk merge/delete requires authorized tools, backup/snapshot, dry run, rule version, affected counts, reviews, rollback and reconciliation. Never weaken consent or suppression.