Claude Prompt Library

LinkedIn Comments That Earn Profile Visits

30 copy-paste prompts

Paste into Claude. Fill [PLACEHOLDERS]. Get comments you paste on other people's posts, reply-to-reply, and founder threads. You post the comment. Not a feed post.

In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.

Louis Corneloup
By Louis Corneloup · Founder, Techpresso
Last updated ·Hand-curated & tested by the AI Academy team

Authority Comments

5 prompts

Missing Frame Add-On

1/30

✨ What it does

Claude writes an authority comment on [THEIR POST] that adds one frame they skipped, in 4 to 8 short lines, without hijacking the thread. Paste the comment under their post on LinkedIn.

You are a LinkedIn comment writer. You write comments people paste under someone else's post. You do not write feed posts. <context> I will paste [THEIR POST]. I need one authority comment that adds a frame they skipped. Goal: a reader clicks my profile because the comment was specific and useful. Not a hijack. Not Great post. </context> <inputs> - Their post: [THEIR POST] - The frame I can add: [MISSING FRAME] - Proof I can name (project, number, year) or NONE: [PROOF OR NONE] - Who I am in one line: [MY LANE] - Words I never use: [BANNED PHRASES] - Voice: [DIRECT / WARM / DRY] - What I will not pitch: [NO PITCH] </inputs> <task> Write 2 comments (A and B), each 50-120 words, 4-8 short lines. Each must: 1. Open on [MISSING FRAME] or a concrete line from [THEIR POST], not praise 2. Credit the author in one clause, then add the frame 3. Use [PROOF OR NONE] only if it is not NONE. If you want a second fact, write [VERIFY] 4. Stay shorter than a feed post. No see-more essay 5. Close with one light question the author can answer in a sentence, or no question if a question would feel fake First line must stand alone in the thread snippet. </task> <constraints> - Do not write a LinkedIn post, carousel, or About section. - Do not invent clients, studies, or metrics. - No Love this, so true, or unlocking value. - Avoid [BANNED PHRASES]. Honor [NO PITCH]. - No hashtag dump. No stealth CTA to follow me. </constraints> <format> Return Comment A, Comment B, then a 2-line note on which one is less likely to read as a hijack. Label a suggested first line if the open is weak. </format>

💡

Pro tip: Add a frame they did not use. If your comment could stand as its own post, you stole the thread.

Proof From My Week

2/30

✨ What it does

Claude writes a proof comment for [THEIR POST] that adds one fact from [PROOF FROM MY WEEK] and stays shorter than a feed post. Paste the comment under their post on LinkedIn.

You are a LinkedIn comment writer who adds one proof, then stops. <context> I will paste [THEIR POST]. I have [PROOF FROM MY WEEK]. I need a comment that attaches that proof without turning their post into my case study. I will paste the comment under their post. </context> <inputs> - Their post: [THEIR POST] - Proof from my week: [PROOF FROM MY WEEK] - What the proof is not: [WHAT IT IS NOT] - Audience who might click my name: [AUDIENCE] - Voice: [CALM / SHARP] - Off-limits claims: [OFF-LIMITS] </inputs> <task> Write 2 comments (70-130 words). Rules: - First line names the proof or the clash with their point, not thanks for sharing - Use only [PROOF FROM MY WEEK]. State [WHAT IT IS NOT] in one line so I do not overclaim - Honor [OFF-LIMITS] - End with a question about their version of the proof, or a single useful add if a question would be cheap - Short lines. White space. Comment length, not a post If a second number would help and I did not give it, write [VERIFY] instead of guessing. </task> <constraints> - Do not invent a cleaner result. - Do not write a case-study post. - No we helped hundreds of companies. - No check my profile for the full story. </constraints> <format> Return both comments ready to paste, plus a [VERIFY] list, plus one shorter alt under 50 words. </format>

💡

Pro tip: One fact you can screenshot beats a vague I have seen this too. If the proof needs a paragraph of setup, it belongs in your own post.

Steelman Then One Cut

3/30

✨ What it does

Claude writes a steelman comment on [THEIR TAKE] that restates their strongest point, then adds one cut you can defend. Paste the comment under their post on LinkedIn.

You are a LinkedIn comment writer who steelmans first, then adds one cut. <context> They argued [THEIR TAKE]. I agree with the strongest version, then I have one cut. I need a paste-ready comment, not a debate-club essay and not my own post. </context> <inputs> - Their take in their words: [THEIR TAKE] - Their post if I have it: [THEIR POST OR NONE] - The cut I actually believe: [MY CUT] - Proof for the cut or NONE: [PROOF OR NONE] - Who I must not punch: [OFF-LIMITS GROUP] - Voice: [RESPECTFUL / DRY] </inputs> <task> Write 2 comments (60-110 words). Each: 1. Opens by restating [THEIR TAKE] so they would nod 2. Adds [MY CUT] in 2-4 short lines 3. Uses [PROOF OR NONE] only when real 4. Invites their reply on the cut, not a pile-on from the peanut gallery Keep it a comment. If the cut needs a full post, say so and write the comment as a pointer, not the essay. </task> <constraints> - Do not mock the author. - Do not insult [OFF-LIMITS GROUP]. - Do not invent research. - No everyone is wrong closer. - No feed-post length. </constraints> <format> Return both comments, then one line I should delete if I want fewer fights. </format>

💡

Pro tip: Restate their point in words they would accept. If the steelman is a cartoon, the cut looks cheap and nobody clicks through.

Named Three-Part Frame

4/30

✨ What it does

Claude writes a named-framework comment from [FRAMEWORK NAME] that fits in a thread, with three parts and no white-paper tone. Paste the comment under their post on LinkedIn.

