mcpField
L
li-reply

li-reply

github.com/jakeschincariolMarketing & growth2.9k247 installsUpdated 7w ago
Repository

About li-reply

li-reply is a LinkedIn comment-triage and reply-writing skill for people managing replies to their own posts. It prioritizes comments by value and leaves posting to the user.

Key features

  1. 01Five-bucket comment triage
  2. 02Replies tailored to each bucket
  3. 03Guidance for critics and leads
  4. 04Copy-ready grouped output
  5. 05User approval before posting

Use cases

  1. 01Prioritizing replies to a busy post
  2. 02Answering prospective leads publicly
  3. 03Responding constructively to criticism

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jakeschincariol/linkedin-agent-skill --skill li-reply

After installing, type/li-replyin Claude Code to confirm it loaded.

Details

From the project README

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:

bucketwhat it iswhat it gets
LEADsomeone describing the problem you solvea real answer + a soft open door
SUBSTANCEadds data, disagrees, extendsthe longest reply on the thread
PEERa name worth being seen next toa reply that gives them something
SUPPORT"great post", 🔥, a taga like, and a 3-8 word reply at most
NOISEpitch, spam, bad faithnothing, 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.

Comments

Markdown supported