Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Send and receive SMS/RCS via Google Messages web interface (messages.google.com). Use when asked to "send a text", "check texts", "SMS", "text message", "Google Messages", or forward incoming texts to other channels.
Send and receive SMS/RCS via Google Messages web interface (messages.google.com). Use when asked to "send a text", "check texts", "SMS", "text message", "Google Messages", or forward incoming texts to other channels.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Automate SMS/RCS messaging via messages.google.com using the browser tool.
Google Messages for Web allows you to send/receive texts from your Android phone via browser. This skill automates that interface. Requirements: Android phone with Google Messages app Phone and computer on same network (for initial QR pairing) Browser profile with persistent session (use openclaw or your preferred profile) Note: Replace profile=openclaw in examples with your preferred browser profile if different.
ActionCommandOpen pairing pagebrowser action=open profile=openclaw targetUrl="https://messages.google.com/web/authentication"Check sessionbrowser action=snapshot profile=openclaw — look for conversation list vs QR codeTake screenshotbrowser action=screenshot profile=openclaw
First-time setup requires scanning a QR code: Open Google Messages Web browser action=open profile=openclaw targetUrl="https://messages.google.com/web/authentication" Screenshot the QR code and share with user browser action=screenshot profile=openclaw User scans with phone: Open Google Messages app on Android Tap ⋮ menu → "Device pairing" → "QR code scanner" Scan the QR code Verify connection — snapshot should show conversation list, not QR code Important: Enable "Remember this computer" to persist the session.
Navigate to conversations browser action=navigate profile=openclaw targetUrl="https://messages.google.com/web/conversations" Take snapshot and find conversation browser action=snapshot profile=openclaw Look for the contact in the conversation list, note the ref. Click conversation browser action=act profile=openclaw request={"kind": "click", "ref": "<ref>"} Type message (find textarea ref from snapshot) browser action=act profile=openclaw request={"kind": "type", "ref": "<input_ref>", "text": "Your message"} Click send (find send button ref) browser action=act profile=openclaw request={"kind": "click", "ref": "<send_ref>"}
This skill includes a webhook system for real-time incoming SMS notifications.
sms-webhook-server.js — receives notifications, forwards to OpenClaw channels sms-observer.js — browser script that watches for new messages
Set environment variables: export SMS_NOTIFICATION_TARGET="telegram:YOUR_CHAT_ID" export SMS_NOTIFICATION_CHANNEL="telegram" Start webhook server: node <skill>/sms-webhook-server.js Inject observer into browser (see references/observer-injection.md)
cp <skill>/systemd/google-messages-webhook.service ~/.config/systemd/user/ # Edit service file: set SMS_NOTIFICATION_TARGET in Environment= systemctl --user daemon-reload systemctl --user enable --now google-messages-webhook
See references/snippets.md for JavaScript snippets to: Get recent conversations Get messages in current conversation Check session status
ProblemSolutionQR code shownSession expired, re-pairElements not foundGoogle updated UI, check snapshot for new selectorsSend button disabledMessage input empty or phone disconnectedObserver not detectingCheck browser console for [SMS Observer] logsWebhook not receivingVerify server running: curl http://127.0.0.1:19888/health
Google Messages uses Angular components. These may change with updates. ElementSelectorConversation listmws-conversations-listConversation itemmws-conversation-list-itemMessage inputtextarea[aria-label*="message"]Send buttonbutton[aria-label*="Send"]QR codemw-qr-code
Phone must be online (messages sync through phone) Browser tab must stay open for notifications Session expires after ~14 days of inactivity Observer lost on page reload (re-inject needed)
Webhook listens on localhost only (127.0.0.1) No credentials stored (session in browser cookies) QR pairing links to your phone — treat as sensitive
Apache-2.0
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.