You are a LinkedIn comment writer who drops a named three-part frame in comment length. <context> I need a comment that teaches [FRAMEWORK NAME] under someone else's post about a related problem. Readers should steal the name. Not a white paper. Not my own authority post. </context> <inputs> - Framework name I will stand behind: [FRAMEWORK NAME] - Three parts in my words: [PART A / PART B / PART C] - Their post or topic: [THEIR POST] - A situation it explained: [SITUATION] - Voice: [TEACHER / PEER] - Words I never use: [BANNED PHRASES] </inputs> <task> Write 1 full comment (80-140 words) and 1 shorter alt (under 70 words). Structure: - Open on the problem in [THEIR POST], not on my framework brand - Name [FRAMEWORK NAME] once - Three parts, each on its own short line - [SITUATION] in two lines max - Close with when not to use it, or a question about which part they skip Keep the name consistent. Short lines. </task> <constraints> - Do not invent a fourth part. - Do not write slides or a feed post. - Avoid [BANNED PHRASES]. - No thought leadership filler without the three parts. - No follow me for the template. </constraints> <format> Return the long comment, the short alt, and a one-line warning if [FRAMEWORK NAME] sounds like a trademark I should change. </format>

💡

Pro tip: Use a name you already say out loud. If the name needs a footnote, it will not travel, and nobody will tap your profile to learn more.

Myth Replace In Thread

5/30

✨ What it does

Claude writes a myth-replace comment for [MYTH IN THEIR POST] that swaps in [REPLACEMENT] without dunking on the author. Paste the comment under their post on LinkedIn.

You are a LinkedIn comment writer who replaces a myth without dunking on the author. <context> Their post repeats or brushes [MYTH IN THEIR POST]. I do [REPLACEMENT] instead. I need a paste-ready comment that stays kind and specific. Not a rant. Not a 10-myth post. </context> <inputs> - Myth in their words: [MYTH IN THEIR POST] - What I do instead: [REPLACEMENT] - Why smart people still say it: [WHY IT SPREADS] - One example I can defend: [EXAMPLE] - Their post: [THEIR POST] - Tone: [RESPECTFUL / DRY] </inputs> <task> Write 2 comments (60-120 words). Open by quoting or tightly paraphrasing the myth. Credit something they got right. Then [REPLACEMENT] and [EXAMPLE]. Close when the myth is actually true. Invite their version, not a pile-on. First line is not You are wrong. </task> <constraints> - Do not mock beginners. - Do not invent research. - One myth only. - Do not write my own myth-bust post. - No hashtag soup. </constraints> <format> Return both comments ready to paste, plus one line I should cut if I want fewer fights. </format>

💡

Pro tip: Quote the myth the way the post said it. If you polish it into a straw man, you look like you came to score points.

Story Comments

5 prompts

Mid-Scene Three-Line Story

6/30

✨ What it does

Claude writes a mid-scene story comment from [CHARGED MOMENT] in 5 to 8 lines that earns a profile tap without becoming a post. Paste the comment under their post on LinkedIn.

You are a LinkedIn story-comment writer. You start mid-scene and stop after one lesson. Comment length only. <context> I need a story comment under someone else's post. Open inside [CHARGED MOMENT]. Not a memoir post. Not a tip dump dressed as a story. </context> <inputs> - The charged moment: [CHARGED MOMENT] - Sensory or dialogue I remember: [DETAIL] - What I got wrong or saw: [MY BEAT] - The one lesson: [LESSON] - Their post I am commenting on: [THEIR POST] - What I will not share: [OFF-LIMITS] - Voice: [QUIET / FUNNY-THEN-REAL] </inputs> <task> Write 2 comments (70-130 words, 5-8 short lines). Rules: - First line is action or dialogue, not I want to share a story - Tie to [THEIR POST] in one clause so it is a comment, not a hijack - Use [DETAIL] - One lesson only, in my words - Honor [OFF-LIMITS] - End with a light question that invites their similar moment </task> <constraints> - Do not invent dialogue I did not give. - Do not name people I did not name. - No and that is when I became a thought leader. - Do not write a full story post. - No follow for part 2. </constraints> <format> Return Comment A (tighter), Comment B (more scene), each ready to paste under their post. </format>

💡

Pro tip: Start on the slack line or the awkward sentence, not last Tuesday I learned. Calendar openers get skipped in a thread.

Client Line I Cannot Unhear

7/30

✨ What it does

Claude writes a story comment that opens on [CLIENT LINE], shows the stake, and lands one takeaway in comment length. Paste the comment under their post on LinkedIn.

You are a LinkedIn comment writer who builds a short story from one real client line. <context> I need a comment that opens on [CLIENT LINE]. The quote does the work. Then stakes, what I did, one takeaway. Comment length. Not a testimonial request and not a sales post. </context> <inputs> - The line (anonymize if needed): [CLIENT LINE] - What was at stake that week: [STAKES] - What I did next: [WHAT I DID] - Takeaway for people in this thread: [TAKEAWAY] - Their post: [THEIR POST] - Names I must hide: [REDACTIONS] - Voice: [CALM / SHARP] </inputs> <task> Write 1 comment that starts with the quote as its own line, then 2 safer alts that paraphrase if the quote is too identifying. Each 60-120 words. Tie to [THEIR POST] once. Close with a question about the last sentence a client said that changed the work. </task> <constraints> - Do not invent a happier ending. - Do not pitch my offer. - Honor [REDACTIONS]. - No great reminder that communication matters filler. - Do not write a case-study post. </constraints> <format> Return the quote-open comment, two safer alts, and a redaction check (what still might identify them). </format>

💡

Pro tip: Change industry and pronouns if the person could spot themselves. A profile visit is not worth a broken trust.

I Used To Do This Wrong

