Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Send and read SMS text messages via an Android phone using pidge. Use when asked to send a text, check texts, read SMS inbox, or reply to a text message.
Send and read SMS text messages via an Android phone using pidge. Use when asked to send a text, check texts, read SMS inbox, or reply to a text message.
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.
Send and read SMS messages via pidge, a CLI for Android SMS Gateway. The gateway runs on an Android device and pidge connects to it automatically. pidge reads its config from ~/.config/pidge/config.toml — no env vars needed.
pidge send "+1XXXXXXXXXX" "Your message here" Phone numbers must be E.164 format (e.g. +15551234567) Response includes id and state (Pending → Processed → Sent → Delivered)
pidge status <message-id>
pidge inbox pidge inbox --unread pidge inbox --json
pidge ack <id> # mark as processed pidge unack <id> # mark as unprocessed
pidge health
Messages are sent to real phone numbers. Always confirm the recipient and content before sending. NEVER send SMS to unknown numbers without explicit owner approval. NEVER send bulk or repeated messages. NEVER send sensitive information (passwords, API keys, tokens, etc.) via SMS. NEVER include the full content of private SMS messages in group chat responses. When showing credentials, prefer a summary — only reveal full message content if directly requested in a private context.
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.