Social intent monitoring skill

Build a social intent monitoring system that turns public social conversations into qualified outbound triggers.

by LeadMagic·MIT license·★ 62 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words
# Social Intent Monitoring

## Overview

Most outbound programs are volume-gated rather than timing-gated. Reps build
lists and send sequences regardless of whether anything has actually happened.
Social intent monitoring replaces that model: an AI agent watches public
social conversations continuously, and an email or DM only fires when a
qualifying event occurs in real time.

The mistake this skill prevents: treating social platforms as broadcast
channels rather than signal feeds. Every competitor-mention comment, every
"does anyone have a recommendation for X" post, every founder publicly
describing a problem you solve — these are live intent signals that expire
within 24-72 hours. Catching them and acting fast beats the best cold copy
by a wide margin.

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

Files of Social intent monitoring

LeadMagic/main1 file shown
SKILL.md
Show the full text326 lines

Social Intent Monitoring

Overview

Most outbound programs are volume-gated rather than timing-gated. Reps build lists and send sequences regardless of whether anything has actually happened. Social intent monitoring replaces that model: an AI agent watches public social conversations continuously, and an email or DM only fires when a qualifying event occurs in real time.

The mistake this skill prevents: treating social platforms as broadcast channels rather than signal feeds. Every competitor-mention comment, every "does anyone have a recommendation for X" post, every founder publicly describing a problem you solve — these are live intent signals that expire within 24-72 hours. Catching them and acting fast beats the best cold copy by a wide margin.

This skill builds the full monitoring architecture: what to watch, how to qualify signals, how to route them to enrichment and outreach tools, and how to measure signal quality over time.

When to Use

  • "Set up social intent monitoring for our target accounts"
  • "Monitor LinkedIn for people talking about problems we solve"
  • "Build a Trigify workflow that routes competitor mentions to outreach"
  • "Detect social buying signals before prospects fill out a form"
  • "Create a signal infrastructure for our outbound motion"
  • "How do I use social listening for lead generation?"
  • "Set up keyword monitoring on LinkedIn and X for intent"
  • "Automate outreach from social signals"

Authoritative Foundations

Max Mitchum — Signal, Context, Action Framework

Max Mitchum, Co-Founder & CEO of Trigify.io, published the Signal, Context, Action model as the operating framework for signal-led outbound. The three layers:

Signal — the public event that suggests an account is worth contacting now. Examples from Mitchum's 2026 playbook: competitor engagement on LinkedIn or X, hiring posts for GTM roles, founder or operator posts describing a problem you solve, funding reactions, pain-point mentions in comments, product launches in adjacent categories, public recommendation requests.

Context — the judgement layer. Who is this person? What company? Are they in ICP? Why does this specific event matter? Is the timing strong? A signal without context is noise; context without a signal is guessing.

Action — the downstream workflow. Enrich the person, find the email, research the company, draft the message anchored to that specific signal, push into the sequencer, alert the rep in Slack with the reasoning.

Source: https://maxmitcham.substack.com/p/48-meetings-from-120-leads-in-two

The core principle: the email is the commodity. AI can write decent emails. The moat is knowing when the email has a reason to exist.

Trigify Workflow Patterns

Trigify's public documentation describes four canonical agentic workflow patterns for sales and lead generation teams:

  1. ICP-Filtered Post Trigger: New Post Trigger → Person Enrichment → ICP filter (country, headcount) → Email Enrichment → deliverability check → CRM or email campaign push.

  2. Viral Engager Harvesting: Post with high engagement threshold detected → fetch all engagers → Person Enrichment → filter for VP/Director titles → CRM or agent memory.

  3. Inbound Lead Routing by Seniority: Webhook trigger → Person Enrichment using LinkedIn URL → seniority check → high-value: Slack alert to sales team; others: nurture sequence.

  4. Competitor Mention Monitoring: Track competitor mentions → enrich mentioner → ICP filter → route to warm outreach sequence.

Source: https://help.trigify.io/en/articles/8836198-draft-common-workflow-patterns

ColdIQ Signal Taxonomy

