champion-tracker
Track product champions for job changes and qualify their new companies against ICP. Takes a CSV of known champions (with LinkedIn URLs), creates a baseline snapshot via Apify enrichment, then detects when champions move to new companies. Scores new companies on a 0-4 ICP fit scale. Outputs a downloadable CSV of movers with qualification verdicts.
npx skills add gooseworks-ai/goose-skills --skill champion-tracker --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Champion Tracker Detect when product champions change jobs and qualify their new companies against ICP. ## When to Use - You have a list of known product users/champions (from reviews, LinkedIn posts, CRM exports) - You want to detect when they change companies (high-intent re-sell signal) - You want each job change scored against ICP before reaching out ## Two Phases ### Phase A: Discover Champions (agent-driven, one-time) Build the initial champion list from public sources. This is done by the agent, not the script. 1. **Scrape reviews** — Use `review-site-scraper` skill to pull G2/Trustpilot reviews. Extract reviewer names + companies. 2. **Search LinkedIn posts** — Use the `linkedin-post-research` skill (Apify-based) to find people who posted about the product. 3. **Resolve LinkedIn URLs** — Use Fiber `/v1/kitchen-sink/person` (name + company → profile URL) or ContactOut via Orthogonal. 4. **Compile CSV** — Merge all sources into `champions.csv` with required columns. ### Phase B: Track Job Changes (script-driven, repeatable) Use `champion_tracker.py` for ongoing tracking. ## Script Usage ### Prerequisites - `APIFY_API_TOKEN` in `.env` (for LinkedIn profile enrichment) - Cham
- When to Use
- Two Phases
- Phase A: Discover Champions (agent-driven, one-time)
- Phase B: Track Job Changes (script-driven, repeatable)
- Script Usage
- Prerequisites
- Commands
- Output CSV Columns
- ICP Scoring (0-4)
- Cost
- File Structure
- Dependencies
Dry run — see cost estimate python3 skills/champion-tracker/scripts/champion_tracker.py init -i champions.csv --dry-run Create baseline python3 skills/champion-tracker/scripts/champion_tracker.py init -i champions.csv Dry run python3 skills/champion-tracker/scripts/champion_tracker.py check --dry-run Detect changes and output CSV python3 skills/champion-tracker/scripts/champion_tracker.py check -o changes.csv python3 skills/champion-tracker/scripts/champion_tracker.py status
What does the champion-tracker skill do?
Track product champions for job changes and qualify their new companies against ICP. Takes a CSV of known champions (with LinkedIn URLs), creates a baseline snapshot via Apify enrichment, then detects when champions move to new companies. Scores new companies on a 0-4 ICP fit scale. Outputs a downloadable CSV of movers with qualification verdicts.
How do I install it?
Run `npx skills add gooseworks-ai/goose-skills --skill champion-tracker --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From gooseworks-ai/goose-skills, a repository with 1,091 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.