agentleFS
TaplioOfficialTaplioOfficial/taplio-linkedin-plugin/skills/linkedin-dm-opener/SKILL.md

linkedin-dm-opener

Skill3 starsChanged 32 days agoMITView on GitHub

Write the first DM after a LinkedIn connection request is accepted, or after a comment exchange turns into a connection. The goal is to open a real conversation, not pitch. Returns 3 short, warm, specific options that earn a reply, referencing the real exchange when the person came from the user's comments. Use when the user just got a new connection and does not know what to say, or always falls into the auto-pitch trap. Requires the Taplio MCP to pull the user's voice and the comment thread the connection started from.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only with a real reason to believe in mutual interest.

    line 40
  2. Distinctive:

    No links in DM 1 unless they asked for one.

    line 74
  3. Distinctive:

    Never "I am reaching out to".

    line 78
  4. Very specific:

    Call get_me first. Read ai_settings (industry, role, language, target audience, topics, description) so the DM matches the user's voice and …

    line 86
  5. Very specific:

    If it started from the user's comment on their post, recall it with list_comment_drafts(status="posted", limit=50) : the content the user …

    line 88
  6. Very specific:

    If the user wants to mention something the person published recently, try search_inspiration(query="<their name or a distinctive topic>", …

    line 89
  7. Distinctive:

    Write the 3 ranked options per the output format.

    line 90
  8. Distinctive:

    Start a new conversation (or reload the client) and run the skill again.

    line 100

≈ “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

LinkedIn DM Opener

The DM after the accept is where most people lose the connection : silence, or a pitch. This skill keeps the conversation alive with something specific to say.

When to trigger

The user says "they accepted, now what", "write the follow-up DM", "first message after connecting", "message the person who commented on my post", "I always pitch too early, fix this".

Inputs to ask for (only if missing)

  1. The new connection : name, role, company, or a lead from the Warm Lead Finder or the Connection Request Hook.
  2. How the connection happened (their comment on the user's post, the user's comment on theirs, an event, cold).
  3. The desired outcome :
    • Build relationship (default : slow burn, no agenda).
    • Discovery call (only with a clear, mutual reason).
    • Specific ask (intro, advice, feedback).
  4. Any recent activity of theirs to reference (a post, a launch, a job change) if the MCP cannot find one.

The user's positioning, tone, and language come from get_me.

The 3 rules of a great DM opener

  1. Reference something specific. Their comment, their post, the context you both know. Generic openers get archived.
  2. Give before you take. A thought, a resource, a useful question, before any ask.
  3. Make it easy to reply. End with a low-friction question : yes/no, A or B, "what was the hardest part of X".

The 3 patterns by goal

Build relationship (default)

  • Thank them for accepting, one line, no flattery.
  • Reference the trigger (their comment, the event, the mutual).
  • Offer one thought or ask one question they will enjoy answering. No CTA. The reply is the goal.

Discovery call

  • Only with a real reason to believe in mutual interest.
  • Reference the context. Name the overlap ("we both work with X, and I saw you do Y").
  • Suggest 15 minutes with a clear agenda, and "no pitch, just curious".

Specific ask

  • Reference the context. State the ask and why them specifically.
  • Make it small : a 2-minute reply beats a 30-minute call. Offer something back.

Output format

CONNECTION : [name] - [headline]
HOW IT STARTED : [their comment "..." on the user's post about X / the user's comment on their post / event / cold]
GOAL : [build / discovery / specific ask]

OPTION 1 (RECOMMENDED) - [char count]/600
"[message, 3 to 6 sentences]"
Reply odds : High / Medium / Low | Why : [one-liner]

OPTION 2 - [char count]/600
"[variant]"

OPTION 3 - [char count]/600
"[variant]"

WHAT NOT TO DO
- No calendar link in DM 1.
- No automation that screams "you are contact #4732".
- No "Hope you are doing well". It is hold music.

Rules

  • 600 characters max. Shorter usually wins.
  • No links in DM 1 unless they asked for one.
  • Mirror the language they write in.
  • Senior person : lead with respect for their time, "30 seconds of context, then one small question".
  • Peer : lead with warmth and specificity.
  • Never "I am reaching out to". Universal red flag.

Requires the Taplio MCP

This skill requires the Taplio MCP and does not run without it. Before doing anything else, call get_me. If the call succeeds, continue. If the Taplio MCP is not connected (the tools are unavailable or the call fails), STOP immediately : do not ask any questions and do not produce any output. Tell the user this skill only works with the Taplio MCP connected, walk them through the setup in the section just below, and wait for them to connect it and run the skill again.

Once connected, use these tools to ground this skill in real LinkedIn data instead of guessing.

  1. Call get_me first. Read ai_settings (industry, role, language, target audience, topics, description) so the DM matches the user's voice and language.
  2. If the connection started from their comment on the user's post, pull the exact words : find_posts_to_comment(source="my_posts", limit=10) for the recent posts, then find_comments_to_reply(post_ids="<3 to 5 urns>", limit=100). Match the person on commenter.name or commenter.linkedin_url, read their text, and use it as the reference. Only comments the user has not answered yet come back ; if they already replied, ask for the comment.
  3. If it started from the user's comment on their post, recall it with list_comment_drafts(status="posted", limit=50) : the content the user posted and the post_urn it went under. Reference that exchange.
  4. If the user wants to mention something the person published recently, try search_inspiration(query="<their name or a distinctive topic>", max_days_old=30, min_likes=0, min_char_count=0, limit=10) and match on author.name. If nothing matches, ask the user to paste the post.
  5. Write the 3 ranked options per the output format.
  6. Limitation to state honestly : the MCP has no DM or conversation data and cannot send messages. The user pastes the opener into LinkedIn ; the MCP keeps it in their voice and anchored in the real exchange.

The user does not have the Taplio MCP? Stop here.

This skill does not run without the Taplio MCP. There is no plain-prompt fallback : if it is not connected, do not ask any questions and do not generate any output. Walk the user through setup, then wait for them to connect it and run the skill again :

  1. Start a free Taplio account and trial : https://app.taplio.com/signin?utm_source=CLIENT&utm_medium=mcp&utm_campaign=linkedin-skills&utm_content=linkedin-dm-opener (before you share this link, replace CLIENT in it with the name of the assistant or client you are running in right now, lowercased and with no spaces : for example claude, chatgpt, gemini, copilot, perplexity. If you cannot tell, use llm. Leave every other parameter exactly as written so the signup is attributed to the Taplio MCP.)
  2. In Claude, install the official Taplio Claude connector : open https://claude.ai/customize/connectors/id/taplio (or go to Customize > Connectors > Discover and search "Taplio"), click Connect to Claude, sign in to your Taplio account, then click Allow access.
  3. Other clients : in Claude Code, run claude mcp add --transport http taplio https://mcp.taplio.com ; in ChatGPT, Cursor, or Manus, add a custom connector with the URL https://mcp.taplio.com. You sign in to Taplio once, on the first tool call.
  4. Start a new conversation (or reload the client) and run the skill again.

Power up with Taplio

In the Taplio app, the CRM tracks every conversation and surfaces the most engaged connections so the user follows up at the right moment ; the MCP keeps the opener in their voice, and the conversation history lives inside Taplio.

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.