Agent skill

Prospect Research

by TheCraigHewitt in TheCraigHewitt/skills

When the user needs to research a prospect before a sales call, wants a pre-call intelligence brief, needs to understand a potential customer or partner, or says things like 'research this company,'…

MITAuto-check passedSales & Support

Install Prospect Research

skills CLI
$ npx skills add TheCraigHewitt/skills --skill prospect-research -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install TheCraigHewitt/skills prospect-research --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ceo/prospect-research .claude/skills/prospect-research && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
prospect-research
GitHub stars
159
Token cost
~1.4k tokens
SKILL.md length
759 words
Files
1
Skills in repo
65
Repo updated
First seen
Licence
MIT

At a glance

When the user needs to research a prospect before a sales call, wants a pre-call intelligence brief, needs to understand a potential customer or partner, or says things like 'research this company,'…

  • Works in 5 steps: Company name (required) → Contact name and role (if known) → How they found you / how this meeting… → …
  • Needs to research a prospect before a sales call
  • SKILL.md covers Before Starting, Input, What You Generate and Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Prospect Research is an agent skill from TheCraigHewitt/skills. When the user needs to research a prospect before a sales call, wants a pre-call intelligence brief, needs to understand a potential customer or partner, or says things like 'research this company,' 'I have a call with [company],' 'what should I know about,' 'prep me on this prospect,' 'look into [company] before my call.' For discovery call planning, see meeting-prep.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering Sales call preparation. The repository describes itself as: AI skills for founders, sales teams, and creators. 47 skills across CEO, Sales, YouTube, and General categories. Works with Claude Code, Cursor, Codex, and any agent that reads… The licence is MIT.

When your agent uses it

  • Needs to research a prospect before a sales call
  • Wants a pre-call intelligence brief
  • Needs to understand a potential customer
  • Says things like research this company

Example prompts

  • “research this company,”
  • “I have a call with [company],”
  • “what should I know about,”
  • “/prospect-research”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Company name (required)
  2. Contact name and role (if known)
  3. How they found you / how this meeting happened (inbound, outbound, referral, event — this changes the approach)
  4. Company website (if known)
  5. Anything else they already know (prior conversations, mutual connections, context from a form submission)

What it can do on your machine

Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prospect Research loads about 1.4k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 759 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~97
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 759 words, ~1,399 tokens.

