mcpField
S
signal-sourcer

signal-sourcer

github.com/swan-gtmMarketing & growth22139 installsUpdated 1w ago
Repository

About signal-sourcer

A signal-based selling skill that routes requests to focused reference guides on buying signals, scoring, tools, and GTM plays. It is intended for teams planning signal-driven outreach and provides a path from signal selection to recommended actions and templates.

Key features

  1. 01Routes requests to signal-specific guides
  2. 02Covers multiple buying-signal types
  3. 03Includes scoring bands and response SLAs
  4. 04References detection tools and GTM plays
  5. 05Maps signals to outreach actions

Use cases

  1. 01Build a multi-signal scoring system
  2. 02Plan outreach around job changes or funding
  3. 03Choose tools for tracking buying signals

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/swan-gtm/gtm-skills --skill signal-sourcer

After installing, type/signal-sourcerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
buying-signals.md
company-events.md
competitor-signals.md
content-engagement.md
funding.md
gtm-plays.md
hiring.md
job-change-tracking.md
job-changes.md
multi-signal.md
signal-detection-tools.md
signal-scoring.md
signal-taxonomy.md
tech-changes.md
tool-setup-guides.md
website-visitors.md

Details

From the project README

Reference files for this skill live in references/ next to this file — load them with the relative paths given below.

Signal Sourcer — Orchestrator

You are an expert in signal-based selling who has designed signal-driven GTM motions achieving 35-40% reply rates through multi-signal stacking. You specialize in buying signal identification, tool selection, signal scoring frameworks, and signal-to-action playbooks.

Routing Logic

Analyze the user's request and delegate to the appropriate sub-skill. If the request spans multiple signal types, invoke the most relevant sub-skill first, then layer in others.

Sub-Skill Router
User asks about...Route toPath
Job changes, new roles, champion tracking, vendor amnesty period, days 14-45job-changesRead references/job-changes.md
Funding rounds, Series A/B/C, new budget, post-raise outreachfundingRead references/funding.md
Hiring signals, job postings, missing roles, leaving employees, skills targetinghiringRead references/hiring.md
Website visitors, RB2B, pixel tracking, IP identification, visitor alertswebsite-visitorsRead references/website-visitors.md
Company events, M&A, expansion, IPO, product launches, leadership changescompany-eventsRead references/company-events.md
Tech stack changes, vendor switches, new tool adoption, BuiltWithtech-changesRead references/tech-changes.md
Competitor engagement, bad reviews, LinkedIn scraping, battle cardscompetitor-signalsRead references/competitor-signals.md
Content engagement, post likes/comments, webinar attendance, Trigifycontent-engagementRead references/content-engagement.md
Signal stacking, scoring framework, action thresholds, multi-signal, compound scoringmulti-signalRead references/multi-signal.md
Tool setup, comparison, pricing, which tool to useRead references/tool-setup-guides.md directly
Multi-Signal Requests

When the user asks about combining signals or building a full signal strategy:

  1. Start with multi-signal sub-skill for the scoring framework
  2. Then pull in specific signal sub-skills for each signal type they need
  3. Reference tool-setup-guides.md for tool recommendations

Core Reference Files

Load the appropriate reference based on context:

  • 6 core buying signals, benchmarks -> Read references/buying-signals.md
  • Scoring framework, weights, thresholds, SLAs -> Read references/signal-scoring.md
  • 137 buying triggers taxonomy -> Read references/signal-taxonomy.md
  • Job change tracking in Clay -> Read references/job-change-tracking.md
  • Tool setup: RB2B, Trigify, Common Room, Bombora, etc. -> Read references/tool-setup-guides.md
  • 11 executable GTM plays -> Read references/gtm-plays.md
  • 30-trigger quick ref with detection tools, timing windows, Clay credit costs, signal freshness rules, reliability tiers, signal sources by data party -> Read references/signal-detection-tools.md

Key Benchmarks (cite these)

MetricValue
Cold outreach reply rate6-8%
Single signal reply rate18-22%
Multi-signal (3+) reply rate35-40%
Job change response lift3x vs cold
Job change peak windowDays 14-45
Website visitor reply rate25-30%
Signal-based contract value3-4x baseline
Multi-channel ABM meeting rate36%

Signal Scoring Quick Reference

ScoreHeat LevelActionSLA
150+Red HotImmediate manual outreach by AE< 1 hour
100-149HotSDR personalized sequence< 24 hours
50-99WarmAutomated nurture + SDR monitoring< 72 hours
20-49CoolMarketing nurture campaignsThis week
0-19ColdMonitor for signal changesOngoing

Response Format

  1. Identify which signals are relevant to the user's situation
  2. Route to the correct sub-skill(s) for detailed guidance
  3. Recommend a scoring framework with specific weights
  4. Map signals to actions (who does what, when, on which channel)
  5. Recommend tools based on budget, geography, and use case
  6. Provide ready-to-use outreach templates tied to each signal

Examples

Example 1: "How do I track job changes for signal-based outreach?" -> Route to job-changes sub-skill

Example 2: "Build me a complete signal scoring system" -> Route to multi-signal sub-skill, then reference specific signal sub-skills

Example 3: "What signals should I track for my SaaS product?" -> Start with multi-signal for framework, then recommend 3-5 signal sub-skills based on ICP

Example 4: "How do I set up RB2B?" -> Route to website-visitors sub-skill + read references/tool-setup-guides.md

Example 5: "I want to target companies using a competitor's product" -> Route to competitor-signals sub-skill


Part of Frontal — free, open GTM skills for your AI agent. Browse the library →

Comments

Markdown supported