ColdIQ's published trigger-selling taxonomy classifies intent signals into four tiers: Hiring signals, Funding signals, Tech Stack changes, and Behavioral intent (website visits, content engagement, review site activity). Social listening adds a fifth tier — Public Conversation signals — not captured by traditional data providers. Each tier requires different outreach timing and angle.

Prerequisites

  • Target account list (CRM, CSV, or HubSpot/Salesforce export)
  • ICP criteria defined (firmographic + role criteria for signal filtering)
  • Social listening platform configured (Trigify recommended; alternatives: Brandwatch, Mention, Keywordsio for simpler setups)
  • Enrichment provider for email and firmographic lookup (LeadMagic, Apollo, Clay waterfall)
  • Outreach tool connected (Instantly, Smartlead, Salesloft, or HubSpot sequences)
  • Slack or CRM for internal signal routing and rep alerts

Step-by-Step Process

Phase 1: Define Your Signal Taxonomy

Decide which social signals are worth acting on for your business. Not all conversations are buying signals. The highest-value signals:

Signal Type Description Urgency Outreach Angle
Competitor engagement Prospect comments on, likes, or shares competitor content High — 24-48hr window Offer comparison, address common pain with that competitor
Problem statement post Founder or operator publicly describes a problem you solve High — act within 12 hrs Reference their exact words; offer a specific solution
Recommendation request "Does anyone have a recommendation for X?" Very High — act within 2 hrs Direct reply + personal DM
Hiring for GTM role Post about hiring SDR, RevOps, VP Sales — roles your product supports Medium — 3-5 day window Tie outreach to the hiring intent; new hires evaluate tools
Funding reaction post Company or founder posts about closing a round Medium — 1 week window Congratulate + connect to common post-funding challenges
Pain-point comment Target prospect comments on someone else's post about a problem High — act within 48 hrs Reference the comment thread; show understanding
Content engagement pattern Prospect consistently engages with content in your category Low/Medium — warm long-play Nurture track; add to account monitoring

Mitchum's rule: only act on signals where you can write a specific, non-generic opening that references exactly what happened. If the signal can't anchor the first line of the message, it's not a strong enough trigger.

Phase 2: Configure Social Listening

Using Trigify (full agentic workflow):

  1. Create social listening searches for your target topics, competitors, and keywords across LinkedIn, X, Reddit, and other configured sources.
  2. Configure Signal types in the Signals tab — buying intent, hiring signals, competitor mentions, product complaints, leadership changes.
  3. Set score/severity thresholds to filter noise; only fire workflows above your minimum signal confidence bar.
  4. Set date windows — only act on signals from the past 24-72 hours; stale signals lose their timing advantage.

Keyword search strategy:

  • Competitor names + pain phrases ("Competitor X is too expensive", "left Competitor X")
  • Problem categories your product solves ("struggling with [problem]", "anyone solved [problem]")
  • Recommendation requests ("looking for a tool that does X", "anyone use Y")
  • Adjacent category launches ("just launched our outbound program")

Avoid over-broad keywords that generate noise (company names alone, generic industry terms). Signal quality matters more than signal volume.

Phase 3: Build the Enrichment and Qualification Layer

When a signal fires, the workflow must answer three questions before any outreach is initiated:

  1. Is this person in ICP? (job title, company size, industry, geography)
  2. Is this company on our target account list? (or does it match ICP firmographic criteria if not pre-listed?)
  3. Is there a reachable email? (run through email enrichment with deliverability verification before pushing to sequencer)

Typical workflow node sequence:

Signal Trigger → Person Enrichment (LinkedIn → firmographics + title)
  → ICP Filter (Boolean: title match AND company size match)
    → True: Email Enrichment → Deliverability Check
      → Verified: Push to Sequencer + Slack Alert with signal context
      → Unverified: Add to CRM without email trigger
    → False: Discard or add to low-priority nurture list

Use Trigify's built-in AI qualification agents to assess whether a post or mention is genuinely relevant before enrichment credits are consumed.

Phase 4: Craft Signal-Anchored Outreach

The outreach message must reference the specific signal. Generic openers destroy the value of the signal layer.

Fake personalisation (signal wasted):

"Hi Sarah, I noticed you're scaling your GTM team. Curious if you'd be open to a quick call about how we help companies like yours..."

Signal-anchored message (Mitchum framework applied):