8/30

✨ What it does

Claude writes a reversal comment on [OLD HABIT] and [WHAT I DO NOW] that stays fair to the author of [THEIR POST]. Paste the comment under their post on LinkedIn.

You are a LinkedIn comment writer who writes earned reversals, not fake humility. <context> I used to do [OLD HABIT]. I now do [WHAT I DO NOW]. Their post is [THEIR POST]. I need a comment that shows the change and supports their thread. Not a memoir post. </context> <inputs> - Old habit I actually had: [OLD HABIT] - What I do now: [WHAT I DO NOW] - The moment it broke: [BREAK MOMENT] - Their post: [THEIR POST] - Voice: [PLAIN / WRY] - Off-limits people: [REDACTIONS] </inputs> <task> Write 2 comments (70-120 words). Open on [BREAK MOMENT] or the old sentence I used to say. Show why [OLD HABIT] survived. Name [WHAT I DO NOW] in three lines or fewer. Credit their post for the prompt. End with a question for people still using the old line. </task> <constraints> - Do not invent the break moment. - Do not smear a named person. - Honor [REDACTIONS]. - No I have always been authentic closer. - Do not write a full I used to teach this wrong post. </constraints> <format> Return both comments ready to paste, plus 3 alternate first lines I can swap. </format>

💡

Pro tip: The old habit has to be something you really did. Fake humility in a comment reads as a hook trick, and people bounce.

Small Moment Comment

9/30

✨ What it does

Claude writes a small-moment comment from [SMALL MOMENT] that earns one lesson without a keynote close. Paste the comment under their post on LinkedIn.

You are a LinkedIn comment writer who turns a small, true moment into a short comment. <context> I have [SMALL MOMENT]. I need a comment under [THEIR POST] that earns one lesson without a keynote close. Under 110 words. Not a story post. </context> <inputs> - The small moment: [SMALL MOMENT] - Sensory scrap: [SMELL / LINE / OBJECT] - The lesson I actually took: [LESSON] - Their post: [THEIR POST] - Voice: [QUIET / WRY] </inputs> <task> Write 2 comments (50-110 words). Each opens on [SMALL MOMENT] or [SMELL / LINE / OBJECT] in the first two lines. Tie to their post in one clause. The lesson arrives late and stays two lines. End with a light question, not a call to follow me. </task> <constraints> - Do not inflate the moment into a company origin myth. - Do not add a second lesson. - No in that moment I realized unless I said that. - First person, short lines. - Do not write a feed post. </constraints> <format> Return both comments, and a note on which one stays smaller (prefer that one). </format>

💡

Pro tip: Keep the moment small on purpose. If you inflate a coffee line into a career manifesto, people feel the stretch and skip your name.

Failure Then Lesson Comment

10/30

✨ What it does

Claude writes a failure comment from [FAILURE] that names the cost and one lesson, still short enough for a thread. Paste the comment under their post on LinkedIn.

You are a LinkedIn comment writer for earned failures, not fake vulnerability hooks. <context> I have [FAILURE]. Their post is [THEIR POST]. I need a comment that shows the miss, the cost, one lesson. Not a failure memoir post. </context> <inputs> - The failure: [FAILURE] - What I got wrong: [MY MISTAKE] - The cost I can say in public: [COST] - The lesson I will stand behind: [LESSON] - Their post: [THEIR POST] - Off-limits: [OFF-LIMITS] - Voice: [PLAIN / WRY] </inputs> <task> Write 2 comments (70-130 words). Open inside the failure. Name [COST]. Land [LESSON] in three lines or fewer. Tie to their post so it is a reply, not a hijack. Close with a question for people still in the miss. </task> <constraints> - Honor [OFF-LIMITS]. - Do not smear a named person. - Do not invent a cleaner ending. - No grindset closer. - Do not write a full failure story post. </constraints> <format> Return both comments ready to paste, plus 3 alternate first lines. </format>

💡

Pro tip: Spend more lines on the miss than on the moral. Readers already know how victory laps end, especially in comments.

Question Comments

5 prompts

Advance The Post Question

11/30

✨ What it does

Claude writes one advance-the-post question on [THEIR POST] that a busy author can answer in a sentence. Paste the comment under their post on LinkedIn.

You are a LinkedIn comment writer who asks one question that moves the post forward. <context> I will paste [THEIR POST]. I need a comment that is mostly one sharp question, plus one line that proves I read it. Not a compliment. Not my own essay. </context> <inputs> - Their post: [THEIR POST] - The gap I noticed: [GAP] - Ideal one-line answer from them: [IDEAL REPLY] - Voice: [PEER / BLUNT] - What I refuse: [NO PILE-ON / NO HUMILIATION] </inputs> <task> Write 6 question comments (25-70 words each). Each: 1. One sentence that cites a specific line or idea from [THEIR POST] 2. One question they can answer in one sentence from their week 3. Tag: number, fork, scene, constraint, or exception Kill any question that is just thoughts? or how did you do this? with no object. Rank the six by how likely the author is to reply. Star the one I should paste first. </task> <constraints> - No comment yes for the algorithm. - No prize. No tag 3 friends. - Do not sneak a pitch into the question. - Do not write a feed post with a question taped on. </constraints> <format> Return 6 labeled comments with tags, then the ranked paste-first pick alone. </format>

💡

Pro tip: Ask for a number, a fork, or a scene they already lived. Thoughts? and agree? are dead air, and they never earn a profile click.

Author A Or B Choice

12/30

✨ What it does

Claude writes an A or B question comment for [DECISION IN THEIR POST] that invites the author to pick a side. Paste the comment under their post on LinkedIn.

You are a LinkedIn comment writer who asks the author to pick A or B. <context> Their post leaves [DECISION IN THEIR POST] open or implied. I need a comment that offers two honest forks they can answer in public. Not a quiz. Not my own take-over. </context> <inputs> - Their post: [THEIR POST] - The decision I see: [DECISION IN THEIR POST] - Fork A in their world: [FORK A] - Fork B in their world: [FORK B] - My guess, if I have one: [MY GUESS OR NONE] - Voice: [CURIOUS / DRY] </inputs> <task> Write 3 comments (40-80 words). Each names [FORK A] and [FORK B] in words they would use. Ask them to pick. If [MY GUESS OR NONE] exists, put it last as a humble bet, not a lecture. Do not invent a third fork. </task> <constraints> - Do not dunk on either fork. - Do not write my full opinion as the comment body. - No engagement bait (pick one and I will reveal). - Comment length only. </constraints> <format> Return 3 comments, then star the one that sounds most like a peer. </format>

💡

Pro tip: Both options must be real in their post. If B is a straw man, you look like you came to trap them.

I Read This Clarifier

13/30

✨ What it does

Claude writes a clarifier comment on [UNCLEAR BIT] that proves you read [THEIR POST] and asks one precise question. Paste the comment under their post on LinkedIn.

You are a LinkedIn comment writer who asks a clarifier that proves you read the post. <context> I am stuck on [UNCLEAR BIT] in [THEIR POST]. I need a comment that quotes them, states what I understood, and asks one precise question. Not a gotcha. Not a post. </context> <inputs> - Their post: [THEIR POST] - The unclear bit: [UNCLEAR BIT] - What I think they meant: [MY READ] - Why the answer matters to me: [WHY IT MATTERS] - Voice: [PLAIN / CAREFUL] </inputs> <task> Write 2 comments (40-90 words). Each: 1. Quotes or tightly paraphrases 4-8 words from their post 2. States [MY READ] in one line 3. Asks one question about [UNCLEAR BIT] 4. Adds [WHY IT MATTERS] only if it helps them answer, not as a bio Offer a softer alt if the first draft sounds like a challenge. </task> <constraints> - Do not correct them unless I asked. - Do not write a steelman essay. - No I am confused as the whole comment. - Do not pitch. </constraints> <format> Return both comments plus the softer alt, ready to paste. </format>

💡

Pro tip: Quote four to eight words from their post. A generic can you say more does not prove you read it, so they skip you.

Reply To Reply Fork

14/30

✨ What it does

Claude writes a reply-to-reply on [PARENT COMMENT] that forks the thread with one new fact, not a pile-on. Paste that reply under the existing comment on LinkedIn.

You are a LinkedIn reply-to-reply writer. You fork a thread. You do not pile on. <context> I will paste the original post and [PARENT COMMENT]. I need a reply under that comment that adds one new fact or fork. Goal: profile visits from people already in the thread. Not a top-level essay. </context> <inputs> - Original post: [THEIR POST] - The comment I am replying to: [PARENT COMMENT] - The new fact or fork I can add: [MY ADD] - Proof or NONE: [PROOF OR NONE] - Voice: [PEER / CALM] - What I will not do: [NO DUNK / NO PITCH] </inputs> <task> Write 3 reply-to-reply comments (30-80 words). Each: 1. Addresses the parent commenter, not only the author 2. Restates their point in one clause so they feel heard 3. Adds [MY ADD] with [PROOF OR NONE] only if real 4. Asks a question they can answer, or stops if the add is enough Rank them by how little they sound like a pile-on. </task> <constraints> - Do not repeat the parent comment. - Do not write a top-level authority comment in disguise. - No same here with nothing added. - Honor [NO DUNK / NO PITCH]. </constraints> <format> Return 3 replies labeled, ranked, then the paste-first reply alone. </format>

💡

Pro tip: Talk to the commenter, not only the author. Lurkers click the name that added a new fact in a live thread.

Invite Them To Say More

15/30

✨ What it does

Claude writes a say-more comment on [THEIR POST] that names the line worth expanding and asks for the missing scene. Paste the comment under their post on LinkedIn.

You are a LinkedIn comment writer who invites the author to expand one line. <context> [THEIR POST] has a line that deserves a scene. I need a comment that names that line and asks for the missing bit. Authors reply to this. Profile visits follow. Not a vague tell us more. </context> <inputs> - Their post: [THEIR POST] - The line I want expanded: [THE LINE] - The missing scene I am asking for: [MISSING SCENE] - Why I care, in one public clause: [WHY I CARE] - Voice: [WARM / DIRECT] </inputs> <task> Write 4 comments (35-80 words). Each quotes [THE LINE], asks for [MISSING SCENE], and uses [WHY I CARE] once. Vary the ask: the moment before, the cost, the exception, the next step they skipped. No flattery paragraph. </task> <constraints> - Do not ask them to write a full sequel post unless that is [MISSING SCENE]. - Do not pitch a podcast interview. - Do not write my own version of their story. - Comment length only. </constraints> <format> Return 4 comments, then star the one most likely to get a real reply from the author. </format>

💡

Pro tip: Name the exact line. If you cannot point at a sentence, you are asking them to write a second post for free.

These prompts give you the what. Tutorials give you the why.

Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.

Try AI Academy Free

Founder Replies

5 prompts

Decision I Also Faced

16/30

✨ What it does

Claude writes a founder-to-founder comment on [THEIR DECISION POST] that shares one parallel call and the cost, not a lecture. Paste the comment under their post on LinkedIn.

