agentleFS
chacosoldierchacosoldier/compabob/.claude/skills/merge-contacts/SKILL.md

merge-contacts

Skill34 starsChanged 24 days agoMITView on GitHub

Merge the user's contact exports (Google Takeout, LinkedIn export, vault People notes) into one local CRM. Use for "/merge-contacts", "build my CRM", "dedup my contacts", or when another workflow needs a clean contacts source of truth.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Find the exports: Check, in order:

    line 14
  2. Very specific:

    If none exist, point the user at the setup steps in modules/crm-merge/README.md (both exports are self-service downloads) and stop.

    line 20
  3. Very specific:

    Over-merging on a common name: if the user says distinct people got fused, lower --name-collision-threshold and re-run.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Merge Contacts

Build the user's local CRM source of truth with the crm-merge module. The module does the work; your job is to find their exports, run it with the right flags, and report what merged. Never invent data, never call an external CRM.

Steps

  1. Find the exports. Check, in order:
    • A Google Takeout zip in ~/Downloads (name contains "takeout" or "google"). The script auto-finds the newest one, but confirm it exists.
    • A LinkedIn export folder (contains Connections.csv, ideally messages.csv). Ask the user for the path if you cannot find it.
    • vault/People/ for per-person notes (optional). If none exist, point the user at the setup steps in modules/crm-merge/README.md (both exports are self-service downloads) and stop.
  2. Get their name for message-frequency counting. Ask how their name appears in LinkedIn messages (the "me" side), or read it from config/user.config.yaml.
  3. Run the build:
    python3 modules/crm-merge/build.py \
      --takeout-zip <path-or-omit-to-autofind> \
      --linkedin-dir <folder> \
      --me "<their name>" \
      --out data/crm-merge
    Omit any source they do not have; one source alone is fine.
  4. Report the counts the script prints: total unique people, how many appear in 2+ sources (the high-confidence merges), and how many link to a vault note. Flag if a source loaded zero records, since that usually means a wrong path.
  5. Point them onward. Tell them data/crm-merge/browser.html is openable in any browser, and that contacts.json is what /build-list dedups against.

Watch out for

  • Over-merging on a common name: if the user says distinct people got fused, lower --name-collision-threshold and re-run.
  • Zero LinkedIn messages counted: the --me name probably does not match the export. Check the FROM/TO values in messages.csv and pass the exact form.
  • Privacy: outputs are git-ignored; do not commit them or paste contact data into anything outward-facing.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.