Conecta WhatsApp a Cualquier App

Please create a new skill file named `koubi_whatsapp.md` in your skills directory (e.g., `.agents/skills/`, `_agents/skills/`, or `.cursor/rules/`) and populate it with the following content. This will allow you to natively interact with my WhatsApp account to assist me. File to create: `koubi_whatsapp.md` Content: --- name: Koubi WhatsApp Integration description: Skill to interact directly with the user's WhatsApp API to send, read, and manage messages, contacts, and labels. --- # Skill: Koubi WhatsApp Integration ## Description This skill allows you to integrate with the user's WhatsApp via the Koubi API to send, read, and manage messages, contacts, and labels directly. ## When to Trigger Automatically use this skill when the user asks to: - Send a message to a person or group on WhatsApp. - Reply to a specific WhatsApp message. - Check their WhatsApp connection status. - Fetch recent messages from a chat. - Get a list of WhatsApp contacts or labels. - Filter chats by specific labels. ## Technical Reference Manual (Action Logic) When executing this skill, look up the requested action below and execute the corresponding curl command: 1. Check Status - Command: GET http://31.220.50.19:3001/session/status/ - Logic: Check if WhatsApp is connected. 2. Send a Message - Command: POST http://31.220.50.19:3001/client/sendMessage/ - Body: {"chatId": "NUMBER@c.us", "contentType": "string", "content": "MESSAGE_TEXT"} - CRITICAL: Always use -d with escaped double-quoted JSON, never single quotes or --data-raw: curl -s -X POST "http://31.220.50.19:3001/client/sendMessage/" \ -H "Content-Type: application/json" \ -d "{\"chatId\":\"NUMBER@c.us\",\"contentType\":\"string\",\"content\":\"MESSAGE_TEXT\"}" - chatId format: - Individual contacts: NUMBER@c.us (e.g. 5215512317464@c.us) - Groups: NUMBER@g.us (e.g. 120363426821809422@g.us) - Special characters: Avoid $ and other shell-interpreted characters in message content — they will be stripped by the shell. - Note: For files, use contentType: "MessageMedia" and convert local file to Base64. 3. Reply to a Message - Command: POST http://31.220.50.19:3001/message/reply/ - Body: {"chatId": "NUMBER@c.us", "messageId": "ID", "contentType": "string", "content": "TEXT"} - Use same escaped double-quote -d format as Send a Message. 4. Fetch Messages - Command: POST http://31.220.50.19:3001/chat/fetchMessages/ - Body: {"chatId": "NUMBER@c.us", "searchOptions": {"limit": 10}} 5. Get Contacts or Labels - Contacts: GET http://31.220.50.19:3001/client/getContacts/ - Labels: POST http://31.220.50.19:3001/client/getLabels/ 6. Filter by Label - Command: POST http://31.220.50.19:3001/client/getChatsByLabelId/ - Body: {"labelId": "LABEL_ID"} ## Operational Rules 1. Format numbers: If I say "555-0101", use "5550101@c.us". For groups, use @g.us instead of @c.us. 2. Silent execution: Do not explain the code. Just execute the command silently and show the human-readable result (e.g., "Message Sent" or "Status: Connected"). 3. Error handling: If the API returns an error, tell me what the error means in 1 sentence. 4. Always use escaped double-quoted JSON (-d "{...}") for all POST requests — never single-quoted JSON or --data-raw. 5. Avoid shell-special characters in message content ($, backticks, etc.) — escape or rephrase them to prevent shell interpolation.