Sales & CRM·v2.12.0

Podium Contact Dedup Agent Skill

Deduplicate Podium contacts in production and survive the data-quality failures —.

Context cost
20.4k tokensestimated from the bundle, loaded when it triggers
Bundle
11 files · 115.7 kB4 scripts among them — read before you run
Licence
MITthe author’s own terms
Last change
—v2.12.0
Servers it uses
Noneruns standalone

What it does

Deduplicate Podium contacts in production and survive the data-quality failures —

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

contact-dedupdata-qualitye164-normalizationmarketingmerge-orchestrationopt-out-preservationpodium
Filed under

Sales & CRM

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md19.2 kB · preview
--- name: podium-contact-dedup allowed-tools: Read, Write, Edit, Bash(curl:*), Bash(jq:*), Bash(python3:*), Bash(sqlite3:*), Grep version: 2.12.0 license: MIT author: Jeremy Longshore <jeremy@intentsolutions.io> compatibility: Designed for Claude Code tags: - podium - contact-dedup - e164-normalization - data-quality - opt-out-preservation - merge-orchestration ---
27# Podium Contact Dedup
28
29## Overview
30
31Deduplicate Podium contacts in production and operate the dedup pipeline at scale. This is not a one-shot cleanup script — it is the data-quality layer your integration runs continuously to keep the contact corpus sane while messages, calls, webchats, and reviews keep mutating it. Run it once and Sydney's "0412 345 678" walk-in stops creating a fifth contact next to the four that already exist as +61 412 345 678, (04) 1234-5678, +61412345678, and 0412345678.
32
33The six production failures this skill prevents:
34
351. **Phone format inconsistency** — +61 412 345 678, 0412 345 678, (04) 1234-5678, +61412345678 are all the same phone but produce four contacts. Operators paste numbers from a CRM, a phone screen, a written form, and a stored fragment; Podium dedups on exact string match, so all four survive and the next caller appears as a fifth.
362. **Merge API ordering loses fields** — Podium's merge endpoint takes a primary and a duplicate; whichever you pick as primary keeps its own fields, the other's fields are discarded. Pick the wrong record (newer but emptier) as primary and the older, richer record's name, tags, and conversation links vanish silently.
373. **Opt-out flag lost on merge** — duplicate had marketing_opt_out=true, primary had marketing_opt_out=false; naive merge keeps primary's flag and re-enables marketing on a person who explicitly opted out. This is a compliance incident (TCPA, GDPR Article 21, ACMA Spam Act) and a trust incident — the customer opted out, you marketed at them anyway.
384. **Soft-delete vs hard-delete semantic confusion** — Podium's DELETE /contacts/{uid} is reversible; the record is hidden, not destroyed. Treat it as terminal and you ship a "contact reappeared after we deleted them" support ticket every time an admin restores a contact via the UI. Hard-delete (purge) is a separate, irreversible endpoint with different scopes.
395. **Duplicate detection across locations** — same phone calls Sydney AND Burleigh Heads, two contacts created (one per location), per-location dedup misses it entirely. Cross-location dedup needs a separate routine keyed by phone_natural_key across the union of contacts in every location_uid, not just within one.
406. **Merge conflicts on simultaneous edits** — two operators (or one operator + one automated job) merge overlapping clusters at the same time; the second merge's primary may have already been merged into another record, the API silently merges into a now-stale target, and one operator's intent is dropped without surfacing the conflict.
41
42## Prerequisites
43
44- Python 3.10+ with the phonenumbers library (pip install phonenumbers)
45- A working podium-auth integration (this skill calls Podium with an authenticated client)
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md2,495 words
Files11
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈310
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
20,040
on trigger
The instruction body and 10 supporting files, read only when the skill fires.
10.2%
of a 200k window
Ten skills this size would not fit in the window together.
050k100k150k200k context window

20.4k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It asks the agent to write files, using whatever file access your client already has. Whether it reaches the network is not declared.

What it asks for
Writes filesyes
Network accessnot declared

Read from the allowed-tools line of this skill’s own SKILL.md. It also asks for Bash, which could do either, so what is not named there is not ruled out. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

11 files, 115.7 kB on disk. Mostly text — the instructions the model reads — with 4 scripts in it that your client would run only if the instructions tell it to.

  • SKILL.md19.2 kB
  • ARD.md17.8 kB
  • PRD.md14.5 kB
  • config/settings.yaml4.8 kB
  • references/errors.md8.2 kB
  • references/examples.md7.9 kB
  • references/implementation.md9.0 kB
  • scripts/cross_location_dedup.py6.3 kB
  • scripts/find_duplicates.py10.2 kB
  • scripts/merge_contacts.py14.9 kB
  • scripts/phone_normalize.py2.9 kB
What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 4 scripts beside the text, so the bundle is 11 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Podium Contact Dedup · 20.4k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/podium-contact-dedup/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/podium-contact-dedup" ] && { [ ! -e .claude/skills/podium-contact-dedup ] || { mv .claude/skills/podium-contact-dedup "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/podium-contact-dedup" .claude/skills/ && echo "Installed .claude/skills/podium-contact-dedup"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add jeremylongshore/podium-contact-dedup

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/podium-contact-dedup/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/podium-contact-dedup/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/podium-contact-dedup" ] && { [ ! -e ~/.claude/skills/podium-contact-dedup ] || { mv ~/.claude/skills/podium-contact-dedup "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/podium-contact-dedup" ~/.claude/skills/ && echo "Installed ~/.claude/skills/podium-contact-dedup" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/podium-contact-dedup/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Version2.12.0
Publishedno release date on file
PriceFree
Referencejeremylongshore/podium-contact-dedup

Versions

v2.12.0 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v2.12.0
  • No earlier releases have been published to the marketplace.
Pinning

The install command always fetches the release that is current the day you run it — v2.12.0 today — and cannot ask for an earlier one. The copy on your disk does not change until you run it again.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill