Write comments on other people's LinkedIn posts that read as a person with an opinion, not a bot. Use when the user pastes a post and wants a comment, says "comment on this", "engage with this", "what do I say here", or wants a batch of comments for their engagement round.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Commenting is the highest-leverage thing on LinkedIn and the easiest to do badly. A comment on a post with 400 reactions gets seen by more people than most of your own posts. A generic one gets seen by nobody and costs you credibility with the author.
The user pastes the post text (and the author's name and role if they have it). If they paste a screenshot, read it. If they give you a URL you cannot open, ask them to paste the text - do not guess what the post said, and do not use browser automation to scrape the feed.
Pick by what the post actually is. Never default to type 1.
| # | type | when | shape |
|---|---|---|---|
| 1 | Add a datum | post makes a claim you can support with a number | "We saw the same thing: 40% of our..." |
| 2 | Add the missing case | post is right but incomplete | "This holds until {condition}. Then..." |
| 3 | Respectful disagree | you genuinely think it is wrong | name the agreement first, then the fork |
| 4 | Extend one line | one sentence in the post is the good one | quote it, then build on it |
| 5 | Ask the real question | post skipped the hard part | one question, specific, no "curious to hear" |
| 6 | The receipt | you have done the thing they described | what happened, in two sentences |
| 7 | The correction | there is a factual error | be right, be brief, be kind, be sure |
| 8 | The reframe | the post has the right facts and the wrong frame | "Another way to read this:" |
| 9 | The one-liner | the post needs nothing, you want presence | under 12 words, must be funny or true |
Give two options of different types, labelled, plus a one-line reason for
the one you would post. Run both through /li-human first - a comment with an
em dash in it is more obviously machine-written than a post, because comments
are short and people read them closely.
COMMENT OPTIONS (on @author's post about hiring)
[6 · Receipt]
We tried the no-resume version of this for 3 hires last year. Two were the
best hires we made. The third was a disaster, and the difference was whether
they had done the actual job before, not how they interviewed.
[3 · Respectful disagree]
Agree on the signal problem. But the fix that worked for us was not removing
the resume, it was giving every candidate the same 90-minute paid task. Same
outcome, far less argument internally.
Post the first. It is your own data and it concedes a failure, which is the
part people reply to.
If the user wants an engagement round, ask for the 5-10 posts as pasted text
in one message, return one comment each in a single block, and keep a running
note of who they have already commented on this week in
~/.claude/linkedin/log.md. Commenting on the same three people every day is
visible and it looks like what it is.
Do not auto-post. Do not use a browser tool to publish comments on the user's behalf. Automated posting and scraping both violate LinkedIn's User Agreement and put the account at risk. This skill writes the comment. The user posts it.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Post-mortem on what the user has already published - which posts actually worked, why, and what to stop doing. Use when the user pastes their LinkedIn analytics or past posts and asks "what's working", "why did this flop", "read my analytics", "audit my content", or wants to know what to double down on.
The English summary is being prepared. Showing the original description.
Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the swipe, and the PDF to upload. Use when the user says "carousel", "document post", "slides for LinkedIn", "turn this into a carousel", or has a list-shaped idea that would die as a text post.
The English summary is being prepared. Showing the original description.
Write connection notes and DM follow-ups that get replies - the 200-character invite, the first message, and the two follow-ups. Use when the user says "write a connection request", "DM this person", "outreach message", "how do I follow up", or is reaching out to someone specific on LinkedIn.
The English summary is being prepared. Showing the original description.
Strip the machine fingerprint out of any draft - em dashes, AI slop words, invisible watermark characters - and score it against a five-check detection panel before it goes out. Use whenever text needs to sound human, when the user says humanize, "does this sound like AI", "remove the em dashes", "de-slop this", "will this get flagged", or before any LinkedIn post, comment, reply or DM is shown to the user.
The English summary is being prepared. Showing the original description.
Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers and spam, and draft the replies worth sending. Use when the user says "my inbox is a mess", "triage my DMs", "should I reply to this", pastes a batch of LinkedIn messages, or is drowning in connection requests.
The English summary is being prepared. Showing the original description.
Build the week on LinkedIn - what to post, when to post it, and who to engage with. Use when the user says "plan my week", "what should I post", "content calendar", "I have nothing to post about", or wants a posting schedule and an engagement list.
The English summary is being prepared. Showing the original description.