agentleFS
Sign inStart free
prosyo-aiprosyo-ai/gtm-skill/skills/linkedin-comment-strategy/SKILL.md

linkedin-comment-strategy

Skill13 starsChanged 22 days agoMITView on GitHub

Use this skill when you want to use LinkedIn comments to get noticed by target buyers before reaching out: \"comment strategy for prospects\", \"warm up accounts on LinkedIn\", \"write thoughtful comments\". Builds a list of target buyers and the voices they follow, sets a daily commenting routine, and writes comments that add an insight, a question or a relevant experience so prospects recognise your name when your connection request arrives.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this to warm up Tier 1 buyers before outreach.

    line 16
  2. Distinctive:

    After two or three meaningful interactions, send a connection request that references the thread.

    line 45
  3. Distinctive:

    MUST add a genuine insight, example or question in each comment.

    line 55
  4. Distinctive:

    MUST draw only on the commenter's real experience.

    line 56
  5. Distinctive:

    NEVER pitch or link to your product in a comment on someone else's post.

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Use this to warm up Tier 1 buyers before outreach. A few thoughtful comments on a buyer's posts over two weeks make your later connection request familiar rather than cold.

Inputs

  • Target buyers (and whether they post), plus the industry voices they engage with.
  • Topics the commenter can speak to with real experience.
  • Time available: 15-30 minutes a day is enough.

The play

1. Build the watch list

  • Buyers who post: comment on their posts directly.
  • Buyers who don't post: find the voices and communities they engage with; comment there, where they read.
  • 20-40 people on the list at a time.

2. Write comments that add something

Comment typeExample
Add an insight"We saw the same thing; the twist for us was that approvals, not accounting, drove the delay."
Add a number or example"One team I work with went from 9 days to 4 by adding a day-3 cut-off."
Ask a sharp question"Did the 6-day close hold through quarter end, or does that need a different playbook?"
Respectful disagreement"Agree on the goal, but in our experience the tool came last, not first."

Two to four sentences. No pitch, no links, no "Great post!".

3. Keep a rhythm

Per day: 5-10 comments, mostly on target buyers' content and the voices they follow. Reply to replies on your comments within a few hours; those threads are where real conversations start.

4. Convert to connection

After two or three meaningful interactions, send a connection request that references the thread. Then the first message continues the topic.

What good looks like

  • The buyer replies to your comment, or likes it, before you ever send a request.
  • Comments would be useful to any reader of the post, not only the author.
  • The common mistake is "Great insights, thanks for sharing!" on 50 posts a day, which builds nothing and looks automated.

Rules

  • MUST add a genuine insight, example or question in each comment.
  • MUST draw only on the commenter's real experience.
  • NEVER pitch or link to your product in a comment on someone else's post.
  • NEVER automate comments.

Example prompts

  • "Set up a 2-week comment plan to warm up these 15 CFOs before outreach."
  • "Write a thoughtful comment on this post from a VP Sales about SDR ramp."
  • "Which voices do heads of RevOps follow, so I can show up there?"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free