crm-duplicates

Detect and merge duplicate CRM records across contacts and companies.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Cimminelli1982/crm-frontend --skill crm-duplicates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crm-duplicates
Source: https://github.com/Cimminelli1982/crm-frontend/tree/main/docs/openclaw-skills/crm-duplicates
Command: npx skills add https://github.com/Cimminelli1982/crm-frontend --skill crm-duplicates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Duplicate CRM records across contacts and companies create data fragmentation and manual reconciliation overhead, leading to wasted time and inconsistent data.

Core Features & Use Cases

  • Automated detection of duplicate contacts and companies across CRM datasets
  • Manual analysis and guided merge workflow with a hold mechanism for uncertain records
  • Clear audit trail and persistence in the contact_duplicates and company_duplicates tables

Quick Start

Trigger the duplicate scan via the backend to start identifying and resolving duplicates.

Frequently Asked Questions about crm-duplicates

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect and merge duplicate CRM contacts and companies at scale?

Detect and merge duplicate CRM records by triggering an automated scan across your contact and company datasets. The system identifies matches and provides a guided merge workflow to reconcile data fragmentation efficiently.

What is the hold-merge workflow for ambiguous duplicate CRM records?

The hold-merge workflow is a manual analysis mechanism for ambiguous duplicate CRM records. It allows you to place uncertain contact or company matches on hold instead of merging them immediately, ensuring accurate data reconciliation.

Do I need backend endpoints configured to run CRM deduplication scans?

Yes, CRM deduplication requires configuring backend endpoints. You must set the COMMAND_CENTER_BACKEND_URL and CRM_AGENT_URL environment variables to trigger scans and coordinate merging operations across your contact_duplicates and company_duplicates tables.

How does CRM deduplication persist merge audit trails and duplicate records?

CRM deduplication persists records and audit trails using dedicated database tables. The contact_duplicates and company_duplicates tables coordinate deduplication efforts and maintain a clear history of merged contacts and companies.

Can I manually analyze CRM duplicates instead of relying on automated scans?

Yes, you can manually analyze CRM duplicates alongside automated scans. The system supports manual analysis workflows, allowing you to review detected duplicate contacts and companies and execute guided merges for uncertain records.