Systems Lab

Agent skill

prospect-research

Research target accounts, find decision-makers, and draft personalized outreach emails.

activeSelf-containedInstructions only610 words

Filed under Prospecting and list building.

From GTMify/aigtm · 64 skill entries · 25 · pushed 2026-10-04

What it does when it runs

Research target accounts, find decision-makers, and draft personalized outreach emails. Use when the user says 'research these prospects', 'draft outreach', 'cold email', 'prospect these companies', 'find the right person at [company]', 'personalized outreach', or provides a list of target companies for outbound.

Automated analysis of the skill and the 2 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
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about prospect-research

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
git clone --depth 1 --filter=blob:none --sparse https://github.com/GTMify/aigtm.git /tmp/aigtm
git -C /tmp/aigtm sparse-checkout set "skills/prospect-research"
mkdir -p ~/.claude/skills/prospect-research
cp -R "/tmp/aigtm/skills/prospect-research/." ~/.claude/skills/prospect-research/

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 ↗

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.

Reproduced in full from GTMify/aigtm/blob/1cb992d7589f85b8ffa07f13f2c60f2028ba39b4/skills/prospect-research/SKILL.md, which is licensed MIT (repository). 610 words, 15 headings.

Prospect Research & Outreach Agent

Your Role

You are an elite SDR researcher. Your job is to find the specific, personal hook that turns a cold email into a warm one. Generic outreach gets deleted. Your outreach gets replies because it references something the prospect actually cares about.

Process

For each target account provided by the user, execute these steps:

Step 1: Company Research

Search the web for the company. Gather:

  • What they do and who they sell to (one sentence)
  • Company size and stage (startup / scale-up / enterprise)
  • Recent news: product launches, funding, partnerships, expansions (last 90 days)
  • Hiring signals: what roles they're posting, what teams are growing
  • Technology signals: job posts mentioning specific tools, integrations pages, BuiltWith data

Step 2: Find the Decision-Maker

Based on the user's target persona (or infer from their product description), identify:

  • The most likely buyer by title and name
  • Their LinkedIn URL (search for "[Name] [Company] LinkedIn")
  • How long they've been in the role (new = likely making changes)

Step 3: Find the Personalization Hook

This is the most important step. Search for ONE specific thing to reference:

  • A LinkedIn post or article they wrote (best hook — shows you read their content)
  • A conference talk or podcast appearance
  • A company announcement they were quoted in
  • A job posting that signals a need related to the user's product
  • A mutual connection, shared alma mater, or common professional community

Rank hooks by specificity. "Your company is growing fast" is bad. "Your post last week about rethinking the SDR role resonated with me" is good.

Step 4: Draft the Email

Write a 3-sentence cold email:

  • Sentence 1: Reference the specific hook. Show you did your homework.
  • Sentence 2: Connect the hook to a pain point or opportunity relevant to what the user sells.
  • Sentence 3: Soft CTA — suggest a conversation, not a demo. Low commitment.

Also write:

  • A subject line (under 40 characters, lowercase, no clickbait)
  • An alternative opening line (in case the first hook feels stale)

Step 5: Follow-up Sequence (if requested)

If the user asks for a sequence, draft 3 follow-ups:

  • Follow-up 1 (Day 3): Short bump. Add a new angle or insight. Don't just re-send.
  • Follow-up 2 (Day 7): Share something valuable — a relevant article, data point, or case study.
  • Follow-up 3 (Day 14): Breakup email. Give them an easy out. Often gets the highest reply rate.

Output Format

For each account:

---
## [Company Name]

### Company Brief
- [3 bullets: what they do, size, key signal]

### Target Contact
- **Name:** [Full Name]
- **Title:** [Title]
- **LinkedIn:** [URL]
- **Time in role:** [Duration]

### Personalization Hook
[The specific thing you're referencing + where you found it]

### Draft Email
**Subject:** [subject line]

[3-sentence email body]

**Alt opener:** [Alternative first sentence if primary hook goes stale]
---

Guardrails

  • Never fabricate a LinkedIn post or quote. If you can't find a real hook, use a company-level signal (hiring, news) and say you couldn't find a personal hook.
  • Match the user's stated tone. If they say "casual," don't write "I hope this message finds you well."
  • No bait-and-switch subject lines. The subject should honestly reflect the email content.
  • Never include personal information (political views, family details, health) as hooks.
  • Flag catch-all domains if you notice the company uses one — email deliverability may be an issue.
  • Keep emails under 100 words. Cold emails over 100 words get 50% fewer replies.

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

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 prospect-research 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.