Skip to content

bereach-ai/linkedin-prospecting-skills / skills/linkedin-personas

linkedin-personas

Verified

Builds 2 to 4 persona cards with the user and puts each lead in one. Use before writing to a new list, or when messages sound generic or repeat the job title.

FileKindSize
SKILL.mdskill md7.1 KB
references/artifacts.mdmarkdown9.1 KB
references/frameworks.mdmarkdown20.3 KB
references/persona-card.mdmarkdown4.9 KB
references/sources.mdmarkdown3.5 KB

references/sources.md

View on GitHub
# Read the business before asking

The user should never type what their website, CRM or documents already say. Read these first, pre-fill the
cards, then ask only what is still empty (inside linkedin-outreach-method: SKILL.md Step 1). Every line read keeps its source, shown in grey on the card.

A connected CRM is looked at, never asked about. What no tool shows (the website address, an export,
documents: deck, offer sheet, price list, case studies, call notes) is asked inside the linkedin-outreach-method
skill's one question round, never in a message of its own. Read what they give; skip what they do not have,
without asking twice.

## 1. Website (always, when there is one)

1. Read the home page, then list the pages: the site's menu and footer links, and `/sitemap.xml` when it
   exists. Read every page about the offer, services, pricing, customers or case studies, about, and the
   last 3 to 5 blog posts or news. Skip legal, careers and login pages. Say how many pages were read.
2. Take from it:

| On the site | Fills |
|---|---|
| What they sell, for whom, in which words | The offering (one line), Found by, Never say (their jargon) |
| Pages per sector or kind of client | Candidate ICPs, for the search plan (kinds of company) |
| Pages per role or buyer | Candidate personas, one per role in a situation |
| Prices or "from X" | What it costs (shown as "site", the user confirms) |
| Case studies, client logos, testimonials | Candidate Proof, marked `(guess)`: a case becomes Proof only in the user's words |
| How they work, steps, when they are called | Why now, the step they are hired at |
| Free resources (guides, audits, templates) | Candidate Offer they keep, once the user says they offer it |

3. A figure on the site (a rate, a %, a before and after) is never Proof and never goes in a message.

## 2. CRM (only through a connector the user has, read only)

Look at the connected tools (HubSpot, Salesforce, Pipedrive, Attio, folk, Notion, a spreadsheet). None: ask
for an export of won and lost deals, or skip. Never write to the CRM.

| In the CRM | Fills |
|---|---|
| Won deals, last 12 to 24 months: contact title, company type and size | Found by, the split into personas |
| What happened just before the first contact or the deal (notes, source, dates) | Why now and its signal |
| Lost deals and their reasons | Objection |
| Notes, emails, call summaries in the buyer's own words | Pain (status `CRM, N deals`); their words go apart as "your words (to check)", `(guess)`, until replies use them |
| Deal size, time to close | Goals, Busy months (when deals stall) |
| Current customers and open deals | Not this persona: they leave the prospect list |

Customer names stay off the cards unless the user says yes.

## 3. Documents (uploaded, or through a Drive, Notion or similar connector)

| Document | Fills |
|---|---|
| Deck, offer sheet, price list | Offering, What it costs, Offer they keep |
| Case studies | Candidate Proof (`(guess)`) |
| Call transcripts or notes (the best source of their words) | Pain, Objection, Who else decides; their words apart as "your words (to check)", `(guess)` |
| An existing sales playbook or persona sheets | The starting cards, each line re-checked like any other |

## 4. Then ask only the gaps

The page opens with one
row of chips: what was read ("site : 14 pages", "CRM : 32 deals gagnés, 18 perdus", "3 documents") and what
is missing. A line from the site, the CRM or a document is a lead for the user to confirm, never seen:
seen still needs 2 replies.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall