← ClaudeAtlas

signal-scannerlisted

Use when searching for buying signals, detecting intent data, scoring prospect readiness, or monitoring accounts for trigger events. Triggers: 'scan for signals', 'find buying signals', 'who is ready to buy', 'intent signals', 'signal scoring', 'account signals'.
Othmane-Khadri/gtm-engineer-playbook · ★ 41 · AI & Automation · score 81
Install: claude install-skill Othmane-Khadri/gtm-engineer-playbook
# Signal Scanner Detect, score, and prioritize buying signals for target accounts. This skill searches for live signals using WebSearch, scores them on a Fit x Timing x Access x Intent framework, and produces a prioritized action list for GTM teams. ## Tools Used - **WebSearch** — find real-time signals (funding, hiring, product launches, etc.) - **Read** — load `docs/icp.md` if it exists (output from the ICP Architect skill) - **Write** — save per-company signal reports and summary - **Glob** — check for existing signal files to avoid duplicate work ## Methodology Follow these steps in order. Do not skip steps. Do not fabricate data. ### Step 1: Context Loading Check if `docs/icp.md` exists using Glob. **If it exists:** Read it. Extract ICP segments, buyer personas, and known buying signals. Summarize what you loaded so the user can confirm. **If it does not exist:** Ask the user three questions before proceeding: 1. What does your company sell? (one sentence) 2. Who is your ideal buyer? (title, company size, industry) 3. What signals indicate someone needs your solution? (list 3-5) Wait for answers. Do not assume. ### Step 2: Signal Taxonomy Present the full taxonomy of 20 signal types across 4 categories. Ask the user to select 8-12 that are most relevant to their business. Only scan for the selected signal types in Step 3. #### Company-Level Signals 1. **Fundraise announcement** — Seed, Series A, B, C+ rounds 2. **Leadership change** — New CXO, VP Sales, VP