Menu

Individual skill

track-contact-job-changes

0upvotes

Use this skill when you need to find which contacts in the CRM have changed jobs and act on it — a quarterly database refresh, a "did anyone move?" sweep, a churn-risk or new-champion check, or a job-change signal firing on a known contact. It reads each contact's current role from their work history, compares it to what the CRM believes, and routes the movers: still-there contacts get refreshed, confirmed leavers get their old and new roles separated, movers to non-fit companies get flagged and opted out, and movers to net-new fit companies get the company enriched, tiered, and optionally created as an account. Every CRM write is proposed for approval first — the database is never polluted and no contact is silently overwritten. Also known as: job change detection, contact data refresh, champion tracking, buyer-moved alerts.

skills/jorge-macias/track-contact-job-changes/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

One line: run this when you want the CRM's contacts to reflect where those people actually work now,
and to catch champions who moved to a new account. It produces a reviewed batch of CRM changes, never a
silent rewrite.

**Golden rule: propose, then confirm.** Collect every proposed change and show it as one table before
touching the CRM. And **never act on the wrong person** — if the enriched identity doesn't match the
contact, it goes to "can't confirm", not to a write.

## Setup (once)

Before the first run, capture the operator's configuration and save it — see
[references/setup-checklist.md](references/setup-checklist.md). It records: the CRM and whether writes
are allowed; the **match keys** for a person (record id, email, LinkedIn URL) and a **company** (domain,
LinkedIn company URL, name); the four data sources the play needs (a LinkedIn-URL finder, a work-history
Back to top