Systems Lab

Agent skill

signal-hunter

dormantSelf-containedInstructions only2,310 words

Filed under Prospecting and list building.

From VijayMatt/go-to-market-agent-skills · 12 skills · 1 · pushed 2026-03-29

What it does when it runs

Read from the skill and the 3 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
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about signal-hunter

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/VijayMatt/go-to-market-agent-skills.git /tmp/go-to-market-agent-skills
git -C /tmp/go-to-market-agent-skills sparse-checkout set "signal-hunter"
mkdir -p ~/.claude/skills/signal-hunter
cp -R "/tmp/go-to-market-agent-skills/signal-hunter/." ~/.claude/skills/signal-hunter/

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.

Reproduced in full from VijayMatt/go-to-market-agent-skills/blob/c948db28e7a0147976cc91ad91479900a75f7904/signal-hunter/SKILL.md, which is licensed MIT (repository). 2,310 words, 21 headings.

Signal Hunter: Complete Methodology

The Core Principle

Outbound works when you reach the right person at the right moment with the right message. Signal-based prospecting replaces spray-and-pray with precision timing. Instead of cold-calling 100 accounts, you monitor 500 accounts and reach out to the 8 that just showed a buying signal — with a message that references exactly what changed.

The result: 3-5x higher reply rates compared to cold outreach, because your email arrives when the problem is already top of mind.


The 6 Categories of Buying Signals

1. Job Changes (Signal Strength: HIGH)

What it is: A target persona starts a new role at a company in your ICP.

Why it matters: New leaders have a 90-day mandate to make changes. They have budget to spend, political capital to deploy, and a need to show early wins. They're also bringing mental models from their previous company — if they used a tool like yours before, they'll want it again.

Specific signals to monitor:

  • Target persona hired into a new company (VP Sales joins Series B startup)
  • Promotion into a decision-making role (Sr. Manager promoted to Director)
  • New C-suite hire (signals strategic shift — new CRO means sales transformation)
  • Your champion leaves their company and joins a new one (warm intro opportunity)
  • Your competitor's champion leaves (their deal may stall)

Signal decay: 48-72 hours. After a week, they're already getting pitched by everyone. After two weeks, they've made their initial vendor decisions.

Action: Congratulations email within 48 hours. Reference their background and connect it to a challenge they'll face in the new role.


2. Funding Rounds (Signal Strength: HIGH)

What it is: Company raises capital — seed, Series A/B/C, PE investment, debt financing.

Why it matters: Capital means budget. More specifically, the press release usually says what they plan to do with the money ("expand sales team," "invest in infrastructure," "enter new markets"). That tells you exactly which department is about to spend.

Specific signals to monitor:

  • Series A-C raises (growth stage, building infrastructure)
  • PE acquisition (usually followed by operational optimization)
  • IPO filing (compliance, governance, reporting needs spike)
  • Debt financing (often signals scaling existing operations)
  • Government grants or contracts (specific project needs)

Signal decay: 1-2 weeks. The money takes time to deploy, so you have more runway than job changes. But every rep with a CRM alert is also watching Crunchbase.

Action: Reference the raise and connect it to the specific initiative they announced. "Saw you raised $30M to expand into EMEA — that usually means [specific challenge your product solves]."


3. Hiring Patterns (Signal Strength: MEDIUM-HIGH)

What it is: Company is hiring for specific roles that indicate a need for your product.

Why it matters: Job postings are the most honest signal a company produces. They don't post jobs for fun. If they're hiring 5 SDRs, they're building outbound. If they're hiring a Data Engineer, they're investing in infrastructure. The job description often lists the exact tools they use (or plan to use).

