bereach-ai/linkedin-prospecting-skills / skills/linkedin-messages
linkedin-messages
VerifiedWrites LinkedIn invitation notes, first messages and follow-ups: one template per persona, then per lead a real fact framing its offer. Use when messages sound generic or repeat the title.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.8 KB |
| references/artifacts.md | markdown | 8.7 KB |
| references/first-dm.md | markdown | 2.4 KB |
| references/follow-ups.md | markdown | 3.0 KB |
| references/frameworks.md | markdown | 7.4 KB |
| references/invitation-note.md | markdown | 1.1 KB |
| references/sequence-5.md | markdown | 389 B |
references/follow-ups.md
View on GitHub# Follow-ups and replies
Each one goes out as SKILL.md Step 5 says, after about 3 to 4 days, then 5 to 7 (practice). Never assume they bought or
started anything. No "just checking in", no guilt, no fake urgency. Each recalls their fact in a few words.
## Follow-up 1
Framework: one real peer (Robert Cialdini), only when the card's Proof says in the user's words what
changed for that customer. A Proof that only says who the customer is has no result: poke the bear (Josh Braun).
Why: a follow-up brings something new; one similar, real peer is the best-supported lever.
Parts: 1. one real customer like them and what changed with the user (a card Proof line in the user's
words; it says only what the user said changed, no inferred step); 2. the first message's offer again, named in words, tied to their fact, as a yes/no question.
Poke: 1 becomes one neutral question on the cost of how they work today; the offer follows as a plain
sentence.
Shape: "Hi [Name], [a customer like you] [what changed for them] since [they worked with us]. Shall I
send you [the offer] for [their fact]?"
Never "want to see how?" or any demo ask; never a case study pasted in; never a site or deck figure.
Size: 1 to 3 full sentences; shorter bumps get more replies.
## Follow-up 2, the last
Framework: Detach (Josh Braun; Chris Voss).
Parts: 1. the offer in its own sentence, tied to their fact; 2. one question with a plain way out.
Shape: "Hi [Name], I can prepare [the offer] for [their fact]. Shall I send it, or would you rather I
leave it there?"
## Replies
Framework: FAB through "So what?" (Neil Rackham), tied to their words.
Parts: 1. answer exactly what they asked or objected, naming their own words; 2. what that changes for
them, one sentence (a real peer only if it fits this reader); 3. ONE next step as a yes/no question.
Shape: "Hi [Name], unlike [what they named], [what changes]. [What that means for their week]. Shall I
[one next step]?"
Size follows theirs, in full sentences, never cut to their sentence length. A plain no: no reply
proposed, the sequence stops.
A deferral ("not now", "later", "send me some information" with no word on their own case) is never a
yes and gets no FAB. Information: one question on what they would want it for, or the offer if the first
message named one; never a document the user does not have. Not now: one short thanks and one question on
when to come back; the date they give goes on the contact as a tag (`bereach_contact_update`,
`tags: { add: ["back:YYYY-MM"] }`), and nothing is sent before it, no nurture sequence. From the first
working day of that month, `bereach_contacts` with `tag` `back:YYYY-MM` lists who is due: each goes on
Follow-ups to send, `bereach_brief` first, one message tied to what they said.
"Not me, ask [colleague]": one sentence of thanks, nothing else asked of them; no name given, one question
on who owns it. The named colleague is a new lead: `bereach_brief` first, then a first message whose line 1
says who pointed the user to them, in the referrer's own words, never stretched. Nobody else at that firm
is written to.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| 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: 196k | Updated | Claude CodeCodex | Verified | Install |