Przejdź do treści
Biblioteka skilli
Marketing i treści · Pisanie

li-comment

/li-comment

Pisze komentarze do cudzych postów na LinkedIn w tonie osoby z poglądem, z gotową odpowiedzią lub serią komentarzy do rundy zaangażowania.

Repozytorium
linkedin-agent ↗
Licencja
MIT
Ostatnia zmiana repozytorium
31.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 31.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Pisze komentarze do cudzych postów na LinkedIn w tonie osoby z poglądem, z gotową odpowiedzią lub serią komentarzy do rundy zaangażowania.

Wyzwalacze z opisu

comment on thisengage with thiswhat do I say here
Oryginalny opis (EN)

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.

Jak działa

  1. Input
  2. The nine comment types
  3. Rules
  4. Output
  5. Batch mode
  6. Publishing
Sekcje z nagłówków SKILL.md, w oryginale · 84 linii, 709 słów
Podgląd SKILL.md
---
name: li-comment
description: >-
  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.
---

First read `data/voice.md` and `data/topics.md`: write in that voice, in the language set by `language` in `data/config.json`, and use only proof listed there.

# li-comment

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.

## Input

The post text, author name and role, either pasted by the user or read from
the feed by the `linkedin-session` skill in Ego Lite. Never guess what a post
said: if the text could not be read in full, skip the post.

## The nine comment types

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 |

## Rules

- **2 to 4 sentences.** Longer reads as a hijack. Shorter reads as filler.
- **Never open with "Great post"**, "Love this", "So true", "Couldn't agree
  more", "This resonates", or the author's first name followed by an
  exclamation mark. All six are invisible.
- **No emoji openers.** No 🔥 or 👏 as a first character.
- **Never restate the post.** The author knows what they wrote and so does
  everyone reading.
- **One idea.** A comment with two points reads as a blog attempt.
- **Say the specific thing.** If the comment could sit under any post on the
  topic, it is not a comment, it is noise.
- **Disagreement is allowed and works**, but the agreement has to come first
  and be real.

## Output

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.
```

## Batch mode

For an engagement round, take the 5-10 posts collected by `linkedin-session`,
return one comment each in a single block, and keep a running
note of who they have already commented on this week in
`data/log.jsonl` (via `bin/li log`). Commenting on the same three people every day is
visible and it looks like what it is.

## Publishing

This skill writes the comment. Publishing, limits and logging belong to the
`linkedin-session` skill.

Wersje

RepozytoriumWynikLicencja
Ta strona · mkmlabs-ai/linkedin-agent100MIT
gladosAagman/linkedin-agent-skill100MIT
Jakeschincariol/linkedin-agent-skill100MIT

Migawka bazy z 13.11.2026 · wersja paczki 9f3d09244646 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100ig-comment
    Pisze komentarze pod cudzymi postami i rolkami na Instagramie, które brzmią jak głos osoby z własnym zdaniem, także partiami na codzienną rundę zaangażowania.
  • 100ig-comment
    Pisze komentarze pod cudzymi postami i rolkami na Instagramie, które brzmią jak głos osoby z własnym zdaniem, także partiami na codzienną rundę zaangażowania.
  • 100im-comment
    Pisze komentarze pod cudzymi postami i rolkami na Instagramie tak, by brzmiały jak opinia konkretnej osoby z realnym zdaniem.
  • 100ig-comment
    Pisze komentarze pod cudzymi postami i rolkami na Instagramie tak, by brzmiały jak opinia konkretnej osoby z realnym zdaniem.
  • 100ig-comment
    Pisze komentarze pod cudzymi postami i rolkami na Instagramie, które brzmią jak głos osoby z własnym punktem widzenia, także partiami na codzienną rundę zaangażowania.
  • 100engagement-round
    Planuje i pisze codzienną 20-minutową rundę komentarzy pod cudzymi postami: 10 kont i komentarze brzmiące jak prawdziwa opinia, które twórca publikuje ręcznie.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.