champion-tracker
Skill9 starsChanged 3 months agoMITView on GitHub
Use when monitoring job changes of past customers, positive responders, or engaged prospects, or when a known contact moves to a new company and you need to evaluate the new opportunity
1 other project uses a version of this.
Adopted by
Most recently taken up by
- zime-ai/zime-gtm-skillstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- zime-ai/zime-gtm-skills★ 19same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- compliance-managerSkill
- contact-finderSkill
- deliverability-managerSkill
- email-writerSkill
- linkedin-contentSkill
- meeting-followupSkill
- multi-channel-writerSkill
- pipeline-trackerSkill
- prospect-researcherSkill
- resource-offerSkill
- setupSkill
- signal-scannerSkill
- validateSkill
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
- Distinctive: line 32
When a job change is detected:
- Distinctive: line 55
Do not add champions to cold sequences.
≈ “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
Champion Tracker
Champion Definition
A champion is anyone who has shown genuine interest in your product:
- Past customer or pilot participant
- Replied positively to cold outreach (even "not now")
- Attended a demo or discovery call
- Engaged with content (open-source contributor, GitHub star, paper citation)
Champions carry context. When they move jobs, they bring that context with them — and arrive at a new company with fresh budget and mandate.
Champion List Setup
Maintain a dedicated "Champions" table in Clay with the following fields: Name, Current Title, Current Company, Current Domain, Original Signal, Last Interaction Date, Job Change Alert.
Three monitoring layers (run in parallel):
- Clay job change enrichment — enable "Job Change" column. Clay pings LinkedIn periodically and flags when company or title changes.
- Apollo People Alerts — go to Apollo → Lists → your champion list → enable "Job Change Alert". Sends email notification on change detection.
- LinkedIn Sales Navigator — add all champions to a saved lead list. Enable "Job change" alerts in the alert settings. Most reliable but requires Sales Nav license.
Review champion alerts weekly during pipeline review.
Job Change Workflow
When a job change is detected:
- Verify the change — confirm on LinkedIn directly. Check new company name, title, and start date.
- Evaluate the new company — run
prospect-researcherskill on the new company. Score against ICP criteria fromconfig/gtm-context.md. - Route by ICP score:
- ICP grade A or B: Enrich contact at new company (run
contact-finder), then generate warm outreach within 48 hours. Flag in HubSpot as "Champion Re-engage". - ICP grade C or D: Log the move in HubSpot. Add a note with new company. Set a 90-day follow-up task — re-evaluate if their domain signals grow.
- ICP grade A or B: Enrich contact at new company (run
- Log everything in HubSpot — update contact record with new company, title, domain. Create a new deal if advancing to outreach.
Champion Outreach
Reference config/templates/email-sequences/champion-job-change.md for the full template.
Key principles for champion outreach:
- Lead with the relationship, not the pitch. "Congrats on the move" is the opener, not "we help companies like X".
- Reference shared history — name the specific interaction ("when we spoke about your setup at [OldCo]").
- Be brief — 3–4 sentences max. They know who you are. No need to re-explain the product.
- Single CTA — ask for a 15-minute catch-up, not a demo. Lower barrier.
- Send within 48 hours of confirming the move. After 2 weeks, the "congrats on the new role" opener loses credibility.
Do not add champions to cold sequences. Always send individually from a primary inbox, not a sending domain.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.