"Hi Sarah, Saw your comment on Chris's post about the SDR ramp problem — specifically your point about the first 60 days. We helped three teams at similar stages cut ramp from 90 to 45 days. Worth a conversation?"

Rules for signal-anchored messages:

  • The first line must be traceable to the exact signal event
  • Do not ask for a meeting in the first message; offer context or a question
  • Keep total message under 100 words
  • No product feature lists; one specific proof point tied to their signal
  • If the signal is a comment, quote or closely paraphrase what they said
Phase 5: Route and Alert

Qualified signals with verified emails enter the sequencer. Uncontacted high-value signals (CEO, VP-level with no email found) get a Slack alert to the rep with the signal context included — enough for a manual LinkedIn outreach.

Signal routing tiers:

Account Tier Signal Strength Action
Named target account Any qualifying signal Immediate Slack alert + email enroll
ICP-match not on named list High signal (recommendation request, problem post) Email enroll + add to CRM
ICP-match not on named list Medium signal (competitor engagement, hiring post) CRM add + nurture track
Non-ICP Any signal Discard
Phase 6: Measure Signal Quality

Track signal performance separately from overall outreach metrics. The signal layer needs its own feedback loop:

  • Reply rate by signal type — which signal types generate the highest reply rates? Reallocate monitoring budget to the highest-performers.
  • Signal-to-meeting rate — of all signals that triggered outreach, what percentage booked a meeting?
  • Signal freshness distribution — what percentage of signals fired within 24 hours vs. 24-72 hours vs. older? Older signals should be deprioritized.
  • False positive rate — signals that triggered enrichment and outreach but were not actually relevant. Review and tighten keyword search or ICP filter criteria.

Review signal performance weekly during ramp; monthly once stable.

Output Format

Social intent monitoring system documentation:

  1. Signal taxonomy — table of signal types with urgency, outreach angle, and platform sources configured for each
  2. Listening configuration — keyword list, competitor list, topic categories, and score thresholds per platform
  3. Qualification workflow — node-by-node flow diagram or table (trigger → enrichment → ICP filter → email verification → action routing)
  4. Message templates — 2-3 signal-anchored message variants per top signal type, each under 100 words with first-line tied to the signal
  5. Routing rules — account-tier-to-action mapping
  6. Measurement dashboard spec — KPIs, signal-type breakdown, and weekly review cadence

Quality Check

  • Signal types defined with urgency windows (not just categories)
  • ICP filter criteria specified before enrichment step (prevent credit waste)
  • Email verification in workflow before sequencer push
  • All message templates reference signal in first line — no generic openers
  • Slack or CRM alert configured for high-value uncontacted signals
  • Keyword searches reviewed for noise — signal quality over volume
  • Signal freshness thresholds set (24-72 hr maximum for high-urgency signals)
  • Measurement plan covers reply rate by signal type, not just overall rate

Common Pitfalls

  1. Acting on stale signals. A competitor mention from last week is not the same as one from yesterday. Set hard freshness windows: recommendation requests expire in 2 hours, most other signals in 24-72 hours. Signals older than 72 hours should go to a low-priority nurture track, not hot outreach.

  2. Generic outreach from signal data. Running a signal-triggered sequence with the same generic opener you'd send to a cold list defeats the entire point. The signal must appear in the first sentence. If you can't reference it specifically, don't send the email.

  3. Enriching before filtering. Running every signal through enrichment before checking ICP fit burns credits and slows workflows. Filter by job title and company size using free platform data first; only enrich confirmed ICP-matches.

  4. Keyword search too broad. Monitoring your own company name or a one-word competitor name without context generates hundreds of irrelevant signals. Use phrase-level queries and negative keyword filters.

  5. No feedback loop on signal quality. Running signal-led outbound without tracking reply rate by signal type means you never know which signal types are actually worth acting on. Some categories that seem strong (funding signals) often underperform industry-specific problem posts. Measure weekly.

  6. Confusing social listening with social selling. Social listening is about monitoring what others say publicly (inbound signal collection). Social selling (the social-selling skill) is about building your own presence and engaging with your network. They work together but require separate workflows and metrics.

