pidgesms

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.

Security Scan

The skill's requirements and runtime instructions match its stated purpose (using the pidge CLI to send/read SMS via an Android SMS Gateway); nothing requests unrelated credentials or surprising install sources, though you should trust the upstream pidge project before installing.

Purpose & Capability

Name/description (SMS via pidge) align with the declared runtime requirements: the skill only requires the pidge binary and the pidge config (~/.config/pidge/config.toml). There are no unrelated environment variables, binaries, or config paths requested.

Instruction Scope

SKILL.md instructs only on running the pidge CLI (send, inbox, status, ack/unack, health) and references pidge's config file. It does not instruct reading other files, scanning the system, or posting SMS content to external endpoints unrelated to the Android SMS Gateway.

Install Mechanism

The registry lists no formal install spec, but the SKILL.md metadata suggests `go install github.com/typhonius/pidge@latest`. That will fetch and build code from the public GitHub repo (moderate trust requirement). This is not a private/paste URL or arbitrary binary download, but it does pull external code to disk — review the upstream project before installing.

Credentials

No environment variables or credentials are requested. The only config path referenced is pidge's config (~/.config/pidge/config.toml), which is appropriate for the stated purpose.

Persistence & Privilege

The skill does not request permanent/always-on inclusion (always:false) and does not modify other skills. It is callable by the model (default behavior) — because the skill can send real SMS, consider the implications of autonomous invocation (the platform default) if you need to prevent the agent from sending messages without explicit approval.

Assessment

This skill appears coherent and implements exactly what it claims: a thin wrapper around the pidge CLI to interact with an Android SMS Gateway. Before installing, verify you trust the upstream pidge project (SKILL.md suggests installing via `go install github.com/typhonius/pidge@latest` which fetches code from GitHub). Secure your phone and gateway (run the Android SMS Gateway only on trusted networks), inspect ~/.config/pidge/config.toml for any credentials or webhook endpoints, and test with a controlled phone number. If you want to prevent accidental or automated sends, consider disabling autonomous skill invocation for this skill (or require explicit user approval) so the agent cannot send SMS without your confirmation.

pidgesms — SMS via pidge

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.

Send SMS

pidge send "+1XXXXXXXXXX" "Your message here"

• Phone numbers must be E.164 format (e.g. [phone])
• Response includes id and state (Pending → Processed → Sent → Delivered)

Check delivery status

pidge status <message-id>

Read SMS (inbox)

pidge inbox
pidge inbox --unread
pidge inbox --json

Mark message as processed / unprocessed

pidge ack <id>      # mark as processed
pidge unack <id>    # mark as unprocessed

Health check

pidge health

Safety rules

• 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.