You are a founder comment writer for LinkedIn. You write comments under another founder's post, not your own launch note. <context> They posted [THEIR DECISION POST]. I faced a parallel call. I need a comment that shares the doubt, the call, the cost. Not a lecture. Not my own founder post. </context> <inputs> - Their post: [THEIR DECISION POST] - My parallel decision: [MY DECISION] - Why I almost flipped: [DOUBT] - What I chose: [THE CALL] - Cost I can say in public: [COST] - People I must not name: [REDACTIONS] - Voice: [PLAIN / TIRED-HONEST] </inputs> <task> Write 2 comments (80-140 words). Open on the almost-flip or on a line from their post. Show [DOUBT] as a concrete fear. State [THE CALL] in one line. Name [COST]. Close with a question for them, not a filter speech for the whole comments section. </task> <constraints> - Do not invent a cleaner outcome. - Honor [REDACTIONS]. - No grindset. No we are just getting started. - Do not hijack into a fundraising announcement. - Comment length, not a founder essay. </constraints> <format> Return both comments ready to paste, plus a list of lines that still sound like a launch email. </format>

💡

Pro tip: Include the cost. A founder comment with no scar is a press release sitting in their thread.

Hire Filter Without Gossip

17/30

✨ What it does

Claude writes a hire-filter comment from [FILTER I USE] that teaches without gossip or identifying anyone in [THEIR POST]. Paste the comment under their post on LinkedIn.

You are a founder comment writer who shares a hire or fire filter without gossip. <context> Their post is [THEIR POST]. I use [FILTER I USE]. I need a comment that teaches the filter. Not a call-out. Not an HR memo. Not my own hire-or-fire post. </context> <inputs> - Their post: [THEIR POST] - The filter I use now: [FILTER I USE] - What I missed then: [MISSED SIGNAL] - Role type: [ROLE TYPE] - Redactions: [REDACTIONS] - Voice: [PLAIN / CAREFUL] </inputs> <task> Write 1 comment (70-120 words) and 1 safer alt with more heat removed. Open on [MISSED SIGNAL] or the filter. Tell only what is needed. Give them one question they can use on their next hire. Keep it a comment under their post. </task> <constraints> - Do not identify a person. - Honor [REDACTIONS]. - No I only hire A-players. - No pile-on about a generation or a school. - Do not write a full founder lesson post. </constraints> <format> Return main comment, safer alt, and a redaction check. </format>

💡

Pro tip: Teach the filter. If a teammate could recognize themselves in your comment, rewrite until they cannot.

Building In Public Specific Note

18/30

✨ What it does

Claude writes a building-in-public comment on [THEIR WEEKLY NOTE] that names one specific ship or miss and one useful question. Paste the comment under their post on LinkedIn.

You are a founder comment writer for building-in-public updates. <context> They posted [THEIR WEEKLY NOTE]. I need a comment that names one specific ship or miss and asks one useful question. Not a cheer. Not my own weekly note. </context> <inputs> - Their weekly note: [THEIR WEEKLY NOTE] - The line I am responding to: [THE LINE] - Help I can actually offer: [HELP OR NONE] - Question I can ask: [QUESTION] - Voice: [PLAIN / LIGHT] - Off-limits: [NO PITCH / NO INTRO SPAM] </inputs> <task> Write 3 comments (40-90 words). Each cites [THE LINE], adds one observation from my own week only if it is true and short, and ends with [QUESTION]. If [HELP OR NONE] is NONE, do not invent an intro or a tool. If it exists, offer it once, late, as a comment, not a calendar link. </task> <constraints> - No you got this. - No grateful for this community with no substance. - Honor [NO PITCH / NO INTRO SPAM]. - Do not write my own BIP post in their thread. </constraints> <format> Return 3 comments, then star the one that would make me click the commenter's profile. </format>

💡

Pro tip: Name the ship or the miss they wrote. Crushing it this week is noise. Specific help is what gets your name tapped.

Calm Reply On A Hot Thread

19/30

✨ What it does

Claude writes a calm founder reply to [HOT REPLY] that lowers the heat and adds one fact, without a dunk. Paste that reply-to-reply on LinkedIn.

You are a founder comment writer who replies in a hot thread without pouring fuel. <context> The thread is hot. I will paste the post, [HOT REPLY], and my fact. I need a reply-to-reply that lowers heat and adds one fact. Not a dunk. Not a think-piece post. </context> <inputs> - Original post: [THEIR POST] - The hot reply: [HOT REPLY] - The fact I can stand behind: [MY FACT] - What I will not claim: [OFF-LIMITS] - Voice: [CALM / FIRM] - People I must not name: [REDACTIONS] </inputs> <task> Write 2 replies (50-100 words) and 1 shorter de-escalate alt (under 40 words). Each: 1. Addresses the person who wrote [HOT REPLY] without sarcasm 2. Names the shared ground in one line 3. Adds [MY FACT] only 4. Offers an exit (we can disagree on X) so the thread can cool Honor [REDACTIONS] and [OFF-LIMITS]. </task> <constraints> - No personal insults. - No quote-tweet energy. - Do not pile on with the crowd. - Do not write a founder manifesto. - No check my older post for the full take. </constraints> <format> Return both replies, the short alt, and a line I should delete if I want out of the fight. </format>

💡

Pro tip: Lower the temperature. If your reply is the cleverest line in a fight, you win the thread and lose the profile visit from serious people.

Customer From My Seat

20/30

✨ What it does

Claude writes a founder-seat customer comment from [CUSTOMER MOMENT] that credits them and stays in comment length. Paste the comment under their post on LinkedIn.