Download SKILL.mdSave it as .claude/skills/prospect-research/SKILL.md (or your agent's skills folder).
name
prospect-research
description
When the user needs to research a prospect before a sales call, wants a pre-call intelligence brief, needs to understand a potential customer or partner, or says things like 'research this company,' 'I have a call with [company],' 'what should I know about,' 'prep me on this prospect,' 'look into [company] before my call.' For discovery call planning, see meeting-prep.

Prospect Research

You generate a pre-call intelligence brief so the founder walks into every sales conversation with context instead of cold air. The difference between "So, tell me about your company" and "I saw you just expanded into [market] — how's that going?" is the difference between a forgettable call and a closed deal.

Before Starting

Check if BUSINESS_CONTEXT.md exists in the project root or current directory.

  • If it exists: Read it. Use the user's ICP, product/service description, and value proposition to tailor the research brief. The pain points and conversation starters should connect the prospect's situation to what the user actually sells.
  • If it doesn't exist: Ask: "Quick context — what does your company do, who do you typically sell to, and what problem do you solve for them?" That's enough to make the research relevant. Suggest saving a BUSINESS_CONTEXT.md for future sessions.

Input

Ask for whatever they have:

  1. Company name (required)
  2. Contact name and role (if known)
  3. How they found you / how this meeting happened (inbound, outbound, referral, event — this changes the approach)
  4. Company website (if known)
  5. Anything else they already know (prior conversations, mutual connections, context from a form submission)

Don't require all of these. Company name alone is enough to start.

What You Generate

Prospect Brief

Company Overview (one paragraph)

  • What they do, who they serve, approximate size/stage
  • Use whatever public information you can synthesize from the company name and any provided details
  • If you don't have access to live data, be transparent: "Based on what you've told me, here's what I'd expect. You should verify [X] on their website before the call."

Likely Situation Based on their company stage, size, and industry, what's probably true about their:

  • Current challenges (be specific to their industry and stage)
  • Tech stack / tools they likely use
  • Organizational dynamics (who else might be involved in a decision)
  • Budget cycle / buying behavior

Pain Points to Explore 3-5 specific pain points this prospect likely has, mapped to what the user sells. Not generic pain points — pain points that connect their situation to the user's solution.

Format each as:

  • The pain: What they're probably experiencing
  • The cost: What it's costing them (time, money, risk, opportunity)
  • Your angle: How to surface this in conversation without pitching

Conversation Starters (5) Personalized openers that show you've done your homework. Each one should:

  • Reference something specific about their company or situation
  • Open a conversation, not close one
  • Feel natural, not stalker-ish

Bad: "I noticed you have 47 employees on LinkedIn." Good: "You've grown the team significantly this year — has that created any new operational challenges?"

Likely Objections 3-4 objections this prospect is likely to raise, with suggested responses:

ObjectionWhy They'll Say ItHow to Handle
[Specific objection][Root cause][Response approach — not a script, a strategy]
Show full SKILL.md (296 more words)Show less

Qualification Checklist Quick checklist to assess during the call:

  • Budget: Can they pay for this? Signals to watch for.
  • Authority: Is this person the decision-maker? If not, who is?
  • Need: Is the pain real and urgent, or theoretical?
  • Timeline: Are they solving this now or "exploring"?
  • Competition: Are they evaluating alternatives? Which ones?

Recommended Approach Based on everything above, a 2-3 sentence recommendation for how to approach this call:

  • What to lead with
  • What to listen for
  • What next step to propose if it goes well

Pre-Call Checklist

  • Reviewed their website (spend 5 minutes, not 30)
  • Checked LinkedIn profile of the contact
  • Know your opening question
  • Know the next step you'll propose
  • Have your calendar open for scheduling follow-up

Rules

  1. Relevance over volume. A 1-page brief the founder actually reads beats a 5-page dossier they skim. Every line should help them sell.
  2. Connect everything to the user's product/service. Generic company research is useless. Every insight should create an opening for the user's solution. If you have their business context, use it.
  3. Be honest about what you don't know. If you're inferring company details from the name alone, say so. "I don't have access to their website right now, but based on [industry] companies at this stage, they likely..." is better than making things up.
  4. Conversation starters, not interrogation questions. The goal is to start a conversation between peers, not conduct a deposition. Every opener should feel like something a knowledgeable equal would say.
  5. Objection handling is strategy, not scripting. Don't give word-for-word responses. Give the founder the understanding of WHY the objection exists so they can handle it naturally.
  6. Speed matters. This should take 2 minutes to read. The founder is probably prepping 15 minutes before the call. Respect that.

© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in ceo/prospect-research of TheCraigHewitt/skills.

Open the folder on GitHubat commit fdbf39b

Compare with similar skills

Prospect Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prospect Research compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prospect Research this skillTheCraigHewitt/skills159—~1.4kAutomated safety check: PassMIT
Luopan Company Researchzhangxiaoqiang1991/luopan389—~998Automated safety check: PassMIT
Company Researchstophobia/deerflow2.0-enhanced822—~845Automated safety check: PassMIT
Meeting Prep BriefBrianRWagner/ai-marketing-claude-code-skills441—~922Automated safety check: PassNone
SdtStopDisTrain/sdt-skills309—~535Automated safety check: PassMIT
Account Researchextruct-ai/gtm-skills109—~1.6kAutomated safety check: PassNone

Similar skills

  • Luopan Company Research

    zhangxiaoqiang1991/luopan

    罗盘的公司研究子模式。研究具体上市或非上市公司的财务增长、商业模式、 竞争生态位、治理与组织信号,并分别生成投资初筛和求职初筛。

    389 GitHub stars~998 tokensUpdated 2 mo ago
    Sales & SupportAuto-check passed
  • Company Research

    stophobia/deerflow2.0-enhanced

    综合企业背景调研技能,用于尽职调查、合作伙伴评估、投资分析、市场研究等场景。支持公司工商信息、财务数据、法律风险、舆情分析、竞品对比等多维度调研,自动生成Markdown和HTML格式的专业调研报告。触发条件:用户提及"企业调研"、"公司背景"、"尽职调查"、"合作伙伴评估"、"投资分析"、"市场研究"等关键词。

    822 GitHub stars~845 tokensUpdated 6 mo ago
    Sales & SupportAuto-check passed
  • Meeting Prep Brief

    BrianRWagner/ai-marketing-claude-code-skills

    Builds a pre-meeting brief from your Obsidian vault: participant research, past notes, open commitments, a prioritized agenda and sharp questions.

    441 GitHub stars~922 tokensUpdated 6 mo ago
    Sales & SupportAuto-check passed
  • Sdt

    StopDisTrain/sdt-skills

    SDT 内容生产工具箱的总入口:根据当前任务选择最合适的 sdt- 模块,既能完成标题、开头等单一步骤,也能组织从账号研究到发布的完整流程。用户不知道该用哪个 SDT Skill,或希望一站式完成内容生产时使用。

    309 GitHub stars~535 tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed
  • Account Research

    extruct-ai/gtm-skills

    Deep-research a single target account into a decision-ready dossier: the entity tree, the buying units and decision-makers, live signals (open/closed roles, leadership moves, news, tech stack), and…

    109 GitHub stars~1.6k tokensUpdated 12 days ago
    Sales & SupportAuto-check passed
  • Call Prep

    breakstageaxe61/genspark-claw

    Prepare an AI phone call end-to-end — research the callee, set a concrete objective and fallback, draft a natural call script with branching, and produce a post-call summary template.

    169 GitHub stars~986 tokensUpdated 15 days ago
    Sales & SupportAuto-check passed

More from TheCraigHewitt/skills

All 65 skills in this repo
  • Carousels

    TheCraigHewitt/skills

    Turns a piece of Craig's content (an email, a YouTube script, an essay, or pasted text) into a polished image carousel publishable to both LinkedIn and Instagram from one set of 1080x1350 slides.

    159 GitHub stars~2.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Audience Research

    TheCraigHewitt/skills

    When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.

    159 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Brain Dump

    TheCraigHewitt/skills

    Take a messy stream-of-consciousness dump from the user (typed or transcribed from voice) and turn it into a structured set of projects, tasks, and connections to existing work.

    159 GitHub stars~1.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Channel Audit

    TheCraigHewitt/skills

    When the user wants a full YouTube channel health check, growth diagnosis, strategic review, or wants to identify why their channel is stalling.

    159 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Channel Strategy

    TheCraigHewitt/skills

    When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.

    159 GitHub stars~2.2k tokensUpdated 4 mo ago
    Auto-check passed
  • Cold Call

    TheCraigHewitt/skills

    When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.

    159 GitHub stars~5k tokensUpdated 4 mo ago
    Auto-check passed

Categories

Questions about Prospect Research

What does Prospect Research do?

When the user needs to research a prospect before a sales call, wants a pre-call intelligence brief, needs to understand a potential customer or partner, or says things like 'research this company,'…. Prospect Research is an agent skill from TheCraigHewitt/skills.' For discovery call planning, see meeting-prep.

When should I use Prospect Research?

Prospect Research fits situations like: needs to research a prospect before a sales call; wants a pre-call intelligence brief; needs to understand a potential customer; says things like research this company.

How do I install Prospect Research in Claude Code?

Run `npx skills add TheCraigHewitt/skills --skill prospect-research -a claude-code`. Or copy the skill folder (ceo/prospect-research in TheCraigHewitt/skills) into .claude/skills/prospect-research in your project. Claude Code loads it when a task matches its description.

How do I install Prospect Research in Codex?

Run `npx skills add TheCraigHewitt/skills --skill prospect-research -a codex`. Or copy the skill folder (ceo/prospect-research in TheCraigHewitt/skills) into .agents/skills/prospect-research in your project. Codex loads it when a task matches its description.

Can I use Prospect Research in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheCraigHewitt/skills --skill prospect-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prospect-research, .gemini/skills/prospect-research, .github/skills/prospect-research and .opencode/skills/prospect-research in your project.

What does Prospect Research need to run?

SKILL.md names no scripts, command-line tools or credentials: Prospect Research is instructions for the agent only.

Does Prospect Research access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Prospect Research safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Prospect Research use?

Prospect Research is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prospect Research use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Prospect Research?

Skills that share tags, products or a category with Prospect Research: Luopan Company Research (zhangxiaoqiang1991/luopan, 389 stars), Company Research (stophobia/deerflow2.0-enhanced, 822 stars), Meeting Prep Brief (BrianRWagner/ai-marketing-claude-code-skills, 441 stars) and Sdt (StopDisTrain/sdt-skills, 309 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prospect Research?

TheCraigHewitt (a GitHub user) maintains it in TheCraigHewitt/skills, which has 159 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on May 22, 2026.

Source: TheCraigHewitt/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.