gtm-pipeline:signal-search

Find and score buying intent signals for target companies using Parallel web search and Firecrawl crawls.

69|8|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/keinsaasforever/gtm-pipeline-skills --skill gtm-pipeline-signal-search-keinsaasforever
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gtm-pipeline:signal-search
Source: https://github.com/keinsaasforever/gtm-pipeline-skills/tree/main/skills/gtm-signal-search
Command: npx skills add https://github.com/keinsaasforever/gtm-pipeline-skills --skill gtm-pipeline-signal-search-keinsaasforever

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Sales teams waste time on cold prospects because they lack visibility into which target companies are actively showing buying intent. This Skill automates the discovery and scoring of intent signals (funding, hiring, leadership changes, product launches) so outreach focuses on companies with real, recent, attributable triggers. ## Core Features & Use Cases - Multi-source signal collection: Runs Parallel web search (always on), optional Firecrawl website crawls (native API or pre-crawled MCP pages), and optional Parallel structured enrichment for funding, hiring, and tech stack fields. - Two-axis intent scoring: Scores each signal 1-100 using an attribution gate (direct/adjacent/generic) plus offering fit, with freshness gating, domain verification, and prompt-injection hardening baked into the script. - Flexible LLM backends: Default agent backend collects raw evidence for in-context scoring with no external LLM cost; claude-cli and legacy OpenRouter backends support fully autonomous runs. - Use Case: Given a CSV of ICP-scored companies, run the skill to produce signals.csv where each company has an overallScore, scored signals with source URLs and dates, and a one-line outreach hook. ## Quick Start Ask the agent to run signal search on your client directory, for example: run signal search on the acme-gtm folder with a 2-month lookback and a test limit of 5 companies.

Frequently Asked Questions about gtm-pipeline:signal-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find buying intent signals for a list of companies?

Run the signal_search.py script with a client directory containing icp.md, offering.md, and signal_criteria.md context files plus a companies CSV. It queries Parallel web search and optionally Firecrawl, then scores each signal 1-100 into csv/intermediate/signals.csv.

What buying signals can this skill detect?

It detects funding rounds, relevant new leadership, hiring for adjacent roles, technology adoption, stated transformation projects, expansion plans, and product launches. The exact include and exclude criteria come from your signal_criteria.md file, not hardcoded rules.

Does signal search require a Firecrawl API key?

No. Firecrawl is optional and off by default. You can enable the native API route with --firecrawl and a FIRECRAWL_API_KEY, or use --firecrawl-pages-dir to read pre-crawled pages from the Firecrawl MCP with no API key needed.

Can I run signal search without paying for an external LLM?

Yes. The default agent backend is collect-only: the script gathers raw evidence per company and the calling Claude agent scores it in-context using the built-in rubric, so no OpenRouter or other third-party LLM key is required.

Why are some signals scored zero in the output?

Signals are zeroed when they fail the attribution gate (generic industry news not attributable to the company), lack a verifiable domain match, are older than the lookback window, or have no parseable source URL and date.

How much does signal search cost per company?

With the default agent backend, web search only costs roughly $0.01 per company in Parallel credits. Adding Firecrawl crawl brings it to about $0.05, and adding Parallel structured enrichment to about $0.08 per company.