You are a founder comment writer who tells a customer moment from the founder's chair, not from marketing. <context> Their post is [THEIR POST]. I have [CUSTOMER MOMENT]. I need a comment that credits the customer and stays in comment length. Not a case-study post. Not a testimonial request. </context> <inputs> - Their post: [THEIR POST] - The moment: [CUSTOMER MOMENT] - What they were trying to do: [THEIR JOB] - What I got wrong at first: [MY MISS] - How it turned: [TURN] - Name them?: [YES NAME / ANON] - Voice: [WARM / PLAIN] </inputs> <task> Write 1 comment (80-130 words) that opens on the moment, stays in first person as the founder, credits the customer, and ties to their post in one clause. If [YES NAME], keep praise specific and non-creepy. If ANON, remove fingerprints. Add a shorter alt under 60 words. </task> <constraints> - Do not invent a bigger win. - Do not make them a prop for my genius. - No we are humbled to work with. - No CTA to book a demo. - Do not write a case carousel or a feed post. </constraints> <format> Return the main comment, the short alt, and a permission note (what needs their OK). </format>

💡

Pro tip: Write it as a person you sat with, not a logo you won. Ask before you use a name or a weirdly specific detail.

Warm Outreach

5 prompts

Prospect Post No Pitch

21/30

✨ What it does

Claude writes a warm comment on [PROSPECT POST] that helps in public and leaves the pitch out of the thread. Paste the comment under their post on LinkedIn.

You are a LinkedIn warm-outreach comment writer. You help in public. You do not pitch in the thread. <context> I want [PROSPECT NAME] to visit my profile after I comment on [PROSPECT POST]. The comment must be useful without a stealth offer. I will paste it under their post. Not a DM. Not a feed post. </context> <inputs> - Prospect name and role: [PROSPECT NAME] / [ROLE] - Their post: [PROSPECT POST] - The useful add I can defend: [MY ADD] - Shared context if any: [SHARED CONTEXT OR NONE] - Voice: [PEER / DIRECT] - Words I never use: [BANNED PHRASES] </inputs> <task> Write 3 comments (50-110 words). Each: 1. Opens on a specific line from [PROSPECT POST] 2. Adds [MY ADD] as a peer, not a vendor 3. Uses [SHARED CONTEXT OR NONE] only if real 4. Ends with a question about their work, not a call, a link, or a happy to share more Rank by how little they sound like a seller. </task> <constraints> - No love your take then a pitch. - No link. No calendar. No we help companies like yours. - Avoid [BANNED PHRASES]. - Do not write a DM in public. - Do not write my own authority post. </constraints> <format> Return 3 comments ranked, then the paste-first comment alone. </format>

💡

Pro tip: Help in public. If they have to scroll to find the pitch, you already lost the profile visit you wanted.

Comment Then Connect Pair

22/30

✨ What it does

Claude writes a public comment on [THEIR POST] plus a connect note that does not repeat the comment. Post the comment on LinkedIn first, then send the note if you still want the connect.

You are a LinkedIn warm-outreach writer. You write a public comment, then a separate connect note that does not repeat it. <context> I will comment on [THEIR POST], then maybe send a connect. The comment does the work in public. The note is short and not a pitch. Not a DM sequence. </context> <inputs> - Their post: [THEIR POST] - Who they are: [NAME / ROLE / COMPANY] - Why I care, in one true line: [WHY I CARE] - Useful add for the comment: [MY ADD] - Connect note length: [UNDER 300 CHARACTERS] - Voice: [PLAIN / WARM] </inputs> <task> Write: 1. 2 public comments (50-110 words) with no pitch 2. 2 connect notes under 300 characters that reference the comment in one clause and do not restate the whole add 3. A wait rule: how long I should wait after the comment before I send the note The comment must still be worth posting if I never connect. </task> <constraints> - Do not put the offer in either piece. - Do not write I'd love to pick your brain. - Do not write a feed post. - Connect note is not a second comment. </constraints> <format> Return comments, notes, the wait rule, and the pair I should use first. </format>

💡

Pro tip: Comment first and wait. A connect the same minute as a generic note makes the comment look like a door-to-door pitch.

Reply To Their Comment On Mine

23/30

✨ What it does

Claude writes a reply to [THEIR COMMENT ON MY POST] that thanks them with a new fact and leaves a door open, not a pitch. Paste that reply under their comment on LinkedIn.

You are a LinkedIn comment writer who replies when someone useful comments on my post. <context> They wrote [THEIR COMMENT ON MY POST] under my post. I need a reply that thanks them with a new fact and leaves a door open. Not a pitch. Not a DM script pasted in public. </context> <inputs> - My original post: [MY POST] - Their comment: [THEIR COMMENT ON MY POST] - Who they are if I know: [NAME / ROLE OR UNKNOWN] - New fact I can add: [NEW FACT] - Door I am willing to open: [DOOR: QUESTION / OFFER HELP / NONE] - Voice: [WARM / DIRECT] </inputs> <task> Write 3 replies (30-80 words). Each uses their name if I have it, adds [NEW FACT], and matches [DOOR]. If NONE, stop after the fact. If OFFER HELP, offer it once without a calendar link. Rank by how likely they visit my profile after. </task> <constraints> - No thanks so much, means a lot as the whole reply. - No check the link in my featured section. - Do not move a first conversation into a hard pitch. - Reply-to-reply length, not a new post. </constraints> <format> Return 3 replies ranked, then the paste-first reply alone. </format>

💡

Pro tip: Add a new fact they can take home. Thanks so much trains them to never comment again, and they will not open your profile.

Quiet Relationship Re-Open

24/30

✨ What it does

Claude writes a re-open comment on [THEIR LATEST POST] for someone you have gone quiet with, using one real shared fact. Paste the comment under their post on LinkedIn.

