Li reply skill

Handle the replies under the user's own LinkedIn posts - draft answers to every comment, sorted by which ones are worth answering.

by Jakeschincariol·MIT license·★ 1,856 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words
# li-reply

The reply thread under your own post is where reach is actually decided. Every
reply is a second engagement event on the post, and the first hour of replies
does most of the work. But the value is not equal across comments, so this
skill sorts before it writes.

## Input

The user pastes the comments, ideally with names and roles. Screenshots are
fine. Do not scrape the thread with a browser tool.

## Triage first

Sort every comment into one of five buckets and say the count out loud:

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

Files of Li reply

Jakeschincariol/main1 file shown
SKILL.md
Show the full text79 lines
li-reply/SKILL.md79 lines · 2.9 KB

li-reply

The reply thread under your own post is where reach is actually decided. Every reply is a second engagement event on the post, and the first hour of replies does most of the work. But the value is not equal across comments, so this skill sorts before it writes.

Input

The user pastes the comments, ideally with names and roles. Screenshots are fine. Do not scrape the thread with a browser tool.

Triage first

Sort every comment into one of five buckets and say the count out loud:

bucket what it is what it gets
LEAD someone describing the problem you solve a real answer + a soft open door
SUBSTANCE adds data, disagrees, extends the longest reply on the thread
PEER a name worth being seen next to a reply that gives them something
SUPPORT "great post", 🔥, a tag a like, and a 3-8 word reply at most
NOISE pitch, spam, bad faith nothing, or one line and out

Then write in that order, and stop writing when the value stops.

How to reply

  • Answer the actual question. If someone asks how, tell them how, in the reply. Do not send them to a DM to hear the answer they could have had.
  • Use their name once, at the start, and never with an exclamation mark.
  • Match their length. A two-line comment does not get a six-line reply.
  • To a critic: concede the true part first, in their words, then hold the line on the part you believe. Never delete, never get defensive, never reply twice on the same thread.
  • To a lead: answer fully in public. The open door is one sentence at the end, and it is an offer of help, not a pitch. Public value is what makes the next person DM you.
  • To a pitch in your comments: ignore it. Replying gives it reach.

Output

One block, grouped by bucket, each reply copy-ready and already humanized:

REPLIES  ·  17 comments  ·  1 LEAD, 3 SUBSTANCE, 4 PEER, 8 SUPPORT, 1 NOISE

LEAD
@Sarah Chen - "we have the same problem with proposals"
> The part that fixed it for us was pulling the pricing table out of the doc
> entirely and sending it as its own page. Cut a whole review round. Happy to
> send you the template if it is useful.

SUBSTANCE
@Marcus Webb - disagrees on cadence
> Fair, and 4x a week only worked because I had 8 months of posts behind it.
> From a standing start I would do what you said.

SUPPORT  (like these, reply to the first three)
@... "This is great" -> Thanks Dan.
...

NOISE  (1)
Skipped: an agency pitch. Replying gives it reach.

Then the gate: nothing is posted until the user says yes. They paste the replies themselves.

1---
2name: li-reply
3description: >-
4 Handle the replies under the user's own LinkedIn posts - draft answers to
5 every comment, sorted by which ones are worth answering. Use when the user
6 pastes the comments on their post, says "reply to these", "handle my
7 comments", "someone said X on my post", or is dealing with a critic or a
8 lead in the comments.
9---
10 
11# li-reply
12 
13The reply thread under your own post is where reach is actually decided. Every
14reply is a second engagement event on the post, and the first hour of replies
15does most of the work. But the value is not equal across comments, so this
16skill sorts before it writes.
17 
18## Input
19 
20The user pastes the comments, ideally with names and roles. Screenshots are
21fine. Do not scrape the thread with a browser tool.
22 
23## Triage first
24 
25Sort every comment into one of five buckets and say the count out loud:
26 
27| bucket | what it is | what it gets |
28| --- | --- | --- |
29| **LEAD** | someone describing the problem you solve | a real answer + a soft open door |
30| **SUBSTANCE** | adds data, disagrees, extends | the longest reply on the thread |
31| **PEER** | a name worth being seen next to | a reply that gives them something |
32| **SUPPORT** | "great post", 🔥, a tag | a like, and a 3-8 word reply at most |
33| **NOISE** | pitch, spam, bad faith | nothing, or one line and out |
34 
35Then write in that order, and stop writing when the value stops.
36 
37## How to reply
38 
39- **Answer the actual question.** If someone asks how, tell them how, in the
40 reply. Do not send them to a DM to hear the answer they could have had.
41- **Use their name once**, at the start, and never with an exclamation mark.
42- **Match their length.** A two-line comment does not get a six-line reply.
43- **To a critic:** concede the true part first, in their words, then hold the
44 line on the part you believe. Never delete, never get defensive, never reply
45 twice on the same thread.
46- **To a lead:** answer fully in public. The open door is one sentence at the
47 end, and it is an offer of help, not a pitch. Public value is what makes the
48 next person DM you.
49- **To a pitch in your comments:** ignore it. Replying gives it reach.
50 
51## Output
52 
53One block, grouped by bucket, each reply copy-ready and already humanized:
54 
55```
56REPLIES · 17 comments · 1 LEAD, 3 SUBSTANCE, 4 PEER, 8 SUPPORT, 1 NOISE
57 
58LEAD
59@Sarah Chen - "we have the same problem with proposals"
60> The part that fixed it for us was pulling the pricing table out of the doc
61> entirely and sending it as its own page. Cut a whole review round. Happy to
62> send you the template if it is useful.
63 
64SUBSTANCE
65@Marcus Webb - disagrees on cadence
66> Fair, and 4x a week only worked because I had 8 months of posts behind it.
67> From a standing start I would do what you said.
68 
69SUPPORT (like these, reply to the first three)
70@... "This is great" -> Thanks Dan.
71...
72 
73NOISE (1)
74Skipped: an agency pitch. Replying gives it reach.
75```
76 
77Then the gate: **nothing is posted until the user says yes.** They paste the
78replies themselves.
79 

Discussion