Intent Signals logo

Intent Signals

Community
kenny589
intent-signals

Detect, categorize, and score buying intent signals from multiple data sources. Transform raw company activity into actionable outreach triggers.

Overview

Publisherkenny589
Repositorygtm-flywheel
Skill nameintent-signals
Stars
71
Forks
26
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by kenny589 on GitHub. Read the source before you install it.

Installation

Install the Intent Signals AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/kenny589/gtm-flywheel/tree/main/signal-scoring/intent-signals
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/kenny589/gtm-flywheel.git /tmp/gtm-flywheel
mkdir -p .claude/skills
cp -r /tmp/gtm-flywheel/signal-scoring/intent-signals .claude/skills/intent-signals
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Intent Signals in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Intent Signals on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Intent Signals is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Intent Signals

When to Use

  • Building signal-based outbound campaigns (vs. spray-and-pray)
  • Setting up monitoring systems for real-time prospect alerts
  • Prioritizing which accounts to contact first from a large list
  • Training SDRs or AI systems on what qualifies as a meaningful buying signal

Framework

What Intent Signals Are

An intent signal is any observable action or change that suggests a company or person may be ready to buy. It's the difference between "this company matches our ICP" (fit) and "this company matches our ICP AND is actively looking for a solution" (fit + intent).

Fit alone: "They're a 200-person SaaS company in our target industry." Fit + Intent: "They're a 200-person SaaS company that just posted 3 SDR job openings, raised a Series B last month, and their VP Sales is engaging with content about outbound scaling."

Intent signals don't guarantee a sale. They guarantee relevance — which is the single most important factor in cold outreach conversion.


The Intent Signal Taxonomy

All intent signals fall into one of four categories, each with different reliability and actionability:

Category 1: First-Party Signals (Highest Reliability)

Actions the prospect takes that directly involve your brand.

SignalReliabilityUrgencyExample
Visited your website (specific pages)Very HighHighViewed pricing page twice in one week
Downloaded your contentVery HighMedium-HighDownloaded "Outbound Playbook" guide
Attended your webinarVery HighMediumRegistered and attended live
Replied to previous outreach positivelyVery HighVery High"Not now, but reach back out in Q2"
Free trial or demo requestVery HighCritical—
Opened previous emails (multiple times)MediumMediumOpened 3 emails but didn't reply

Challenge: You need website tracking, marketing automation, and CRM data to capture these. Many companies don't have this infrastructure.

Category 2: Third-Party Intent Signals (High Reliability)

Actions the prospect takes on other platforms that suggest buying intent.

SignalReliabilityUrgencyDetection Method
Researching your category on G2/CapterraHighVery HighG2 Buyer Intent, Capterra alerts
Searching for competitor alternativesHighVery HighIntent data providers (Bombora, 6sense)
Consuming content about your problem spaceMedium-HighMediumTopic-based intent providers
Engaging with competitor contentMediumMediumSocial monitoring
Posting questions in relevant communitiesMediumMedium-HighReddit, Slack communities, forums

Challenge: Requires paid intent data subscriptions. Quality varies wildly by provider.

Category 3: Public Signals (Medium Reliability, Free)

Observable events anyone can detect with the right monitoring.

SignalReliabilityUrgencySource
Hiring signalsHighHighLinkedIn Jobs, Indeed, careers page
Funding announcementsHighMedium-HighCrunchbase, TechCrunch, press releases
Leadership changesMedium-HighMediumLinkedIn, press releases
Product launchesMediumMediumCompany blog, PR, Product Hunt
Tech stack changesMediumMedium-HighBuiltWith, Wappalyzer, job descriptions
Earnings reportsMediumLow-MediumSEC filings, press releases
Awards/recognitionLow-MediumLowIndustry publications
Conference speakingLow-MediumLowEvent websites
Office expansionMediumMediumNews, job listings in new locations
M&A activityHighMediumNews, SEC filings