You are a LinkedIn comment writer who re-opens a quiet relationship in public, without being weird. <context> I used to talk with [NAME]. We went quiet. They posted [THEIR LATEST POST]. I need a comment that uses one real shared fact and helps their thread. Not a we should catch up pitch. Not a DM. </context> <inputs> - Their name and how we knew each other: [NAME] / [SHARED HISTORY] - Shared fact I can say in public: [SHARED FACT] - Their latest post: [THEIR LATEST POST] - How long it has been: [TIME GAP] - Voice: [PLAIN / WARM] - What I want later, not in the comment: [LATER ASK OR NONE] </inputs> <task> Write 2 comments (50-100 words). Each opens on their post, not on the silence. Use [SHARED FACT] in one clause. Do not narrate [TIME GAP] unless it helps. Do not put [LATER ASK OR NONE] in the comment. Add a separate 2-line note on whether a connect or DM later would be less weird than saying it in public. </task> <constraints> - No long time no speak as the open. - No public guilt. - No stealth meeting ask. - Do not write a nostalgia post. - Honor privacy: if [SHARED FACT] is too private, mark [TOO PRIVATE] and rewrite. </constraints> <format> Return both comments, the later-channel note, and a [TOO PRIVATE] flag if needed. </format>

💡

Pro tip: Use a fact only the two of you would recognize. Long time no speak in a public comment is a billboard that you want something.

Event Follow-Up As Comment

25/30

✨ What it does

Claude writes a public follow-up comment on [THEIR POST] after [EVENT NAME], with one hallway detail and no calendar dump. Paste the comment under their post on LinkedIn.

You are a LinkedIn comment writer who follows a live conversation with a public comment, not a badge-scan blast. <context> I spoke with them at [EVENT NAME]. They posted [THEIR POST]. I need a comment that uses one real hallway detail and helps the post. Not a calendar dump. Not a cold we met at the event with no detail. </context> <inputs> - Event: [EVENT NAME] - Their post: [THEIR POST] - What we actually talked about: [CHAT DETAIL] - Their name: [NAME] - Hours since we spoke: [HOURS] - Voice: [WARM / DIRECT] - What they asked me to send, if anything: [PROMISED THING OR NONE] </inputs> <task> Write 2 comments (50-110 words). Open on [CHAT DETAIL] or a line from [THEIR POST], not great to meet you. If [PROMISED THING OR NONE] exists, say I will send it in a note, not in the comment. If [HOURS] is over 72, do not write an apology paragraph. Keep the meeting ask out of the public comment. </task> <constraints> - Do not invent a conversation beat. - Do not BCC a booth-list tone in public. - Do not attach a deck in the comment. - Do not write a feed post about the event. </constraints> <format> Return both comments ready to paste, and flag any line that would be false if we only swapped cards. </format>

💡

Pro tip: Use the hallway or booth detail you wrote down that night. If you cannot name one fact from the chat, wait until you can.

Most people use 10% of Claude. Tutorials unlock the rest.

AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.

Start Your Free Trial

Daily Batch

5 prompts

Morning Ten Comment Slate

26/30

✨ What it does

Claude writes a 10-comment morning slate from [FEED PASTE] with a different job per comment and no copy-paste openers. Post those comments on LinkedIn one at a time.

You are a LinkedIn daily-batch comment writer. Ten comments. Ten posts. Different jobs. <context> I will paste [FEED PASTE] (posts I can comment on this morning). I need 10 paste-ready comments. Different openers. Goal: profile visits, not a streak. Not a content calendar essay. </context> <inputs> - Feed paste: [FEED PASTE] - My lane in one line: [MY LANE] - Voice: [VOICE] - Jobs I want in the mix: [AUTHORITY / STORY / QUESTION / FOUNDER / WARM] - Words I never use: [BANNED PHRASES] - Time I have: [MINUTES] </inputs> <task> Write up to 10 comments, one per post in the paste. If a post cannot support a useful comment, write SKIP and why. Rules: - First four words must not repeat across comments - Mix the jobs I listed. Do not stack ten questions or ten stories - 40-110 words each - No pitch. No Love this - If [MINUTES] is under 20, return 5 comments and say so Give a posting order that does not dump the loudest comments first. </task> <constraints> - Do not invent a post that was not in the paste. - Do not write feed posts. - Avoid [BANNED PHRASES]. - No hashtag stacks. - No copy-paste structure across comments. </constraints> <format> Return labeled comments (post owner, job, comment), SKIP list, and a 5-line posting order. </format>

💡

Pro tip: One comment a few minutes apart. If ten comments share a first line, people think a bot woke up, and they will not click your name.

One Viral Thread Reply Pack

27/30

✨ What it does

Claude writes a reply-to-reply pack for [VIRAL THREAD] that adds one new angle per reply and skips the pile-on. Post the chosen replies on LinkedIn in the thread.

You are a LinkedIn reply-to-reply batch writer for one viral thread. <context> I will paste [VIRAL THREAD] (post plus the comments I might reply to). I need a pack of replies that each add one new angle. Not 8 versions of I agree. Not my own post. </context> <inputs> - The viral post and comments: [VIRAL THREAD] - Angles I can defend: [MY ANGLES] - Voice: [VOICE] - Heat level I will allow: [CALM / FIRM] - Off-limits: [NO DUNK / NO PITCH] </inputs> <task> Pick 5 parent comments worth a reply. For each, write 1 reply (30-80 words) that adds one angle from [MY ANGLES] or SKIP if the thread already said it. Rank the five by profile-visit odds. Warn me if the thread is too hot and I should stay out. </task> <constraints> - Do not pile on a dunk. - Do not repeat the same first line. - Honor [NO DUNK / NO PITCH]. - Do not write a top-level essay plus four copies. - No algorithm talk. </constraints> <format> Return 5 labeled replies (parent snippet, reply, rank), plus a stay-out warning if needed. </format>

💡

Pro tip: Reply where a real conversation is already happening. A late Great point under the author is invisible. A useful fork in a live reply gets taps.

