Goose Skills is a library of workflows and data APIs that lets coding agents handle growth and go-to-market work such as advertising, social media, content, SEO, lead generation, and customer research. It is intended for teams using Claude Code, Cursor, Codex, and similar agents. The catalogue entries are its reusable skills.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add gooseworks-ai/goose-skills --skill champion-move-outreachgit clone --depth 1 https://github.com/gooseworks-ai/goose-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/gooseworks-ai/goose-skills/champion-move-outreach)<a href="https://agentmods.dev/skills/gooseworks-ai/goose-skills/champion-move-outreach"><img src="https://agentmods.dev/badge/skills/gooseworks-ai/goose-skills/champion-move-outreach/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gooseworks-ai/goose-skills/champion-move-outreach"><img src="https://agentmods.dev/badge/skills/gooseworks-ai/goose-skills/champion-move-outreach.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00078 | $0.06344 |
| Opus 5 | $0.00039 | $0.03172 |
| Sonnet 5 | $0.00016 | $0.01269 |
| Haiku 4.5 | $0.00008 | $0.00634 |
Grade A, and why
champion-move-outreach scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 644 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Champion Move Outreach
Tracks known buyers, champions, and power users for job changes. When someone who already knows your product moves to a new company, that's the highest-conversion outbound signal in B2B — they already trust you, they're in a new role trying to make an impact, and they have firsthand experience with what your product delivers.
Why this is the #1 signal: Every other signal (funding, hiring, leadership change) targets strangers. This targets people who already know, like, and trust your product. Conversion rates on champion-move outreach are 3-5x higher than cold outreach because:
- They don't need to be educated on what you do
- They have a positive experience to anchor on
- They want quick wins at the new company (bringing in a tool they trust IS a quick win)
- They can internally champion the deal because they have firsthand results to cite
When to Auto-Load
Load this composite when:
- User says "track my champions", "check for job changes", "who moved from our customer accounts", "champion tracking"
- User has a list of past buyers/users and wants to know if anyone changed jobs
- An upstream workflow (TAM Pulse) triggers a champion change check
Step 0: Configuration (One-Time Setup)
On first run for a client/user, collect and store these preferences. Skip on subsequent runs.
People to Track
| Question | Purpose | Stored As |
|---|---|---|
| Where does your list of people to track come from? | Defines the input source | people_source |
| What categories of people are you tracking? | Determines outreach tone per person | tracked_categories |
People source options:
- CRM export (Salesforce, HubSpot) — pull closed-won contacts, active users, power users
- CSV file — manually curated list
- Supabase
peopletable — filter bylead_status = 'customer'or similar - Manual list — names + LinkedIn URLs
Tracked categories:
| Category | Who They Are | Why They Matter | Stored As |
|---|---|---|---|
| Past buyers | Signed the contract at their previous company | Can sign again. Know the ROI. Can articulate value to new leadership. | past_buyers |
| Past champions | Advocated for your product internally, drove adoption | Will champion again. Often have stronger conviction than the original buyer. | past_champions |
| Power users | Used your product daily, know it deeply | Can demonstrate value hands-on. Often become the internal expert at the new company. | power_users |
| Lost deal contacts | Evaluated your product but chose a competitor or no decision | Weaker signal but still valid — they know you exist. New company = fresh start. | lost_deal_contacts |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 644 lines · 78 tokens per session scan A 8923871e7c22
champion-move-outreach is a skill published in the GitHub repository gooseworks-ai/goose-skills (1,202 stars, last pushed 11d ago), licensed MIT. It adds 78 tokens to every session and 6,344 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
sequence-architect
Design a 4-6 touch outreach cadence with channels, timing, tonal arc, and branching. Use when starting a new sequence from scratch given an ICP and offer.
icebreaker
Draft 3 distinct opening messages for a specific prospect, anchored on a why-now and a why-this-person. Use when sending a high-leverage first touch where personalization is worth the time.
sequence-doctor
Audit an outreach sequence and produce a ranked fix list. Use when reply rates are low, when you want a second opinion before sending, or when rewriting a sequence from scratch.
jargon-bingo
Score sales calls, emails, or posts on a 5x5 bingo card of cliches. Mostly for fun; quietly useful for spotting jargon-heavy patterns.
prospect-twin
Build a believable persona simulation of a prospect from their LinkedIn profile, then practice outreach against them. Use when preparing for a high-stakes outreach or call, when iterating on openers, or when testing whether a pitch lands.
cringe-translator
Translate sales-jargon-laden LinkedIn messages into what the sender actually means. Mostly for fun; occasionally educational about why a message tanked.