first-message
Skill1 starsChanged 24 days agoMITView on GitHub
Writes a short, honest first message to a stranger who might become a customer, as a cold email or a cold DM on Reddit, LinkedIn, X or Instagram. Shows you know them, offers something of value, and asks one genuinely curious question instead of pitching. Use when a founder asks for a cold email, cold DM, first message, message template, or \"how do I message this person without being spammy\".
3 other projects use a version of this.
Adopted by
Most recently taken up by
- saloprj/dialogbrain-claude-plugintheir own version, first seen Nov 8, 2026
- nadavnaveh/skillstheir own version, first seen Nov 8, 2026
- Castan-AI/founder-commandstheir own version, first seen Nov 8, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- nadavnaveh/skills★ 2same name
- Castan-AI/founder-commands★ 1same name
- saloprj/dialogbrain-claude-plugin★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- alert-wordsSkill
- ask-for-an-introductionSkill
- customer-interviewSkill
- daily-fiveSkill
- expert-to-skillSkill
- find-one-personSkill
- one-line-pitchSkill
- readiness-checkSkill
- reddit-reply-not-pitchSkill
- research-one-personSkill
- show-hn-launchSkill
- update-that-earns-a-dmSkill
- where-my-customers-areSkill
- who-buys-from-meSkill
- why-they-said-yesSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 26
Leave the pitch out of the first message: If they reply, there's a conversation.
- Distinctive: line 60
No em dashes, no exclamation marks.
- Distinctive: line 62
Don't automate sending from your own accounts.
≈ “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.
Files
First message
Show you know them. Give something. Ask one soft question.
Around nine in ten cold emails never get a reply, and most deserve it: a template with a first name, "I saw your post", a pitch, and a request for thirty minutes. Founders overthink the first message, trying to be clever and fit everything in. The ones that work are simple. They prove you understand the person's world, and they end on a question worth answering.
What you need
- What you sell, in one plain line.
- Who you're writing to and what you know about them. The
research-one-personskill helps. - The channel: email, Reddit, LinkedIn, X or Instagram.
Steps
- Start with them. One line that shows you understand their situation. Real understanding, not their job title read back to them.
- Offer something. An idea, a useful fact, a perspective on their problem. Something worth having even if they never reply.
- Ask one curious question. Related to their world, not a disguised sales pitch. Something they'd enjoy answering.
- Leave the pitch out of the first message. If they reply, there's a conversation. That's when what you do comes up.
- Cut it in half. Short and simple beats clever and complete.
Real openers that worked
These are first messages Toby Stapleton sent while building Plastic Bank. Neither mentions a product.
"Hey [name], if plastic were as valuable as diamonds, would we have such a significant problem with ocean plastic pollution? What would you say plastic is worth?"
"Hey [name], the average person throws away 28kg of plastic every year. What do you do to reduce that number?"
Each one hands over a thought and a question worth answering, to people who already cared about the problem.
Openers that get you ignored
- "I saw your post about..." and "I noticed you commented on..." Most people don't remember their own posts, so it reads as automated.
- "I see you're the Director of..." Their title is the least interesting thing about them.
- The wrong name or company. One mistake and the message is dead.
- Any compliment you could send to a hundred people.
- "Hope this finds you well", "just following up", "quick question".
Output
Message (<channel>):
<text>
Why it should land: <what it shows you know, and why they'd answer the question>Rules
- One message, one person. Never send the same message to two people.
- No em dashes, no exclamation marks.
- A follow-up needs a new reason to write. If you don't have one, don't follow up.
- Don't automate sending from your own accounts. A few real messages beat a thousand templated ones, and you learn far more from them.
With MyPip (coming)
MyPip writes to the people it finds, one at a time, and introduces you when they say yes. When the MyPip MCP is live, this skill will be able to help you write to the people you'd rather contact yourself.
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
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.