Specific signals to monitor:

  • Volume hiring in a specific department (5+ SDR roles = building outbound motion)
  • Senior individual contributor roles (Sr. Data Engineer = infrastructure investment)
  • New department creation (first-ever Head of RevOps = they're professionalizing)
  • Job descriptions mentioning competitor tools ("experience with Salesforce required")
  • Job descriptions mentioning pain points your product solves

Signal decay: 1-3 weeks. Hiring is a slow process, so the window is wider. But the best time to reach out is when the job is posted, not when it's filled.

Action: Reference the job posting and connect it to the problem they're solving. "Noticed you're hiring your first RevOps lead — teams at that stage usually struggle with [X]. We helped [similar company] with that transition."


4. Tech Stack Changes (Signal Strength: MEDIUM)

What it is: Company adds, removes, or changes a technology in their stack.

Why it matters: Tech changes indicate active evaluation. If they just ripped out a competitor, they're looking for a replacement. If they just added a complementary tool, they may need your product to complete the workflow.

Specific signals to monitor:

  • Competitor removal (detected via BuiltWith, Wappalyzer, or job posting changes)
  • Complementary technology adoption (they added Snowflake — do they need your analytics tool?)
  • Contract renewal dates (public companies sometimes disclose in 10-Ks)
  • RFP postings (government or enterprise procurement portals)
  • Technology migration announcements (cloud migration, platform consolidation)

Signal decay: 2-4 weeks. Tech evaluations move slowly, but reaching out early means you shape the requirements.

Action: Reference the specific technology change. "Saw you recently adopted [tool] — companies that use [tool] typically also need [your capability] because [specific integration pain]."


5. Leadership Changes (Signal Strength: MEDIUM-HIGH)

What it is: Changes at the executive level — new CEO, CRO, CFO, board member, or strategic reorganization.

Why it matters: New leadership means new strategy. A new CRO will re-evaluate the entire sales tech stack. A new CFO will audit every vendor contract. A new CEO triggers a strategic review of everything. Board changes often precede strategic pivots.

Specific signals to monitor:

  • New CEO/CRO/CFO/CTO announcement
  • Board member additions (especially if the board member has domain expertise)
  • Reorganization announcements (merging departments, creating new divisions)
  • Strategy pivots mentioned in earnings calls or press releases
  • Activist investor involvement (signals pressure to cut costs or grow faster)

Signal decay: 2-4 weeks. Leadership transitions take time to produce action, but the research and vendor evaluation often starts immediately.

Action: Reference the leadership change and connect it to a strategic challenge. "With [name] coming on as CRO, you're probably re-evaluating [area]. We've helped other CROs in their first 90 days get visibility into [specific metric]."


6. Competitor Losses / Pain Signals (Signal Strength: VERY HIGH)

What it is: Signals that a company is unhappy with their current solution, lost a deal to you, or is experiencing pain that your product solves.

Why it matters: This is the highest-intent signal because the prospect has already identified the problem and is actively looking for alternatives. The battle is positioning, not awareness.

Specific signals to monitor:

  • Negative reviews of competitors on G2, Capterra, TrustRadius
  • Social media complaints about a vendor (Twitter/LinkedIn venting)
  • Competitor outage or security incident (their customers are suddenly open to alternatives)
  • Contract expiration (if you know their renewal date)
  • Competitor price increase announcements
  • "Rip and replace" job postings ("seeking alternative to [competitor]")
  • Community forum posts asking for alternatives

Signal decay: 24-72 hours for incidents/outages. 1-2 weeks for reviews and complaints. These are the most time-sensitive signals because the emotional frustration fades quickly.

Action: Lead with empathy, not opportunism. "I saw [competitor] had [issue] — that must be frustrating when you're trying to [goal]. We built [product] specifically to avoid that problem because [architectural reason]."


Signal Scoring Model

Not all signals are equal. Use this weighted scoring model to prioritize which accounts to work first.

Base Signal Scores

Signal CategoryBase ScoreRationale
Competitor loss / pain25Highest intent — already looking for alternatives
Job change (target persona)2090-day window, budget authority, mandate to act
Funding round18Budget unlocked, growth mandate
Leadership change15Strategic re-evaluation incoming
Hiring patterns12Indicates investment in the area
Tech stack change10Active evaluation, but may be slow-moving

Signal Multipliers

Apply these multipliers based on signal context:

MultiplierValueExample
Multiple signals from same account1.5xFunding round + hiring SDRs = 27 points
Signal involves your champion2.0xFormer customer joins new company = 40 points
Signal from Tier 1 ICP account1.3xEnterprise target shows any signal
Signal mentions your category1.5xJob posting says "seeking [your category] tool"
Recency (last 48 hours)1.2xFresh signal, act now

Priority Tiers

TierScore RangeActionSLA
P0 - Drop everything30+Personalized email + LinkedIn + phoneSame day
P1 - High priority20-29Personalized email + LinkedInWithin 48 hours
P2 - Standard priority12-19Semi-personalized email sequenceWithin 1 week
P3 - Monitor5-11Add to nurture sequenceOngoing

Compound Signal Scoring (Worked Example)

Account: Acme Corp (Series B SaaS, 200 employees)

Signals detected:

  1. New VP of Sales hired 3 days ago (base: 20, recency 1.2x = 24)
  2. Series B raised 2 weeks ago (base: 18)
  3. 4 SDR job postings this week (base: 12, recency 1.2x = 14.4)

Multiple signal multiplier on highest: 24 x 1.5 = 36 Total composite score: 36 + 18 + 14.4 = 68.4

Verdict: P0 — drop everything. This account is about to buy from someone.


Signal Monitoring Infrastructure

Daily Workflow

  1. Morning scan (15 min): Review overnight alerts from all monitoring sources
  2. Score and prioritize: Apply scoring model to new signals
  3. Act on P0/P1: Write and send personalized outreach
  4. Queue P2: Add to semi-personalized sequences
  5. Weekly review: Audit signal sources for gaps, update monitoring queries

Tool Stack

Primary (required):

  • Apollo.io — job changes, company signals, automated sequences
  • LinkedIn Sales Navigator — job changes, company updates, saved searches
  • Google Alerts — press mentions, funding announcements, leadership changes

Secondary (recommended):

  • Crunchbase — funding rounds, acquisitions, IPO filings
  • BuiltWith / Wappalyzer — tech stack changes
  • G2 / Capterra — competitor reviews and intent signals
  • Feedly or similar — industry press aggregation

Advanced (optional):

  • Bombora / 6sense — third-party intent data
  • Glassdoor — internal culture signals (mass hiring, layoffs)
  • SEC EDGAR — public company filings for contract and vendor data

Apollo.io Integration Pattern

Apollo is the hub because it combines contact data, signal detection, and outreach execution in one platform.

Setup:

  1. Build saved searches for each signal category
  2. Create contact lists that auto-populate from signals
  3. Build outreach sequences triggered by each signal type
  4. Set up Slack/email notifications for P0 signals

Saved Search Examples:

  • "Job changes in the last 7 days" filtered by title + industry + company size
  • "Companies that raised funding in the last 30 days" filtered by round size + industry
  • "Companies hiring [specific roles]" filtered by job title keywords

Automation Rules:

  • When job change detected for Tier 1 persona → auto-enroll in "Congrats" sequence
  • When funding round detected for ICP account → create task for manual research + outreach
  • When competitor mentioned in job posting → add to "Competitor Displacement" sequence

Signal-to-Outreach Mapping

Each signal type requires a different outreach approach. The worst thing you can do is detect a signal and then send a generic pitch. The signal IS the personalization — use it.

SignalOpening FrameToneCTA
Job change"Congrats on the new role"Warm, helpfulOffer a resource relevant to their first 90 days
Funding"Congrats on the raise"Strategic, forward-lookingShare how similar companies invested post-raise
Hiring"Noticed you're building out [team]"ConsultativeOffer insight on common challenges at that stage
Tech change"Saw you adopted [tool]"Technical, specificShare an integration use case or case study
Leadership change"With [name] joining..."Strategic, high-levelOffer a POV on what top [role]s prioritize first
Competitor pain"I saw [event/issue]..."Empathetic, not salesyOffer to show how you handle [specific thing] differently

Anti-Patterns

1. Signal hoarding. Collecting signals but not acting on them. If you can't action a signal within its decay window, don't bother monitoring it.

2. Generic outreach on a specific signal. Detecting a funding round and sending "Hi, I'd love to show you our product." You just wasted the signal. Reference it specifically.

3. Over-monitoring. Setting up alerts for 2,000 accounts when you can only handle 10 outreach messages per day. Monitor what you can action.

4. Single-signal fixation. Only watching for funding rounds and ignoring everything else. Layer signals for compound scoring.

5. Stale signal outreach. Congratulating someone on a job change 3 months after they started. Check your timing before you send.

6. Creepy specificity. "I noticed you liked a LinkedIn post about data governance at 3:47 PM yesterday." Signals should feel observed, not surveilled. Reference public business events, not personal behavior.


Measuring Signal-Based Outreach Performance

Track these metrics weekly to evaluate your signal program:

MetricTargetHow to measure
Signal-to-outreach rate>80% of P0/P1 signals actionedSignals detected vs. outreach sent
Signal outreach reply rate>15%Replies / emails sent (signal-based only)
Signal outreach meeting rate>5%Meetings booked / emails sent
Time-to-action<48 hours for P0Time between signal detection and first outreach
Signal source yieldVariesWhich sources produce the most actionable signals
Composite signal conversion2x single signalCompare conversion rates: single vs. multi-signal accounts

If your signal-based outreach reply rate is below 10%, the problem is your messaging, not your signals. If you're not finding enough signals, the problem is your monitoring setup or your account list is too narrow.

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

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.

Need help setting it up?

This page tells you what signal-hunter 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.