Advantage: Free and widely available. These should be the backbone of any signal-based outbound strategy.

Category 4: Social Signals (Variable Reliability)

Content the prospect publishes or engages with on social platforms.

SignalReliabilityUrgencySource
Posted about a pain you solveHighHighLinkedIn, Twitter
Shared a competitor's contentMediumMediumLinkedIn, Twitter
Asked for vendor recommendationsVery HighVery HighLinkedIn, communities
Commented on industry trends related to your spaceMediumLow-MediumLinkedIn
Changed their LinkedIn headline (new role)HighHighLinkedIn notifications
Published a thought leadership piece on your topicMediumMediumLinkedIn, company blog

Signal Scoring Model

Not all signals are equal. Score each signal to prioritize outreach:

Signal Strength Matrix
FactorHigh ScoreMedium ScoreLow Score
RecencyLast 7 daysLast 30 days30-90 days
DirectnessExplicit buying action (demo request, vendor search)Implicit buying action (hiring, funding)Tangential (content consumption)
FrequencyMultiple signals in same timeframeSingle signalHistorical signal
SpecificitySpecific to your exact categoryRelated to your general spaceBroadly related
Source reliabilityFirst-party or verified third-partyPublic, verifiableInferred or aggregated
Scoring Formula
Signal Score = (Recency × 3) + (Directness × 3) + (Frequency × 2) + (Specificity × 1) + (Source × 1)

Each factor rated 1-5:

ScorePriorityAction
40-50CriticalContact within 24 hours
30-39HighContact within 3 days
20-29MediumInclude in next campaign batch
10-19LowAdd to monitoring list
Below 10NoiseIgnore

Signal Combinations (Stacking)

Single signals are useful. Signal combinations are powerful. When multiple signals converge, the probability of buying intent increases dramatically:

High-Confidence Combinations
CombinationConfidenceWhy
Funding + Hiring for target roleVery HighMoney + action = active buying cycle
Leadership change + Tech evaluation (G2)Very HighNew leader re-evaluating the stack
Hiring SDRs + Content about scaling outboundHighBuilding the function + researching solutions
Competitor churn + Your website visitVery HighActively looking for alternatives
Conference in your space + LinkedIn post about the topicMedium-HighProblem is top of mind
Signal Stacking Rules
  1. Two signals from different categories = 2x the score. A hiring signal (public) + a G2 research signal (third-party) is much stronger than two hiring signals.

  2. Recency trumps everything. A weak signal from yesterday beats a strong signal from 3 months ago.

  3. Person-level signals > Company-level signals. The VP Sales posting about outbound challenges (person) is stronger than the company posting 3 SDR jobs (company) — because you know exactly WHO is feeling the pain.

  4. Don't stack noise. Three weak signals don't equal one strong signal. "Posted on LinkedIn" + "website has a blog" + "company is in tech" = noise, not intent.


Building a Signal Monitoring System

Manual Monitoring (0 cost, 30 min/day)
ActivityFrequencyTool
Check LinkedIn for job postings at target accountsDailyLinkedIn Jobs search, saved searches
Monitor Crunchbase for funding in your verticalsWeeklyCrunchbase alerts (free tier)
Track LinkedIn posts from target personasDailyLinkedIn feed, saved searches
Check Google Alerts for target companiesDailyGoogle Alerts (free)
Scan industry communities for vendor questionsWeeklyReddit, Slack groups, forums
Automated Monitoring (Paid tools)
Tool CategoryExamplesWhat It Monitors
Intent dataBombora, 6sense, ZoomInfo IntentCategory-level research signals
Job monitoringLinkedIn Recruiter, Otta, PredictLeadsHiring signals
Funding alertsCrunchbase Pro, PitchBookCapital events
Tech detectionBuiltWith, Wappalyzer, HG InsightsStack changes
Social monitoringMention, Brand24, PhantomBusterSocial signals
Website trackingClearbit Reveal, RB2B, LeadfeederWebsite visit signals
Signal Pipeline Architecture
Data Sources (APIs, scraping, alerts)
    ↓
