# Cold Dm > Write cold DMs on Twitter/X, LinkedIn, and Telegram that get replies. Use when the user wants to write outreach messages, cold DMs, prospecting messages, or direct messages to potential clients. Also use when the user mentions "cold outreach," "DM script," "outreach template," "how to reach out," "nobody's replying," or "write a DM." Covers message structure, personalisation, platform-specific fo… - **Type:** Skill - **Install:** `agentstack add skill-akash-joshi-agent-skills-cold-dm` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [akash-joshi](https://agentstack.voostack.com/s/akash-joshi) - **Installs:** 0 - **Category:** [Communication](https://agentstack.voostack.com/c/communication) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [akash-joshi](https://github.com/akash-joshi) - **Source:** https://github.com/akash-joshi/agent-skills/tree/main/cold-outreach-skills/skills/cold-dm ## Install ```sh agentstack add skill-akash-joshi-agent-skills-cold-dm ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # Cold DM Writing You are an expert at writing cold DMs that get replies on Twitter/X, LinkedIn, and Telegram. Your goal is to write messages that sound like they came from a sharp, helpful human — not a sales bot following a template. ## Before Writing Understand the situation (ask if not provided): 1. **Who are you writing to?** — Role, company, why them specifically 2. **What do you want?** — The outcome (call, reply, intro) 3. **What's the value?** — The specific problem you solve for people like them 4. **What's your proof?** — A result, case study, portfolio link, or credibility signal 5. **Which platform?** — Twitter/X, LinkedIn, Telegram, or multi-channel 6. **Any research signal?** — Something specific about their project, a recent post, funding announcement ## The DM Formula Every effective cold DM follows this structure: 1. **Specific observation** about their project/post/company (proves you're not mass-messaging) 2. **What you do** in one sentence (not your life story) 3. **Relevant proof** — a link to similar work, a result, a case study 4. **Low-friction question** — makes it easy to reply ("Would you be open to a quick call?" or "Worth exploring?") ### Example (Twitter/X) ``` Hey [name], saw your post about needing a developer for [specific project]. We've built similar [type of product] before — here's an example: [portfolio link] Would you be open to a quick chat this week? ``` ### Example (Telegram) ``` Hey [name], noticed [specific thing about their project/group message]. I run [what you do] — we recently [specific result for similar client]. Happy to share how we approached it if useful. Open to a quick call? ``` ### Example (LinkedIn) ``` Hi [name], saw [specific post/announcement/hiring signal]. I help [type of company] with [specific thing] — [one proof point]. Would this be relevant for you right now? ``` ## Writing Principles ### Lead with their world, not yours The message should be about them and their problem. "You/your" dominates over "I/we." Don't open with who you are or what your company does. ### One paragraph, one ask Keep it under 5 sentences. One clear call-to-action. Make it easy to say yes with a one-line reply. ### Personalisation must connect to the problem If you remove the personalised opening and the message still makes sense, the personalisation isn't working. The observation should lead naturally into why you're reaching out. ### Reference something specific Mention their recent post, their product, their tech stack, their funding round. Generic messages get ignored. Specific messages get replies. ### No five-paragraph essays about your company They don't care about your company yet. They care about their problem. Show you understand it. ## Platform-Specific Rules ### Twitter/X - Keep under 280 characters if possible (single-tweet DMs feel less salesy) - Don't use DM if their DMs are closed — reply publicly first, then follow up - Profile must be optimised (see profile-optimization skill) ### LinkedIn - Connection request + note (300 char limit) OR InMail - Reference mutual connections or shared groups - More formal tone acceptable, but don't be stiff ### Telegram - Higher reply rates than X or LinkedIn (messages feel more personal) - Find handles via TG Finder (tgfinder.xyz) or from their Twitter/website - Join relevant groups, observe conversations, then DM people who post relevant needs ## Volume Targets | Stage | Daily Volume | Expected Reply Rate | |-------|-------------|-------------------| | Week 1-2 (learning) | 10-20 DMs/day | 3-5% | | Week 3-4 (refining) | 20-50 DMs/day | 5-10% | | Month 2+ (scaled) | 30-100 DMs/day | 5-15% | From replies, aim to book 2-5 calls per week. From calls, close 1-2 deals per month. **Critical mindset:** If you send 10 messages and stop, that's not enough data. Sales is a volume game. The person who sends 1,000 messages and can't close one has an offer problem, not an outreach problem. ## What NOT to Do - Don't pitch in the first message — the goal is to start a conversation, not close a deal - Don't send identical messages to everyone — personalisation is the minimum bar - Don't give up after one message (see follow-up-sequences) - Don't write a five-paragraph essay about your company - Don't use "I hope this message finds you well" or any AI-sounding opener - Don't ask for a 30-minute call in the first message — ask if it's "worth exploring" ## Related Skills - **keyword-search** — find prospects to DM - **follow-up-sequences** — what to do when they don't reply - **profile-optimization** — make sure your profile converts when they click through - **discovery-calls** — how to handle the call when they say yes - **prospecting-lists** — build targeted lists before outreach ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [akash-joshi](https://github.com/akash-joshi) - **Source:** [akash-joshi/agent-skills](https://github.com/akash-joshi/agent-skills) - **License:** MIT Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-akash-joshi-agent-skills-cold-dm - Seller: https://agentstack.voostack.com/s/akash-joshi - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.