Agent skill
linkedin-comment-and-invite-writer
Write LinkedIn comments, connection-request notes and first messages that get replies: rules, character limits (200 or 300 for invitation notes), anti-patterns, and examples in English and French.
Filed under LinkedIn and social.
From gtmotto/gtm-skills · 5 skill entries · 1 · pushed 2026-09-21
What it does when it runs
Write LinkedIn comments, connection-request notes and first messages that get replies: rules, character limits (200 or 300 for invitation notes), anti-patterns, and examples in English and French. Use when the user asks for a LinkedIn comment, an invite note, a connection request message, a first DM after connecting, a follow-up, wants to rewrite an outreach draft, or asks 'what should I say to this person'. Works on any draft, from any tool, or from scratch.
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/gtmotto/gtm-skills.git /tmp/gtm-skills git -C /tmp/gtm-skills sparse-checkout set "skills/linkedin-comment-and-invite-writer" mkdir -p ~/.claude/skills/linkedin-comment-and-invite-writer cp -R "/tmp/gtm-skills/skills/linkedin-comment-and-invite-writer/." ~/.claude/skills/linkedin-comment-and-invite-writer/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
Or take the whole library
This repo ships a .claude-plugin manifest, so Claude Code can install all 5 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.
/plugin marketplace add gtmotto/gtm-skills /plugin
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from gtmotto/gtm-skills/blob/7e851d8ce8ead8d3f6eff579deabfbfc0e0d4ef9/skills/linkedin-comment-and-invite-writer/SKILL.md, which is licensed MIT (repository). 750 words, 6 headings.
LinkedIn comment and invite writer
Three things get written on LinkedIn during outreach, and each has one job:
| 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 |
None of them pitches. The pitch happens after they answer, if it happens at all.
The comment
Rules:
- Add one specific thing. A number, a counter-example, a step they skipped, a question only they can answer. "Great post" and "so true" are noise.
- Disagree politely when you can. A courteous "I'd push back on one point" gets three times the replies of agreement.
- No link, no product name, no "we".
- Match the language and the register of the post. A French rant gets a French comment. A post with emoji gets none back; a comment is not a reply.
- Under three sentences. The best comments are one.
- Reply to a comment rather than the post when the thread is long. The author sees both; the commenter sees only yours.
Examples:
Le vrai coût n'est pas les 100 euros, c'est les 4h par semaine à nettoyer la liste après. Vous avez mesuré ce temps-là ?
The 30 percent acceptance rate is the number I'd watch before the reply rate. Below that it is a targeting problem, not a copy problem.
The connection-request note
Rules:
- 200 characters, hard. LinkedIn gives a free seat 200 and Premium 300, and a note over the limit means the invite is never sent, silently. Count.
- Name the reason. The post, the comment, the hire, the mutual context. Something that proves this note was written for them.
- No pitch, no ask, no link. The ask is the invite itself.
- One sentence, sometimes two. First name, the reason, done.
- Send it two days after the visit and the reaction, not the same hour.
Examples (each under 200 characters):
Pierre, votre post sur Sales Nav m'a fait rire jaune, on fait la même chose à la main. Ravi de vous suivre ici.
Sarah, your comment on the SDR ramp thread was the only one with a number in it. Would like to keep reading you.
Marc, saw you're opening a first SDR role. Been through that stage twice, happy to connect.
The first message
They accepted. Now the mistake is to pitch within the hour. Rules:
- Under 60 words.
- Ask about the thing they said, not about their needs. "How did the spreadsheet thing end up?" beats "What are your biggest challenges?".
- One question. Two questions get zero answers.
- Nothing to click. No calendar link, no deck, no case study.
- Wait at least a day after the accept.
Example:
Merci pour l'accept. Je repensais à votre post : vous avez fini par garder Sales Nav ou vous avez trouvé autre chose pour les listes ?
The follow-up, if there is no answer after 5 to 7 days, is one line and gives them an out: "Pas de souci si ce n'est pas le moment, je voulais juste savoir comment ça s'était fini."
Anti-patterns
Rewrite any draft that contains one of these:
- "I hope this message finds you well", "Je me permets de vous contacter"
- "Quick question" followed by a long one
- "I noticed you..." followed by something on their profile (everyone notices)
- the product name, a feature, a pricing word
- "would love to", "jump on a call", "15 minutes"
- more than one question mark
- an exclamation mark in a note to a stranger
- a note that would work for anyone else on the list
Voice
Before writing, ask for or infer the voice in one line: "direct, French, no emoji, tutoiement only after they do". Keep it for the whole sequence. A comment in one voice and a note in another reads as two people, which it often is.
GTM Otto drafts these three pieces for every person it finds, in your voice, and waits for your approval before anything is said. Use this skill to review or rewrite those drafts; it needs a GTM Otto account.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- linkedin-comment-drafter by sergebulaev · 4,230
- linkedin-post-writer by sergebulaev · 4,230
- linkedin-comment-drafter by sergebulaev · 4,230
- linkedin-post-writer by sergebulaev · 4,230
- 07-linkedin-outreach-writer by SimonTheSalesBooster · 39
- linkedin-marketing by sergebulaev · 4,230
- linkedin-content-planner by sergebulaev · 4,230
- linkedin-employee-advocacy by sergebulaev · 4,230
Need help setting it up?
This page tells you what linkedin-comment-and-invite-writer does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.