Systems Lab

Agent skill

psp-signal-hunt

Surface 5-10 public, recent, verifiable signals worth hunting for a given ICP segment.

activeSelf-containedDeclared tools487 words

Filed under Prospecting and list building.

From cmj-hub/claude-psp · 5 skills · 2 · pushed 2026-09-09

What it does when it runs

Surface 5-10 public, recent, verifiable signals worth hunting for a given ICP segment. Catalogs signal types (hiring, funding, leadership, product, pivot, content) and proposes operational sources + cadence to track each. Loaded by the main psp skill when the user wants to find what signals to hunt.

Read from 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
  • Read
  • WebFetch
  • -
  • Grep
Actions present in the files
network

Ask about psp-signal-hunt

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

Install it

View source on GitHub ↗
git clone --depth 1 --filter=blob:none --sparse https://github.com/cmj-hub/claude-psp.git /tmp/claude-psp
git -C /tmp/claude-psp sparse-checkout set "skills/psp-signal-hunt"
mkdir -p ~/.claude/skills/psp-signal-hunt
cp -R "/tmp/claude-psp/skills/psp-signal-hunt/." ~/.claude/skills/psp-signal-hunt/

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 5 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.

/plugin marketplace add cmj-hub/claude-psp
/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.

The skill

Source on GitHub ↗

Reproduced in full from cmj-hub/claude-psp/blob/970cb1702ffdf35663b81946f64f46aa30507cf5/skills/psp-signal-hunt/SKILL.md, which is licensed MIT (skill frontmatter). 487 words, 12 headings.

PSP Signal Hunt — sub-skill

Loaded by psp when the user wants to identify what signals to track for a specific ICP segment.

Activation

The main psp skill routes here on:

  • "What signals should we hunt for <ICP>"
  • "Find signals for <segment>"
  • "Signal hunt"

Signal taxonomy

The skill produces signal candidates across 6 categories:

CategoryExamples
HiringSpecific role open ≤30 days; team size jump; first-of-kind hire (first SDR, first VP)
FundingRound announced ≤30 days; secondary; bridge; ARR milestone
LeadershipNew C-level / VP ≤60 days; departure; board change
ProductNew tier / pricing change / feature launch / public roadmap ≤45 days
PivotWebsite hero rewrite; positioning shift; rebrand; new ICP language
ContentPodcast / panel / public talk on the relevant pain ≤30 days

Workflow

1. Take the ICP segment

The user provides a specific ICP (e.g. "Series-B SaaS, $20-50M ARR, PLG motion"). If they're vague, ask for precision before continuing.

2. Generate 5-10 candidate signals

For each candidate, output:

  • Signal type (from the 6 categories)
  • What to look for (specific shape — e.g. "Demand Gen Lead role posted ≤14 days")
  • Where to find it (LinkedIn / Crunchbase / RSS / podcast feeds / their own blog)
  • Cadence (daily / weekly / event-driven)
  • Why this signal implies operational pain for this ICP

3. Rank by hunting feasibility

Rank the 5-10 candidates by:

  • Volume: how many target companies show this signal monthly
  • Specificity: how directly it implies actionable pain
  • Effort: how hard to operationalize the hunt

4. Output

# Signal hunt — <ICP segment>

| # | Signal | Where | Cadence | Pain implied | Volume |
|---|---|---|---|---|---|
| 1 | Demand Gen Lead role posted ≤14d | LinkedIn job search + RSS | Daily | Pipeline gap | ~15-30/mo |
| 2 | Series B announced ≤30d | Crunchbase API + CB Insights newsletter | Weekly | 3x revenue mandate | ~5-10/mo |
| 3 | New CMO ≤60d | LinkedIn search + The Org | Weekly | 90-day GTM stack review | ~3-8/mo |
| 4 | ... | ... | ... | ... | ... |

## Recommended hunt stack
1. **Daily**: LinkedIn job posts (manual or via Phantombuster)
2. **Weekly**: Crunchbase + The Org
3. **Event-driven**: Podcast RSS for relevant shows

## Operational notes
- Capture signal date so freshness is enforced
- Tag each signal with the implied pain at capture time
- Stale signals (>45 days for hiring, >30 days for funding) drop from outreach queue

5. Hand off

Once signals are picked, hand to:

  • claude-cold-email → first-line opener uses Signal verbatim
  • claude-psp psp-construct → map each signal to a felt pain

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 psp-signal-hunt 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.