Execution Artifacts

  • references/framework-notes.md — Named frameworks and reference tables
  • templates/output-template.md — Deliverable shell for agent output
  • scripts/check-output.py — Lightweight deliverable validator
  • signal-scoring: Score and tier accounts across multiple signal sources; complements social monitoring with hiring, funding, and tech stack signals
  • lead-enrichment: Enrich the people detected by social monitoring
  • hiring-signal-play: Specific play for hiring-intent signals from job boards
  • multi-channel-outreach: Coordinate email + LinkedIn + call after signal fires
  • social-selling: Build your own LinkedIn presence that generates inbound signals
  • cold-email-strategy: Write the signal-anchored emails that social monitoring triggers
1---
2name: social-intent-monitoring
3description: >-
4 Build a social intent monitoring system that turns public social conversations
5 into qualified outbound triggers. Use when the user wants to monitor LinkedIn,
6 X, Reddit, or other platforms for buying signals — competitor engagement,
7 hiring intent posts, pain-point mentions, funding reactions, or public
8 recommendation requests — and automatically route those signals into outreach
9 workflows. Triggers on: "social listening", "social signals", "monitor LinkedIn
10 for intent", "Trigify", "agentic social listening", "competitor mention
11 monitoring", "social intent", "signal-led outbound", "signal infrastructure",
12 "social buying signals", or any request to detect intent from public social
13 content.
14license: MIT
15compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
16metadata:
17 version: "1.0.0"
18 author: LeadMagic
19 category: prospecting
20 tags: [signals, social-listening, intent, outbound, trigify, agentic]
21 related_skills: [signal-scoring, lead-enrichment, hiring-signal-play, multi-channel-outreach]
22 frameworks:
23 - "Max Mitchum — Signal, Context, Action Framework (Trigify)"
24 - "Trigify Workflow Patterns — Agentic Social Listening"
25 - "ColdIQ Signal Taxonomy — Trigger-Based Selling"
26---
27 
28# Social Intent Monitoring
29 
30## Overview
31 
32Most outbound programs are volume-gated rather than timing-gated. Reps build
33lists and send sequences regardless of whether anything has actually happened.
34Social intent monitoring replaces that model: an AI agent watches public
35social conversations continuously, and an email or DM only fires when a
36qualifying event occurs in real time.
37 
38The mistake this skill prevents: treating social platforms as broadcast
39channels rather than signal feeds. Every competitor-mention comment, every
40"does anyone have a recommendation for X" post, every founder publicly
41describing a problem you solve — these are live intent signals that expire
42within 24-72 hours. Catching them and acting fast beats the best cold copy
43by a wide margin.
44 
45This skill builds the full monitoring architecture: what to watch, how to
46qualify signals, how to route them to enrichment and outreach tools, and
47how to measure signal quality over time.
48 
49## When to Use
50 
51- "Set up social intent monitoring for our target accounts"
52- "Monitor LinkedIn for people talking about problems we solve"
53- "Build a Trigify workflow that routes competitor mentions to outreach"
54- "Detect social buying signals before prospects fill out a form"
55- "Create a signal infrastructure for our outbound motion"
56- "How do I use social listening for lead generation?"
57- "Set up keyword monitoring on LinkedIn and X for intent"
58- "Automate outreach from social signals"
59 
60## Authoritative Foundations
61 
62### Max Mitchum — Signal, Context, Action Framework
63 
64Max Mitchum, Co-Founder & CEO of Trigify.io, published the Signal, Context,
65Action model as the operating framework for signal-led outbound. The three
66layers:
67 
68**Signal** — the public event that suggests an account is worth contacting
69now. Examples from Mitchum's 2026 playbook: competitor engagement on LinkedIn
70or X, hiring posts for GTM roles, founder or operator posts describing a
71problem you solve, funding reactions, pain-point mentions in comments, product
72launches in adjacent categories, public recommendation requests.
73 
74**Context** — the judgement layer. Who is this person? What company? Are they
75in ICP? Why does this specific event matter? Is the timing strong? A signal
76without context is noise; context without a signal is guessing.
77 
78**Action** — the downstream workflow. Enrich the person, find the email,
79research the company, draft the message anchored to that specific signal,
80push into the sequencer, alert the rep in Slack with the reasoning.
81 
82Source: https://maxmitcham.substack.com/p/48-meetings-from-120-leads-in-two
83 
84The core principle: the email is the commodity. AI can write decent emails.
85The moat is knowing when the email has a reason to exist.
86 
87### Trigify Workflow Patterns
88 
89Trigify's public documentation describes four canonical agentic workflow
90patterns for sales and lead generation teams:
91 
921. **ICP-Filtered Post Trigger**: New Post Trigger → Person Enrichment →
93 ICP filter (country, headcount) → Email Enrichment → deliverability check
94 → CRM or email campaign push.
95 
962. **Viral Engager Harvesting**: Post with high engagement threshold detected
97 → fetch all engagers → Person Enrichment → filter for VP/Director titles
98 → CRM or agent memory.
99 
1003. **Inbound Lead Routing by Seniority**: Webhook trigger → Person Enrichment
101 using LinkedIn URL → seniority check → high-value: Slack alert to sales
102 team; others: nurture sequence.
103 
1044. **Competitor Mention Monitoring**: Track competitor mentions → enrich
105 mentioner → ICP filter → route to warm outreach sequence.
106 
107Source: https://help.trigify.io/en/articles/8836198-draft-common-workflow-patterns
108 
109### ColdIQ Signal Taxonomy
110 
111ColdIQ's published trigger-selling taxonomy classifies intent signals into
112four tiers: Hiring signals, Funding signals, Tech Stack changes, and
113Behavioral intent (website visits, content engagement, review site activity).
114Social listening adds a fifth tier — Public Conversation signals — not
115captured by traditional data providers. Each tier requires different outreach
116timing and angle.
117 
118## Prerequisites
119 
120- Target account list (CRM, CSV, or HubSpot/Salesforce export)
121- ICP criteria defined (firmographic + role criteria for signal filtering)
122- Social listening platform configured (Trigify recommended; alternatives:
123 Brandwatch, Mention, Keywordsio for simpler setups)
124- Enrichment provider for email and firmographic lookup (LeadMagic, Apollo,
125 Clay waterfall)
126- Outreach tool connected (Instantly, Smartlead, Salesloft, or HubSpot
127 sequences)
128- Slack or CRM for internal signal routing and rep alerts
129 
130## Step-by-Step Process
131 
132### Phase 1: Define Your Signal Taxonomy
133 
134Decide which social signals are worth acting on for your business. Not all
135conversations are buying signals. The highest-value signals:
136 
137| Signal Type | Description | Urgency | Outreach Angle |
138|---|---|---|---|
139| **Competitor engagement** | Prospect comments on, likes, or shares competitor content | High — 24-48hr window | Offer comparison, address common pain with that competitor |
140| **Problem statement post** | Founder or operator publicly describes a problem you solve | High — act within 12 hrs | Reference their exact words; offer a specific solution |
141| **Recommendation request** | "Does anyone have a recommendation for X?" | Very High — act within 2 hrs | Direct reply + personal DM |
142| **Hiring for GTM role** | Post about hiring SDR, RevOps, VP Sales — roles your product supports | Medium — 3-5 day window | Tie outreach to the hiring intent; new hires evaluate tools |
143| **Funding reaction post** | Company or founder posts about closing a round | Medium — 1 week window | Congratulate + connect to common post-funding challenges |
144| **Pain-point comment** | Target prospect comments on someone else's post about a problem | High — act within 48 hrs | Reference the comment thread; show understanding |
145| **Content engagement pattern** | Prospect consistently engages with content in your category | Low/Medium — warm long-play | Nurture track; add to account monitoring |
146 
147Mitchum's rule: only act on signals where you can write a specific, non-generic
148opening that references exactly what happened. If the signal can't anchor the
149first line of the message, it's not a strong enough trigger.
150 
151### Phase 2: Configure Social Listening
152 
153**Using Trigify (full agentic workflow):**
1541. Create social listening searches for your target topics, competitors,
155 and keywords across LinkedIn, X, Reddit, and other configured sources.
1562. Configure Signal types in the Signals tab — buying intent, hiring signals,
157 competitor mentions, product complaints, leadership changes.
1583. Set score/severity thresholds to filter noise; only fire workflows above
159 your minimum signal confidence bar.
1604. Set date windows — only act on signals from the past 24-72 hours; stale
161 signals lose their timing advantage.
162 
163**Keyword search strategy:**
164- Competitor names + pain phrases ("Competitor X is too expensive", "left
165 Competitor X")
166- Problem categories your product solves ("struggling with [problem]", "anyone
167 solved [problem]")
168- Recommendation requests ("looking for a tool that does X", "anyone use Y")
169- Adjacent category launches ("just launched our outbound program")
170 
171**Avoid over-broad keywords** that generate noise (company names alone,
172generic industry terms). Signal quality matters more than signal volume.
173 
174### Phase 3: Build the Enrichment and Qualification Layer
175 
176When a signal fires, the workflow must answer three questions before any
177outreach is initiated:
178 
1791. **Is this person in ICP?** (job title, company size, industry, geography)
1802. **Is this company on our target account list?** (or does it match ICP
181 firmographic criteria if not pre-listed?)
1823. **Is there a reachable email?** (run through email enrichment with
183 deliverability verification before pushing to sequencer)
184 
185Typical workflow node sequence:
186```
187Signal Trigger → Person Enrichment (LinkedIn → firmographics + title)
188 → ICP Filter (Boolean: title match AND company size match)
189 → True: Email Enrichment → Deliverability Check
190 → Verified: Push to Sequencer + Slack Alert with signal context
191 → Unverified: Add to CRM without email trigger
192 → False: Discard or add to low-priority nurture list
193```
194 
195Use Trigify's built-in AI qualification agents to assess whether a post or
196mention is genuinely relevant before enrichment credits are consumed.
197 
198### Phase 4: Craft Signal-Anchored Outreach
199 
200The outreach message must reference the specific signal. Generic openers
201destroy the value of the signal layer.
202 
203**Fake personalisation (signal wasted):**
204> "Hi Sarah, I noticed you're scaling your GTM team. Curious if you'd be
205> open to a quick call about how we help companies like yours..."
206 
207**Signal-anchored message (Mitchum framework applied):**
208> "Hi Sarah, Saw your comment on Chris's post about the SDR ramp problem —
209> specifically your point about the first 60 days. We helped three teams
210> at similar stages cut ramp from 90 to 45 days. Worth a conversation?"
211 
212Rules for signal-anchored messages:
213- The first line must be traceable to the exact signal event
214- Do not ask for a meeting in the first message; offer context or a question
215- Keep total message under 100 words
216- No product feature lists; one specific proof point tied to their signal
217- If the signal is a comment, quote or closely paraphrase what they said
218 
219### Phase 5: Route and Alert
220 
221Qualified signals with verified emails enter the sequencer. Uncontacted
222high-value signals (CEO, VP-level with no email found) get a Slack alert
223to the rep with the signal context included — enough for a manual LinkedIn
224outreach.
225 
226Signal routing tiers:
227| Account Tier | Signal Strength | Action |
228|---|---|---|
229| Named target account | Any qualifying signal | Immediate Slack alert + email enroll |
230| ICP-match not on named list | High signal (recommendation request, problem post) | Email enroll + add to CRM |
231| ICP-match not on named list | Medium signal (competitor engagement, hiring post) | CRM add + nurture track |
232| Non-ICP | Any signal | Discard |
233 
234### Phase 6: Measure Signal Quality
235 
236Track signal performance separately from overall outreach metrics. The signal
237layer needs its own feedback loop:
238 
239- **Reply rate by signal type** — which signal types generate the highest
240 reply rates? Reallocate monitoring budget to the highest-performers.
241- **Signal-to-meeting rate** — of all signals that triggered outreach, what
242 percentage booked a meeting?
243- **Signal freshness distribution** — what percentage of signals fired within
244 24 hours vs. 24-72 hours vs. older? Older signals should be deprioritized.
245- **False positive rate** — signals that triggered enrichment and outreach
246 but were not actually relevant. Review and tighten keyword search or ICP
247 filter criteria.
248 
249Review signal performance weekly during ramp; monthly once stable.
250 
251## Output Format
252 
253Social intent monitoring system documentation:
254 
2551. **Signal taxonomy** — table of signal types with urgency, outreach angle,
256 and platform sources configured for each
2572. **Listening configuration** — keyword list, competitor list, topic
258 categories, and score thresholds per platform
2593. **Qualification workflow** — node-by-node flow diagram or table (trigger
260 → enrichment → ICP filter → email verification → action routing)
2614. **Message templates** — 2-3 signal-anchored message variants per top
262 signal type, each under 100 words with first-line tied to the signal
2635. **Routing rules** — account-tier-to-action mapping
2646. **Measurement dashboard spec** — KPIs, signal-type breakdown, and weekly
265 review cadence
266 
267## Quality Check
268 
269- [ ] Signal types defined with urgency windows (not just categories)
270- [ ] ICP filter criteria specified before enrichment step (prevent credit waste)
271- [ ] Email verification in workflow before sequencer push
272- [ ] All message templates reference signal in first line — no generic openers
273- [ ] Slack or CRM alert configured for high-value uncontacted signals
274- [ ] Keyword searches reviewed for noise — signal quality over volume
275- [ ] Signal freshness thresholds set (24-72 hr maximum for high-urgency signals)
276- [ ] Measurement plan covers reply rate by signal type, not just overall rate
277 
278## Common Pitfalls
279 
2801. **Acting on stale signals.** A competitor mention from last week is not the
281 same as one from yesterday. Set hard freshness windows: recommendation
282 requests expire in 2 hours, most other signals in 24-72 hours. Signals
283 older than 72 hours should go to a low-priority nurture track, not hot
284 outreach.
285 
2862. **Generic outreach from signal data.** Running a signal-triggered sequence
287 with the same generic opener you'd send to a cold list defeats the entire
288 point. The signal must appear in the first sentence. If you can't reference
289 it specifically, don't send the email.
290 
2913. **Enriching before filtering.** Running every signal through enrichment
292 before checking ICP fit burns credits and slows workflows. Filter by job
293 title and company size using free platform data first; only enrich confirmed
294 ICP-matches.
295 
2964. **Keyword search too broad.** Monitoring your own company name or a one-word
297 competitor name without context generates hundreds of irrelevant signals.
298 Use phrase-level queries and negative keyword filters.
299 
3005. **No feedback loop on signal quality.** Running signal-led outbound without
301 tracking reply rate by signal type means you never know which signal types
302 are actually worth acting on. Some categories that seem strong (funding
303 signals) often underperform industry-specific problem posts. Measure weekly.
304 
3056. **Confusing social listening with social selling.** Social listening is about
306 monitoring what others say publicly (inbound signal collection). Social
307 selling (the `social-selling` skill) is about building your own presence
308 and engaging with your network. They work together but require separate
309 workflows and metrics.
310 
311## Execution Artifacts
312 
313- `references/framework-notes.md` — Named frameworks and reference tables
314- `templates/output-template.md` — Deliverable shell for agent output
315- `scripts/check-output.py` — Lightweight deliverable validator
316 
317## Related Skills
318 
319- **signal-scoring**: Score and tier accounts across multiple signal sources;
320 complements social monitoring with hiring, funding, and tech stack signals
321- **lead-enrichment**: Enrich the people detected by social monitoring
322- **hiring-signal-play**: Specific play for hiring-intent signals from job boards
323- **multi-channel-outreach**: Coordinate email + LinkedIn + call after signal fires
324- **social-selling**: Build your own LinkedIn presence that generates inbound signals
325- **cold-email-strategy**: Write the signal-anchored emails that social monitoring triggers
326 

Discussion

Alternatives

Creative performance analysisDiagnose why a specific ad creative is winning or losing using the generalized hook-hold-click-convert funnel, applicable across any platform. Triggers on 'why is this ad underperforming', 'diagnose my creative', or 'where in the funnel is this ad failing'. Platform-agnostic diagnostic framework — platform-specific versions (meta-ads-creative-analytics) apply this with platform-native metrics.Coding · MITProfessional Full-Stack Developer for Network Mapping & Monitoring ApplicationAct as a professional full-stack developer tasked with building a web application for mapping and monitoring networks using Mikrotik Netwatch API. Implement multi-user role-based management to handle devices, monitor their status, and manage user subscriptions.Coding · CC0-1.0Constraint driven developmentEstablishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.Coding · MITObservability and instrumentationInstruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.Coding · MIT