first-message
Skill0 starsChanged 57 days agoMITView on GitHub
Write to someone the workspace has never talked to — a new phone number on WhatsApp or SMS, a Telegram @username, an email address, a LinkedIn member, a Discord or X user. Use whenever messages.send answers "not found", or before writing to a number, handle or address that has no conversation yet.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- nadavnaveh/skillstheir own version, first seen Nov 8, 2026
- Castan-AI/founder-commandstheir own version, first seen Nov 8, 2026
- mypip-io/skillstheir own version, first seen Nov 1, 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
- mypip-io/skills★ 1same 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 repository7 other files it gives its agents.
- connect-channelSkill
- create-agentSkill
- lead-reportSkill
- react-to-eventsSkill
- setup-livechat-widgetSkill
- tasks-boardSkill
- voice-agentSkill
The file
Files
Write a first message
recipient_name only finds people who are already in contacts. A new person
is named by where they are, in thread_id (or one dedicated field), and
the workspace account that sends is named in from_account_id.
Steps
- Check there is no conversation already.
search.threads/contacts.findwith the number, handle or name. If one exists, reply there with its numericthread_idand stop. - Pick the sending account.
channels.list(in_workspace=…)lists the workspace's accounts; take the id of the one on the right channel. With several on a channel, ask which one when the request does not say. - Send with the form for that channel (international numbers,
+and digits):
| To | Call |
| a phone number on WhatsApp (personal account, QR) | messages.send(thread_id="whatsapp:+<number>", from_account_id=<wa account>, text=…) |
| a phone number on WhatsApp Business API | thread_id="whatsapp_business:+<number>"; the first message must be a template |
| a phone number by SMS | thread_id="sms:+<number>", from a phone number with SMS on |
| a Telegram @username | recipient_username="@handle" (no thread_id) |
| an email address | messages.send_email(recipient_email=…, subject=…, text=…) |
| a LinkedIn member | thread_id="linkedin:member:<member id>" |
| a Discord user | thread_id="discord:<numeric user id>" |
| an X user | thread_id="x:@<handle>" |
| a Skool member | thread_id="skool:user:<user id>" |
| a Teams user in the same company | thread_id="teams:<email>" |
- Read the answer. It names the new conversation's numeric
thread_id; use that for every following message, never thewhatsapp:+…form again.
Mistakes that fail
- A phone number in
recipient_name: it is looked up as a contact's name and answers "not found". Put it inthread_idas above. channel="whatsapp"next torecipient_name: there is no such parameter, it is ignored.to/bodyinstead ofrecipient_email/text: not parameters ofmessages.send; email goes throughmessages.send_email.- A WhatsApp group id (
…@g.us) cannot be opened this way; groups are created withgroup.create.
Before sending
A first message to a stranger is outbound in the owner's name. Send it only when the owner asked for it, from the account they named, and follow any workspace rule about which accounts may write first.
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.