Systems Lab

Agent skill

signal-detection

Detect and prioritize buying-intent signals (funding, hiring, tech changes, job changes, news) and map each to a concrete ColdIQ marketplace endpoint.

activeSelf-containedInstructions only654 words

Filed under Prospecting and list building.

From Cold-IQ/coldiq-marketplace-skills · 17 skill entries · 1 · pushed 2026-09-22

What it does when it runs

Detect and prioritize buying-intent signals (funding, hiring, tech changes, job changes, news) and map each to a concrete ColdIQ marketplace endpoint. Use when deciding which intent signals to track for a client, sourcing funding/hiring/acquisition/job-change signals, scoring accounts by signal strength, deciding outreach timing from signal freshness, or stacking signals. Triggers on "intent signals", "buying signals", "trigger events", "funding signal", "hiring signal", "job change", "tech stack change", "signal detection", "when to reach out", "signal stacking". Do NOT use for writing the copy that references the signal (see crawford-method / cold-email-copy), list scoring math (see tam-scoring), or generic search (see coldiq-search-enrich).

Automated analysis of the skill and the 0 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-detection

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/Cold-IQ/coldiq-marketplace-skills.git /tmp/coldiq-marketplace-skills
git -C /tmp/coldiq-marketplace-skills sparse-checkout set "skills/signal-detection"
mkdir -p ~/.claude/skills/signal-detection
cp -R "/tmp/coldiq-marketplace-skills/skills/signal-detection/." ~/.claude/skills/signal-detection/

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 ↗

Or take the whole library

This repo ships a .claude-plugin manifest, so Claude Code can install all 17 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.

/plugin marketplace add Cold-IQ/coldiq-marketplace-skills
/plugin

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 Cold-IQ/coldiq-marketplace-skills/blob/495c1b4256db8c6683ac1ff59a093899228eca73/skills/signal-detection/SKILL.md, which is licensed MIT (repository). 654 words, 8 headings.

Signal Detection

30 sales triggers across 6 categories, tiered by reliability, each mapped to the ColdIQ endpoint that surfaces it. Blend ≥2 independent signals before high-effort plays.

Where a signal is detectable, this skill routes it to a ColdIQ marketplace endpoint; the rest stay as research guidance.

ColdIQ Marketplace Endpoints

SignalMethodPathCreditsEndpoint IDNotes
Funding eventsGET/v1/signalbase/funding-signalsunknownsignalbase.funding_signalsSeries A+ / rounds
Acquisition / M&AGET/v1/signalbase/acquisition-signalsunknownsignalbase.acquisition_signals
Job changes (champion moves)GET/v1/signalbase/job-change-signalsunknownsignalbase.job_change_signalsRole-aware
Hiring surgeGET/v1/signalbase/hiring-signalsunknownsignalbase.hiring_signalsOpen postings
Company jobs (one company)POST/v1/limadata/jobs2limadata.jobsLinkedIn jobs for a page
Financing events (alt source)GET/v1/predictleads/discover/financing_events0.18predictleads.discover.financing_events
Job openings (alt source)GET/v1/predictleads/discover/job_openings0.18predictleads.discover.job_openingsBy O*NET / location
News eventsGET/v1/predictleads/discover/news_events0.18predictleads.discover.news_events
Tech adoption / removalGET/v1/predictleads/companies/{companyIdOrDomain}/technology_detections0.18predictleads.company.technology_detections
Buying intent (job + tech)POST/v1/theirstack/companies/buying_intents3theirstack.companies.buying_intents
LinkedIn post engagementPOST/v1/limadata/posts/reactions2limadata.posts.reactionsWarm-engager lists
News / ads (general)POST/v1/serper/newsunknownserper.newsCheap catch-all

Reliability tiers

  • Tier 1 — highest intent (same-day): Series A+ funding, expansion into new market, leadership change in the buyer's department. Budget approved or imminent. → GET /v1/signalbase/funding-signals · ? cr · signalbase.funding_signals (unverified)
  • Tier 2 — strong (30–90d): competitor tech adoption, partnership/acquisition, hiring surge (5+). → GET /v1/signalbase/hiring-signals · ? cr · signalbase.hiring_signals (unverified)
  • Tier 3 — moderate (nurture): 1–3 job postings, award/recognition, product launch. → GET /v1/predictleads/discover/job_openings · 0.18 cr · predictleads.discover.job_openings
  • Tier 4 — weak (context only): social activity, traffic spikes, general news. → POST /v1/serper/news · ? cr · serper.news (unverified)

The 30 triggers → where to source them

  • Funding & financial: Series A+ (signalbase.funding_signals), M&A (signalbase.acquisition_signals), financing events (predictleads.discover.financing_events).
  • Hiring & team: new exec / champion move (signalbase.job_change_signals), hiring surge (signalbase.hiring_signals), SDR/BDR or dept expansion (limadata.jobs, predictleads.discover.job_openings).
  • Technology & digital: new tech adoption / stack removal (predictleads.company.technology_detections), buying intent (theirstack.companies.buying_intents), running ads / launches (serper.news).
  • Competitive & vendor: competitor reviews / contract expiry / comparison shopping — no native endpoint; use serper.news / predictleads.discover.news_events as proxies.
  • Product & business events: geographic expansion, new office, partnership, regulatory change (predictleads.discover.news_events, serper.news).
  • Marketing & reputation: LinkedIn post engagement (limadata.posts.reactions), PR/media mention (serper.news).

Freshness windows (outreach timing)

Funding 90d (weeks 2–8) · Series C deployment 180d (weeks 5–12) · LinkedIn posts 30d (0–7d) · hiring 60d (14–30d) · new exec 90d (days 14–30) · tech change 60d (0–30d) · champion job change 30d (0–14d, fastest decay) · event attendance 21d (±7d).

Multi-signal stacking

  • T1 + T1 = white-glove (immediate): funding + hiring surge; new exec + tech removal; champion job change + ICP fit.
  • T2 + T2 = priority sequence: hiring (1–3) + LinkedIn engagement; competitor review + your pricing-page visit; industry-news impact + geographic expansion.
  • T3 = templated nurture.

"So what?" test for copy

Every signal you reference must be: recent, connected to your offer, something they'd care that you noticed, tied to a specific pain. Go deeper than the obvious — "hiring SDRs but no rev-ops lead yet" beats "you're hiring SDRs". Hand off to crawford-method for the actual opener.

Tips

  • Automate Tier 1 with same-day triggers (/v1/limadata/watch); batch Tier 3–4 weekly.
  • Cheapest source first: serper.news / predictleads.* (0.18) before 3-credit intent calls.
  • Track signal→meeting conversion, not detection volume.

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-detection 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.