Skip to main content
ClaudeWave
Skill52 estrellas del repoactualizado 3mo ago

signal-scanner

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

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/Othmane-Khadri/gtm-engineer-playbook /tmp/signal-scanner && cp -r /tmp/signal-scanner/.claude/skills/gtm-playbook/signal-scanner ~/.claude/skills/signal-scanner
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# 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 Marketing, Head of Growth
3. **Hiring pattern** — SDR hiring spree, GTM engineering roles, marketing hires
4. **Product launch** — Major feature release, new product line, GA announcement
5. **Partnership or integration** — New tech partner, channel partner, integration announcement
6. **Tech stack change** — Detected via job postings, BuiltWith, Wappalyzer, or press releases
7. **Office expansion** — New market entry, new office location, international expansion
8. **Pricing change** — New tier launch, pricing model shift, free tier added/removed

#### Engagement Signals
9. **Website visit** — If tracking pixel is deployed (user must confirm)
10. **Content download or webinar attendance** — Known engagement with your content
11. **G2/Capterra review activity** — Wrote a review of a competitor product
12. **Community activity spike** — Mentions on Reddit, LinkedIn, Slack, or forums about your problem space
13. **Email engagement** — Opens, clicks, replies on existing sequences (user must confirm)

#### Market Signals
14. **Competitor customer churn** — Switching signals, public complaints, cancellation posts
15. **Industry regulation change** — New compliance requirement that creates demand
16. **Market event or conference** — Speaking at or attending events in your space
17. **Competitor funding or acquisition** — Creates urgency or uncertainty for their customers

#### Behavioral Signals
18. **Job posting pattern shift** — New role types signal new priorities (e.g., first "Head of AI" hire)
19. **Social selling activity** — Prospect sharing or engaging with content about your problem space
20. **Direct inquiry or demo request** — Inbound interest (user must confirm)

**Ask the user:** "Which of these 20 signal types are most relevant to your business? Select 8-12 by number."

Wait for their selection before proceeding.

### Step 3: Live Signal Scan

Ask the user to provide 1-5 target company names.

For each company, run WebSearch queries for every selected signal type. Use these search patterns:

| Signal Type | Search Queries |
|---|---|
| Fundraise | `"[company] funding"`, `"[company] series"`, `"[company] raises"` |
| Leadership change | `"[company] hires"`, `"[company] appoints"`, `"[company] new CXO/VP"` |
| Hiring pattern | `"[company] careers"`, `"[company] hiring"`, search for their jobs page |
| Product launch | `"[company] launches"`, `"[company] announces"`, `"[company] new feature"` |
| Partnership | `"[company] partners with"`, `"[company] integrates"`, `"[company] integration"` |
| Tech stack change | `"[company] tech stack"`, `"[company] migrates to"`, check job postings for tech requirements |
| Office expansion | `"[company] opens office"`, `"[company] expands to"` |
| Pricing change | `"[company] pricing"`, `"[company] new plan"` |
| G2/Capterra reviews | `"[company] vs [competitor] G2"`, `site:g2.com [company]` |
| Community activity | `"[company] reddit"`, `"[company] [problem-space-keyword]"` |
| Competitor churn | `"switching from [competitor] to"`, `"[competitor] alternative"`, `"leaving [competitor]"` |
| Regulation change | `"[industry] regulation 2026"`, `"[industry] compliance new"` |
| Conference attendance | `"[company] [conference-name]"`, `"[company] speaks at"` |
| Competitor funding | `"[competitor] acquired"`, `"[competitor] funding"` |
| Job posting shift | `"[company] job openings"`, `"[company] head of [role]"` |
| Social selling | `"[decision-maker-name] [problem-space-keyword]"` |

**Rules for this step:**
- Use WebSearch to find REAL signals. Never fabricate data.
- If WebSearch returns nothing for a signal type, record "No signal detected" for that type. Do not invent results.
- Only search within the last 90 days unless the user specifies a different window.
- Record each signal found with: **type**, **date** (as specific as possible), **source URL**, and **details** (one sentence).

### Step 4: Signal Scoring (Fit x Timing x Access x Intent)

Score each company on four dimensions. Each dimension is rated 1-5.

#### Fit (1-5) — How well does this company match the ICP?
| Score | Criteria |
|---|---|
| 5 | Perfect match: right size, industry, stage, and budget |
| 4 | Strong match: 3 of 4 criteria met |
| 3 | Partial match: 2 of 4 criteria met |
| 2 | Weak match: 1 criterion met |
| 1 | No match or insufficient data |

#### Timing (1-5) — How recent/urgent is the strongest signal?
| Score | Criteria |
|---|---|
| 5 | Signal detected in the last 7 days |
| 4 | Signal detect
account-research-briefSkill

Use when preparing to engage a target account, researching a company before outreach, or building pre-call intelligence. Triggers: 'research this company', 'account brief for [company]', 'company research', 'what do I need to know about [company]', 'pre-outreach research'.

agent-architecture-plannerSkill

Use when designing an autonomous agent, planning agent architecture, building a scheduled automation, or creating a Claude Code agent workflow. Triggers: 'design an agent', 'build an automation', 'agent architecture', 'automate this workflow', 'create a scheduled agent', 'shell script agent'.

competitive-battlecard-generatorSkill

Use when analyzing competitors, creating sales battlecards, building competitive positioning, preparing for competitive deals, or updating competitive intelligence. Triggers: 'battlecard for [competitor]', 'competitive analysis of [competitor]', 'how do we beat [competitor]', 'compare us to [competitor]', 'competitive intel', 'win against [competitor]'.

crm-hygiene-scannerSkill

Use when auditing CRM data quality, finding duplicate records, identifying stale leads, cleaning pipeline data, or improving data hygiene. Triggers: 'clean my CRM', 'audit CRM data', 'find duplicates', 'CRM hygiene', 'data quality check', 'stale leads', 'pipeline cleanup'.

icp-architectSkill

Use when building or refining an Ideal Customer Profile (ICP), defining target personas, mapping buyer psychographics, or discovering where prospects gather online. Triggers: 'build my ICP', 'define target customer', 'who should I sell to', 'refine ICP', 'persona mapping'.

meeting-prep-briefSkill

Use when preparing for a sales meeting, discovery call, demo, or customer check-in. Triggers: 'prep me for a meeting with [company]', 'meeting brief for [company]', 'pre-call prep', 'I have a call with [contact] at [company]', 'meeting prep', 'call prep'.

outreach-sequence-builderSkill

Use when creating outreach sequences, writing cold email campaigns, building multi-channel cadences, designing follow-up flows, or crafting signal-triggered messages. Triggers: 'build an outreach sequence', 'write a cold email sequence', 'create a cadence', 'outreach for [signal]', 'email sequence', 'follow-up sequence', 'multi-channel outreach'.

qualification-scorerSkill

Use when scoring leads, qualifying prospects, prioritizing pipeline, deciding which accounts to pursue, or building a lead scoring model. Triggers: 'score this lead', 'qualify this prospect', 'is this a good lead', 'lead scoring', 'prioritize my pipeline', 'qualification framework'.