# Li Reply

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

- Repository: https://github.com/Jakeschincariol/linkedin-agent-skill (3031 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-09-17
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-reply -g -a claude-code -y`
Codex: `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-reply -g -a codex -y`
Cursor: `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-reply -g -a cursor -y`
Gemini CLI: `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-reply -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Jakeschincariol/linkedin-agent-skill`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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

The rest: https://github.com/Jakeschincariol/linkedin-agent-skill/blob/HEAD/skills/li-reply/SKILL.md