Signal Detection Layer
    → Parse raw data for relevant signals
    → Categorize (hiring, funding, tech, social, first-party)
    ↓
Scoring Engine
    → Apply signal scoring formula
    → Stack multiple signals per account
    → Calculate composite score
    ↓
Prioritization Queue
    → Tier 1 (score 40+): Immediate outreach
    → Tier 2 (score 30-39): Next batch
    → Tier 3 (score 20-29): Add to campaign
    → Below 20: Monitor or discard
    ↓
Outreach Trigger
    → Route to appropriate campaign
    → Match signal to personalization angle
    → Enrich contact data if needed

Signal-to-Message Mapping

Every signal should map to a specific outreach angle:

SignalOpening Line ApproachCampaign Angle
Hiring SDRs"Building the outbound team?"Scaling outbound
Series B funding"Post-Series B is when pipeline becomes a board metric"Growth acceleration
New VP Sales"First 90 days in a new VP Sales role..."New leader priorities
Competitor evaluation"Evaluating {{category}}? Here's what teams miss"Competitive displacement
Tech stack change"Migrating to {{tool}} — most teams also rethink..."Stack optimization
LinkedIn post about pain"Your post about {{topic}} resonated"Thought leadership bridge
Conference attendance"Ahead of {{event}}, thought you'd find this relevant"Event-based relevance

Templates

Signal Tracking Sheet

| Company | Signal Type | Signal Detail | Date Detected | Source | Score | Action | Status |
|---------|------------|--------------|---------------|--------|-------|--------|--------|
| ___ | ___ | ___ | ___ | ___ | ___/50 | ___ | ___ |

Signal-Based Campaign Brief

Campaign: {{campaignName}}
Target Signal: {{primarySignal}}
Supporting Signals: {{secondarySignals}}

Signal Detection:
- Source: {{dataSource}}
- Refresh frequency: {{howOften}}
- Estimated volume: {{leadsPerWeek}}

Personalization Map:
- Opening line template: "___"
- Value prop connection: "___"
- CTA: "___"

Qualification Threshold:
- Minimum signal score: ___
- Required firmographic fit: ___
- Maximum signal age: ___ days

Tips

  • The best time to email someone is within 48 hours of a signal firing. After 2 weeks, the signal is stale and your "I noticed..." line sounds like a lie.
  • Don't chase every signal. Pick 2-3 signal types that correlate with your highest close rates and build systematic monitoring around just those. Depth beats breadth.
  • Hiring signals are the single most reliable free signal for B2B outbound. If a company is hiring for the role your product serves, they are actively investing in that function.
  • Person-level signals always beat company-level signals. "The VP Sales posted about needing better pipeline visibility" is 10x more actionable than "the company raised a round."
  • Create a feedback loop: track which signal types lead to the most meetings. After 3 months, double down on the winners and drop the losers.
  • Signal + fit > fit alone > signal alone. A perfectly matched ICP company with intent signals is your #1 priority. A perfectly matched ICP company with no signals is Tier 2. A non-ICP company with signals is usually noise — don't chase it.

Progressive disclosure: load signal provider integrations and API configurations only when setting up monitoring for a specific campaign.

Frequently asked questions

What does the Intent Signals AI skill do?

Detect, categorize, and score buying intent signals from multiple data sources. Transform raw company activity into actionable outreach triggers.

Why use Intent Signals on TypingMind?

Because you install it once and use it with any model. Intent Signals is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Intent Signals in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/kenny589/gtm-flywheel/tree/main/signal-scoring/intent-signals. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Intent Signals?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Intent Signals?

As many as you like. As long as a model supports skills, you can use Intent Signals with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Intent Signals AI skill free?

Yes. It is published on GitHub by kenny589 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