Agent skill
job-changes
Job change signal tracking for B2B outbound.
Filed under Prospecting and list building.
From Frontal-so/outbound-skills · 73 skills · 4 · pushed 2026-07-14
What it does when it runs
Job change signal tracking for B2B outbound. Use when the user asks about job change signals, champion tracking, new role outreach, vendor amnesty period, Clay job change monitoring, or days 14-45 engagement window. Do NOT use for general hiring signals (use hiring skill) or company-level events (use company-events skill).
Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- frontal.so
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/Frontal-so/outbound-skills.git /tmp/outbound-skills git -C /tmp/outbound-skills sparse-checkout set "master-skills/signal-sourcer/.claude/skills/job-changes" mkdir -p ~/.claude/skills/job-changes cp -R "/tmp/outbound-skills/master-skills/signal-sourcer/.claude/skills/job-changes/." ~/.claude/skills/job-changes/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from Frontal-so/outbound-skills/blob/27cd847be5ce7e9b749b1d672cbfb29935d911db/master-skills/signal-sourcer/.claude/skills/job-changes/SKILL.md, which is licensed MIT (repository). 508 words, 11 headings.
Job Change Signals
Job changes are the #2 buying signal by purchase correlation. New leaders have a mandate for early wins, vendor amnesty period, and budget air cover. Response rate is 3x higher than cold outreach, with peak engagement at days 14-45.
Reference Files
- Read
{SKILL_BASE}/resources/timing/job-change-tracking.mdfor Clay setup and tracking methods - Read
{SKILL_BASE}/resources/buying-signals.mdfor signal ranking and benchmarks
Why Job Changes Work
- 3x higher response rate vs cold outreach
- Peak engagement: days 14-45 after the change (vendor amnesty period)
- New leaders actively build their stack in first 90 days
- Trust already established with former champions
- Champion job change to target account = 75 points (Tier 1 signal)
Clay Setup - Two Methods
Method 1: Monitor Existing Table
- Go to Actions > Monitor for Job Changes
- Specify the LinkedIn URL column
- Save and run - new row created for each detected change
Method 2: Create New Tracking Table
- +Create New > Table > Track Job Changes
- Include "Person LinkedIn URL" for future monitoring
- Include "Company LinkedIn URL" to detect if they already changed
Historical vs Future
- Historical: Include both Person + Company LinkedIn URLs - checks if contact already changed
- Future: Only Person LinkedIn URL - monitors ongoing changes
Timing Framework
| Window | Multiplier | Action |
|---|---|---|
| Days 0-13 | Too early | Monitor only - they are still settling in |
| Days 14-45 | Peak (1.5x) | Immediate outreach - vendor amnesty window |
| Days 46-90 | Good (1.0x) | Standard outreach - still building stack |
| Days 90+ | Declining (0.7x) | Lower priority - stack likely set |
Outreach Template
Hey congrats on the new role at {{company}}.
As you are taking over {{department}}, curious how you are
currently handling {{relevant_problem}}?
We helped {{similar_company}} with exactly that.
Key Rules
- Do NOT mention you tracked their job change ("I saw you moved to...")
- Reference the role/department naturally, not the signal itself
- Former champions get AE-owned outreach (warm relationship)
- New contacts at target accounts get SDR sequence
- Stack with other signals for compound scoring: job change (75pts) + website visit (50pts) = Hot
Examples
Example 1: "Track when my past customers change jobs" -> Set up Clay historical tracking with Person + Company LinkedIn URLs, filter to ICP companies, trigger AE outreach within 24h
Example 2: "Someone just started as VP Sales at a target account" -> Day 14-45 window = peak timing. Send congratulations + reference relevant problem for their new role. AE owns if former champion, SDR if new contact
Example 3: "Build a job change signal workflow in Clay" -> Create tracking table with Person LinkedIn URLs, add enrichment columns (new company, title, start date), filter ICP match, calculate days-since-change, route to Slack alerts for day 14+ changes
Part of Frontal — free, open GTM skills for your AI agent. Browse the library →
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- job-posting-intent by edupegoretti · 0
Need help setting it up?
This page tells you what job-changes does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.