Skills

Li Reply

Handle the replies under the user's own LinkedIn posts - draft answers to every...

Install

npx skills add Jakeschincariol/linkedin-agent-skill --skill li-reply -g -a claude-code -y
Category
Engineering
Updated
2mo ago
License
MIT
Context cost
Lightabout 662 tokens
Runs scripts
No, instructions only

What it does

Handle the replies under the user's own LinkedIn posts - draft answers to every comment, sorted by which ones are worth answering. Use when the user pastes the comments on their post, says "reply to these", "handle my comments", "someone said X on my post", or is dealing with a critic or a lead in the comments.

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
Read the whole SKILL.md on GitHub

More in Engineering