duplicate-record-review
Skill9 starsChanged 5 months agoMITView on GitHub
Identifies likely duplicate profiles or companies using available record evidence. Use when the user provides a list and wants duplicate groups, match confidence, and merge recommendations. Describe records as likely duplicates unless there is an exact deterministic match.
In this repository23 other files it gives its agents.
- account-prioritizationSkill
- b2b-lead-qualificationSkill
- candidate-qualificationSkill
- company-data-normalizationSkill
- company-researchSkill
- company-research-workflow-plannerSkill
- company-segmentationSkill
- competitor-researchSkill
- directory-research-plannerSkill
- job-title-normalizationSkill
- lead-list-analysisSkill
- lead-list-segmentationSkill
- lead-research-workflow-plannerSkill
- market-researchSkill
- outreach-brief-generatorSkill
- partner-qualificationSkill
- persona-classificationSkill
- person-researchSkill
- prospect-list-cleanupSkill
- recruiting-sourcing-plannerSkill
- research-gap-analysisSkill
- supplier-qualificationSkill
- territory-segmentationSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 50
Never auto-merge; recommend and flag for review.
- Distinctive: line 52
Prefer the most complete record as the survivor.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Duplicate Record Review
Purpose
Identify likely duplicate profiles or companies using available record evidence.
When to use this skill
- De-duplicating a merged or re-scraped list
- Catching the same company under different names
- Preventing double outreach to one contact
- Producing a reviewable merge plan
When not to use this skill
- The records share no comparable identifiers
- You need an irreversible automatic merge (always review)
- The list is already known to be unique
Required inputs
- A list of company or profile records
Optional inputs
- Match keys to prioritize (domain, email)
- A confidence threshold
- Fields that must match exactly
Rules
- Describe matches as likely unless an exact deterministic key matches.
- Report match confidence and the evidence behind it.
- Never auto-merge; recommend and flag for review.
- List conflicting fields explicitly.
- Prefer the most complete record as the survivor.
Process
- Compare records on available keys.
- Group likely duplicates.
- Assess confidence and list matching/conflicting fields.
- Recommend a survivor and merges.
- Set manual-review status.
Output format
Return one record per duplicate group with the following fields:
- duplicate_group
- match_confidence
- matching_fields
- conflicting_fields
- merge_recommendation
- manual_review_status
Validation
- Confirm only exact key matches are called certain.
- Confirm conflicts are listed for each group.
- Confirm no merge is performed automatically.
Limitations
- Without unique keys, matches are probabilistic.
- Distinct entities can share names; review before merging.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

