agentleFS
Sign inStart free
hsigstadhsigstad/research-kit/skills/whatsapp/SKILL.md

whatsapp

Skill0 starsChanged 4 months agoMITView on GitHub

Send or read WhatsApp messages. Use when the user wants to message a contact or group, e.g. '/whatsapp Andrei hey, check the new data'.

14 other projects use 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. 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check if the bridge is running:

    line 23
  2. Distinctive:

    If no response, start it:

    line 29
  3. Distinctive:

    If the bridge fails with a QR code auth error, tell the user to run:

    line 36
  4. Very specific:

    Use mcp__whatsapp__search_contacts to find the recipient by name

    line 57
  5. Very specific:

    Use mcp__whatsapp__send_message with the phone number or JID

    line 59
  6. Very specific:

    Use mcp__whatsapp__list_messages to fetch recent messages

    line 63
  7. Very specific:

    Use mcp__whatsapp__get_direct_chat_by_contact for a specific contact's chat

    line 64
  8. Distinctive:

    If a contact is not found, try partial name matches or ask the user for the phone number.

    line 82

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “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

WhatsApp

Send and read WhatsApp messages via the whatsapp-mcp bridge.

Implementation: use the maintained fork verygoodplugins/whatsapp-mcp, not upstream lharries/whatsapp-mcp. Same architecture (Go whatsmeow bridge + Python MCP server, QR linked-device auth, local whatsapp.db), but upstream went quiet after ~April 2025 (~91 open issues / ~131 open PRs); the fork is actively maintained (CI/CD, call capture, media, LID resolution). This is still the only mature way to reach a personal WhatsApp number — every 2025–26 alternative (Meta Business Agent, Composio/Wati/360dialog MCP gateways) is Business-Cloud-API-only and can't touch personal threads. Tradeoffs are real and unchanged: unofficial → violates ToS + genuine account-ban risk, ~20-day QR re-auth, and protocol breakage that halts messaging until a maintainer fix is pulled + redeployed. See memory [[reference_whatsapp_connection_options]]. Not yet installed on Educloud (needs Go in the sandbox image).

Before any WhatsApp tool call

Check if the bridge is running:

curl -sf http://localhost:8080/api/send 2>/dev/null

If no response, start it:

nohup ~/whatsapp-mcp/whatsapp-bridge/bridge > /tmp/whatsapp-bridge.log 2>&1 &
sleep 8  # wait for connection + history sync

If the bridge fails with a QR code auth error, tell the user to run:

! cd ~/whatsapp-mcp/whatsapp-bridge && ./bridge

and scan the QR code with their phone (WhatsApp → Linked Devices → Link a Device). Auth lasts ~20 days.

Parsing the request

The user may say things like:

  • /whatsapp Andrei hey, the MG data is ready
  • /whatsapp "Laborjust Sigstad Lambais" meeting tomorrow at 3pm
  • send a whatsapp to Frida saying hi
  • check whatsapp messages from Andrei

Extract:

  1. Who — contact name or group name
  2. Message — the text to send (if sending)
  3. Action — send message, read messages, or search contacts

Sending a message

  1. Use mcp__whatsapp__search_contacts to find the recipient by name
  2. For groups, use mcp__whatsapp__list_chats to find the group JID
  3. Use mcp__whatsapp__send_message with the phone number or JID

Reading messages

  • Use mcp__whatsapp__list_messages to fetch recent messages
  • Use mcp__whatsapp__get_direct_chat_by_contact for a specific contact's chat

Project WhatsApp groups

Some projects have associated WhatsApp groups:

  • serasa (projects/serasa): "SERASA Courts Project"
  • connect (projects/connect): "LaborJust henrik lambais"
  • procure (projects/procure): "Corruption Red Flags"
  • audit (projects/audit): "Legal Effects of Audits"
  • electoral-justice (projects/electoral-justice): "Electoral justice"
  • segredo (projects/segredo): Andrei Leite (direct chat)

Before sending

Show the user the recipient and message, and ask for confirmation before sending — unless the user's request is unambiguous (explicit recipient + explicit message text).

Gotchas

  • If a contact is not found, try partial name matches or ask the user for the phone number.
  • Group JIDs end in @g.us, individual contacts end in @s.whatsapp.net.
  • Phone numbers need country code without + or spaces (e.g., "4748142870" for Norway).
  • The bridge must have seen a chat to list it — if a group doesn't show up, ask the user to send a message there from their phone first.

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