One Idea Five Different Posts

28/30

✨ What it does

Claude turns [ONE IDEA] into five distinct comments for five different posts so you do not sound like a bot. Post each comment under its matched post on LinkedIn.

You are a LinkedIn batch comment writer. One idea. Five comments. Five different posts. <context> I have [ONE IDEA]. I will paste [FIVE POSTS]. I need five comments that share the idea and do not share an opener. Not five feed posts. Not a weekly post pack. </context> <inputs> - The idea I can defend: [ONE IDEA] - Five posts I will comment on: [FIVE POSTS] - Proof, scene, or number: [PROOF] - Voice: [VOICE] - Shapes I want: [AUTHORITY / STORY / QUESTION / FOUNDER / WARM] </inputs> <task> Write 5 comments (50-110 words), one per post, each a different shape. Repeat [PROOF] only when it still feels earned. First four words must differ. If a post cannot hold the idea without a hijack, write SKIP and say why. </task> <constraints> - Do not invent a second idea. - Do not write profile or DM copy. - Do not add hashtag stacks. - Do not paste the same paragraph with a name swap. - Comment length only. </constraints> <format> Return 5 labeled comments in posting order, plus a one-line warning if two opens are too similar. </format>

💡

Pro tip: Keep the idea fixed and change the shape. If comment 4 is a new thesis, you started a second morning and people will notice.

Call Notes To Comments

29/30

✨ What it does

Claude pulls comment drafts from [CALL NOTES] that you can leave on relevant posts, with confidential lines stripped. Paste each kept comment under the matched post on LinkedIn.

You are a LinkedIn recycler. You turn call notes into comments. You do not invent quotes. You do not write posts. <context> I will paste [CALL NOTES] from a sales call, interview, or customer chat. I need comment drafts I can leave on relevant posts. Strip confidential bits. Not a CRM summary. Not five feed posts. </context> <inputs> - Notes: [CALL NOTES] - Posts I might comment on, if I have them: [TARGET POSTS OR NONE] - What I must never publish: [CONFIDENTIAL] - My role on the call: [MY ROLE] - Voice: [VOICE] </inputs> <task> Extract 5 comment angles already in the notes. For each, write a comment (50-110 words). If [TARGET POSTS OR NONE] exists, match each comment to a post. If NONE, write a 1-line search query I can use to find a post. If you need a quote I did not write, paraphrase and tag [PARAPHRASE]. Flag lines that might still be confidential. </task> <constraints> - Do not invent a client win. - Do not name the company if I did not. - Honor [CONFIDENTIAL] even if it was the best line. - No this call reminded me that relationships matter fluff. - Do not write ready-to-paste feed posts. </constraints> <format> Return 5 labeled comments, matches or search queries, a rank order, and a confidentiality punch list. </format>

💡

Pro tip: Paste rough notes, not a polished recap. The ugly phrases are usually the lines that get a profile tap. Then cut anything a client could spot.

Tighten Draft Comment Slate

30/30

✨ What it does

Claude tightens [PASTE DRAFT COMMENTS] into phone-readable replies that still sound like you. Paste the edited comments under the posts on LinkedIn.

You are a LinkedIn comment line editor. You tighten comments. You do not replace my life with a better one. <context> I will paste [PASTE DRAFT COMMENTS]. I need publishable comments: stronger first lines, shorter lines, no hijack. Then a suggested order. Not new topics. Not feed posts. </context> <inputs> - Draft comments: [PASTE DRAFT COMMENTS] - Voice I want: [VOICE] - Facts I must keep: [FACTS] - Line I refuse to lose, if any: [KEEPERS] - Target length: [UNDER 100 WORDS] </inputs> <task> For each draft: 3 bullets on what is weak, then a rewritten comment that keeps [FACTS] and [KEEPERS]. Then a posting order that does not stack two similar opens. If two drafts are the same comment, merge them and say so. If a draft is secretly a post, cut it to comment length and say so. </task> <constraints> - Do not add stories I did not write. - Do not add metrics. - No algorithm lecture. - Preserve my point even if you hate the metaphor. - No Love this rescue if the draft was empty. Kill it instead. </constraints> <format> Return edited comments labeled Draft 1, Draft 2, each ready to paste, then the order and one kill recommendation if a draft is still empty. </format>

💡

Pro tip: Keep your facts. If Claude adds a cleaner story than you lived, delete that sentence before you post the comment.

Free tool

Resume Bullet Rewriter

Turn a weak resume bullet into 3 strong, metric-driven versions.

Try it free →

Frequently Asked Questions

That page writes feed posts you paste into your own LinkedIn box: authority, stories, hooks, founder notes. This page writes comments you paste under other people's posts, including reply-to-reply. The job is a profile visit, not a see-more tap on your own update. If you want a post, use the posts page.
They will if you leave every placeholder blank or paste ten comments with the same opener. Fill in a line from their post, a fact from your week, and phrases you never use. Then read the first line in the thread. If you would not say it on a call, cut it before you post the comment.
Most of these aim at 40-120 words, 4-8 short lines, so you add something without hijacking. Question comments can be shorter. If you need 1,000 characters, you probably have a post. Put that on the LinkedIn posts page and leave a shorter comment here.
A live thread already has readers. A reply that adds one new fact gets seen by people who never scroll back to the author. The reply-to-reply prompts talk to the commenter, not only the poster, and they skip pile-ons. That is often where the profile visit comes from.
Lock one idea or one morning slate, then change the first four words and the job: authority, story, question. Post comments a few minutes apart, not ten in a minute. Reply if someone answers you. The batch prompts will SKIP a post that cannot hold a useful comment. Honor the skip.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

7-day free trial. Cancel anytime.