SKILL.md
- name:
- linkedin-comment-and-invite-writer
- description:
- Use this skill when writing or rewriting the three things that get written on LinkedIn during outreach: a comment on a prospect's post, a connection-request note (200 characters free, 300 Premium), and the first message after they accept, plus the one-line follow-up. Produces drafts that get replies, with the rules, the anti-pattern list and examples in English and French. Fires on "write a LinkedIn comment", "invite note", "connection request message", "first DM after connecting", "follow-up", "rewrite this outreach draft", or "what should I say to this person".
LinkedIn comment and invite writer
Applies to any LinkedIn outreach draft, from any tool or from scratch, whenever the words are the thing being decided. Produces the comment, the note and the first message for one person, each doing exactly one job, none of them pitching.
Three pieces, one job each:
| Piece | Job | Length |
|---|---|---|
| Comment on their post | be noticed by someone who does not know you | 1 to 3 sentences |
| Connection-request note | give one reason to accept | under 200 characters |
| First message after they accept | start a conversation, not a sale | under 60 words |
The pitch happens after they answer, if it happens at all.
The play
- Get the voice in one line. "Direct, French, no emoji, informal only after they are." Keep it for the whole sequence; a comment in one voice and a note in another reads as two people, which it often is.
- Write the comment. Add one specific thing: a number, a counter-example, a step
they skipped, a question only they can answer. Disagree politely when possible; a
courteous "I'd push back on one point" gets three times the replies of agreement.
Match the post's language and register. Under three sentences; the best are one.
Rules and examples in
references/comment-and-note.md. - Write the note. 200 characters, hard; over the limit the invite is silently never
sent, so count. Name the reason (the post, the comment, the hire, the mutual
context) so the note proves it was written for them. No pitch, no ask, no link; the
ask is the invite. Send it two days after the visit and the reaction. Examples under
200 in
references/comment-and-note.md. - Write the first message, after they accept. Under 60 words, one question, about
the thing they said rather than their needs, nothing to click, at least a day after
the accept. The follow-up after 5 to 7 days of silence is one line that gives them an
out. Patterns in
references/first-message.md. - Run the anti-pattern list on every draft. Rewrite anything containing an item from
references/anti-patterns.md; the last item ("a note that would work for anyone else on the list") catches what the others miss.
What good looks like
- The best operator writes the note from the person's own words. "Your comment was the only one with a number in it" cannot be sent to anyone else, and that is the whole test.
- The mediocre version is polite, complete and generic: a greeting, a compliment, a question about their challenges, a calendar link. It reads as a template because it is one, and it gets the "not interested in your bot" screenshot.
- A comment that pushes back on one point, politely, with a number, outperforms agreement three to one. Agreement is noise; a specific disagreement is a person.
- Good output is three short texts for one person, in one voice, each under its limit, none containing the product name, and a character count next to the note.
Rules
- MUST keep the invitation note under 200 characters unless the account is known Premium, and show the count.
- MUST name the specific reason in the note; the post, the comment, the hire.
- MUST ask exactly one question in the first message.
- NEVER include a link, a product name, a feature or a pricing word in any of the three pieces.
- NEVER pitch in the comment thread; the thread is where they were found, not where they are sold.
- NEVER send the note the same hour as the visit and the reaction, or the first message within a day of the accept.