---
name: org-signal-scanner
description: Research what's actually happening inside a target organization right now (funding, leadership change, layoffs, new program launches, press) to read the real timing behind a job posting or a client opportunity. Trigger this when the user names an organization and wants to understand "why now," recent developments, or context before applying to a role or pitching a client. Distinct from Role Strategy Analyzer, which reads a specific job posting; this skill works from the organization alone and fits both job-seeking and client-prospecting use cases.
---

# Org Signal Scanner

Reads what's happening inside an organization right now, so the user understands the moment before they apply or pitch. A job posting or a "let's talk" reply tells you almost nothing about timing on its own — this skill fills that gap with sourced, dated research.

## Workflow

1. **Get the input.** Need: the organization name, and ideally what the user is pursuing (a role, a pitch) so the "why now" read can be pointed at something specific. If missing, ask.

2. **Search recent developments (last 6-12 months).** In roughly this priority order:
   - Funding rounds, grants, or major financial news
   - Leadership departures, hires, or org restructuring
   - Layoffs or hiring freezes
   - Mergers or acquisitions
   - New program, product, or initiative launches
   - Major press coverage, positive or negative
   Prioritize primary sources — the org's own press releases, SEC filings or Form 990s where relevant, direct quotes from leadership. Use trade press or local news to fill gaps, and note explicitly when a claim comes only from a secondary source.

3. **Read the "why now."** Cross-reference the timing of what the user is pursuing against what turned up in step 2. Is this a replacement hire after a departure? A new role created by fresh funding? A team rebuilding after a layoff? Show the reasoning, not just a conclusion, and say plainly if the evidence is too thin to conclude anything.

4. **Note what should change the user's approach.** Example: an organization that just lost a major funder needs messaging that doesn't assume stability. A company that just had layoffs may be wary of anything that reads as a new expense. State this practically.

5. **Rate confidence per finding.** Multiple sources, recent, primary = well-supported. One source, older, or inferred = speculative. Never present a guess with the same confidence as a confirmed fact.

6. **Self-check before delivering:**
   - Every dated claim has a source
   - Inference is clearly separated from what a source actually stated
   - No em dashes
   - If little or nothing turned up, that's stated directly rather than padded with generic or outdated filler

## Output format

Deliver inline in chat:

- **Recent developments:** dated bullet list, each with a source
- **Read on timing ("why now"):** 2-4 sentences, reasoning shown
- **What this means for your approach:** 1-3 practical notes
- **Confidence notes:** anything speculative, flagged as such

## Notes

- Expect 6-12 searches per organization depending on public footprint.
- Works alongside Role Strategy Analyzer (which mines a specific job posting) and Decision-Maker Mapper (which finds the person) — this skill covers the organization-level "why now" that feeds both.
- Smaller or lower-visibility organizations will have thinner results; say so rather than inventing signal that isn't there.