SkillAgentSearch skills...

li-reply

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

Install / Use

npx skills add Jakeschincariol/linkedin-agent-skill --skill li-reply

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Supported Platforms

Universal

Tags

Our assessment of li-reply

li-reply scores 82/100 on our quality scale, 3416th of 4,702 Development & Engineering skills we index.

Its SKILL.md is 2.9 KB long, split into 5 sections with 1 code example: a solid amount of guidance for an agent.

It has 671 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so li-reply is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-05. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

li-reply compared with similar skills

All 4 of these similar skills score higher than li-reply; compare them before choosing.

SkillScoreStarsUpdatedFormat
li-reply (this skill)by Jakeschincariol826712mo agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
lobehubby lobehub10085.7ktodayMCP Server

Frequently asked questions

How do I install li-reply?
Run npx skills add Jakeschincariol/linkedin-agent-skill --skill li-reply. The install tabs above show the steps for each supported agent.
Which AI agents does li-reply work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is li-reply safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is li-reply still maintained?
The repository was last updated about 2 months ago, so li-reply is actively maintained.

name: li-reply 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.

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.

Related Skills

View on GitHub
GitHub Stars671
CategoryDevelopment
Updated2mo ago
Forks98

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions