ICP builder
You need to define or sharpen an ideal customer profile (ICP) for B2B sales: starting outbound, the reply rate is low, the pipeline is full of…
You get One-page ICP · Disqualifiers · List-building filters
Use this for one person you are about to contact or meet. It produces a brief a rep can read in 60 seconds and a first line that proves the message was written for them.
Use it when you need to research a specific person before reaching out or meeting them.
“Research Priya Shah, VP Revenue at Lumen. Write an email and a LinkedIn opener.”
What happens when you ask your agent with this skill installed. Every step below comes straight from the skill.
Research Priya Shah, VP Revenue at Lumen. Write an email and a LinkedIn opener.
prospect-research-briefReady for your review. Nothing is sent or changed until you approve.
What good looks like
What you bring
What you get
Use this for one person you are about to contact or meet. It produces a brief a rep can read in 60 seconds and a first line that proves the message was written for them.
Check they still work at the company and in the role. Roughly one in five B2B contacts changes jobs each year; a brief about the wrong job is wasted.
Score each hook on two questions: is it specific to this person, and does it connect to the problem you solve? Keep only hooks that pass both. Read references/hook-ranking.md for the ranking grid and examples of strong and weak hooks.
One for email, one for LinkedIn. One or two sentences each, built from the strongest hook, ending in a natural bridge to the problem, not to your product.
Person: <name> - <title> at <company> - <tenure in role>
Confirmed current: yes/no (source)
Measured on: <likely metrics for the role>
What they talk about: <2-3 themes with links>
Hooks (ranked):
1. <hook> - <source> - <why it connects>
2. ...
Email opener: <1-2 sentences>
LinkedIn opener: <1-2 sentences, more conversational>
Avoid: <topics or claims to stay away from>
| Connects to your problem | Does not connect | |
|---|---|---|
| Specific to the person | Use it. Lead with it. | Use only as a light aside, never as the opener. |
| Generic (role or company level) | Use when nothing better exists. | Drop it. |
| Weak | Strong |
|---|---|
| "Loved your recent post!" | "Your post on cutting ramp time to 45 days made a point I rarely see: that most of it is list quality, not coaching." |
| "Congrats on the new role!" | "Three months into running RevOps at Lumen is usually when the tool audit starts." |
| "I see you went to Michigan." | (Drop it unless the message is about Michigan.) |
| "Saw you’re hiring." | "Four SDR listings in two weeks, all mentioning outbound from scratch, suggests the team is being rebuilt." |
About a third of prospects have no public activity. Do not fake it. Use the role-and-trigger fallback:
"Most heads of operations at multi-site groups your size tell us payroll closes take two to three days. Is that true at Northwind too?"
It is honest, it is relevant and it invites a correction, which is still a reply.
Once the skill is installed, plain requests like these load it automatically. Swap in your own company, buyer and numbers.
“Research Priya Shah, VP Revenue at Lumen. Write an email and a LinkedIn opener.”
“I meet Tom Becker tomorrow. Give me a 60-second brief.”
“Find a real hook for each of these 15 prospects, or tell me when there isn't one.”
Use this for one person you are about to contact or meet. It produces a brief a rep can read in 60 seconds and a first line that proves the message was written for them. You get: person brief, sourced hooks, email opener, linkedin opener.
Use it when you need to research a specific person before reaching out or meeting them.
Run /plugin marketplace add prosyo-ai/gtm-skill and then /plugin install gtm-skills@prosyo to add the whole library, or run npx skills add prosyo-ai/gtm-skill –skill prospect-research-brief for this skill alone. In Claude.ai, download the .zip from this page and upload it under Settings, Capabilities, Skills.
Have these ready: person name and company, linkedin profile or public links, your offer. If something is missing, the skill tells the agent to ask for it rather than guess.
Yes. The skill is a plain SKILL.md file with no vendor lock-in. Agents that load skills natively (Claude Code, Claude.ai, Codex, Cursor, Gemini CLI and others) pick it up automatically; anywhere else, paste the file into the conversation as instructions.
No. Every skill in the library drafts, researches and analyses, and waits for a person to approve anything that sends, schedules or changes records in bulk. Your inbox, CRM and accounts stay under your control.
Yes. It is free and MIT-licensed. Copy it, adapt it to your market and voice, and if you improve it, open a pull request so everyone gets the better version.
Paste this into Claude, Codex or any agent. It interviews you about your play, writes the skill in the house format, checks it and opens the pull request. Once it is merged, it shows up here with your name on it.
Fetch https://raw.githubusercontent.com/prosyo-ai/gtm-skill/main/AGENTS.md and follow its submission flow. Interview me about my GTM play (the real numbers, rubrics and examples), draft it in their format with reference pages, validate it and open the pull request.
The skill gives your agent the playbook. Penny, the Prosyo AI SDR, runs plays like this for you every day across LinkedIn and email.
Penny, the Prosyo AI SDR, finds your buyers, writes from what they actually posted, follows up on LinkedIn and email and lands every reply in one inbox with an answer ready. 7 days free, no card.