ClawHub

Claw Me Maybe - Beeper Desktop API & Multi-Platform Messaging

v1.2.1

Beeper integration for Clawdbot. Send messages and search chats across WhatsApp, Telegram, Signal, Discord, Slack, Instagram, iMessage, LinkedIn, Facebook Messenger, Google Messages via Beeper Desktop API. Reactions, reminders, attachments, mark as read. Unified multi-platform messaging automation—just ask.

⭐ 2· 3.4k·12 current·13 all-time
by@nickhamze
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (multi-platform messaging via Beeper Desktop API) matches the runtime instructions: all examples call the local Beeper API and use curl. Required binary (curl) is appropriate and no unrelated services or credentials are requested.
✓
Instruction Scope
SKILL.md stays within scope: it instructs enabling the Beeper Desktop API, optionally creating an access token, and using curl against the local API (default http://localhost:23373). It does not instruct reading unrelated system files or contacting external endpoints other than the Beeper app.
✓
Install Mechanism
No install spec and no code files — instruction-only. This minimizes risk because nothing is downloaded or written by the skill itself.
ℹ
Credentials
The skill uses BEEPER_API_URL and optionally BEEPER_ACCESS_TOKEN. The metadata includes a default for BEEPER_API_URL but the skill does not declare any required env vars in registry metadata — acceptable because the access token is optional, but you should be aware that if you store a BEEPER_ACCESS_TOKEN (recommended in examples), the skill — and any agent invocation that has access to that config — can access all Beeper-connected chats.
✓
Persistence & Privilege
always:false and no install; the only persistent change suggested is optionally adding a token to ~/.clawdbot/clawdbot.json to ease automated calls. That is a normal, scoped request for a messaging integration.
Assessment
This skill is coherent: it talks to your local Beeper Desktop API using curl and (optionally) a Beeper access token. Before enabling: 1) only enable the Beeper Desktop API in the Beeper app if you trust the machine and Beeper installation; 2) understand that storing BEEPER_ACCESS_TOKEN in ~/.clawdbot/clawdbot.json grants the skill (and any autonomous agent actions) access to read/send across all connected chat services — treat it like a sensitive token; 3) if you don't want automated sending, don't store the token or restrict when the skill is enabled; and 4) note iMessage support is macOS-only despite there being no OS restriction in the registry metadata. If you want more assurance, request the full SKILL.md (complete endpoints/examples) and any audit/logging the agent will retain for actions it takes on your behalf.

Like a lobster shell, security has layers — review code before you run it.

beepervk973x6nsny8y94cqjtefkzgqgs7zvny3chatvk972stce0swyn1rw7v4rsa398x7zvkmachat-automationvk973x6nsny8y94cqjtefkzgqgs7zvny3cross-platformvk973x6nsny8y94cqjtefkzgqgs7zvny3desktop-apivk973x6nsny8y94cqjtefkzgqgs7zvny3discordvk973x6nsny8y94cqjtefkzgqgs7zvny3facebook-messengervk973x6nsny8y94cqjtefkzgqgs7zvny3google-messagesvk973x6nsny8y94cqjtefkzgqgs7zvny3imessagevk973x6nsny8y94cqjtefkzgqgs7zvny3instagramvk973x6nsny8y94cqjtefkzgqgs7zvny3latestvk973x6nsny8y94cqjtefkzgqgs7zvny3linkedinvk973x6nsny8y94cqjtefkzgqgs7zvny3messagingvk973x6nsny8y94cqjtefkzgqgs7zvny3multi-platformvk973x6nsny8y94cqjtefkzgqgs7zvny3signalvk973x6nsny8y94cqjtefkzgqgs7zvny3slackvk973x6nsny8y94cqjtefkzgqgs7zvny3telegramvk973x6nsny8y94cqjtefkzgqgs7zvny3unified-messagingvk973x6nsny8y94cqjtefkzgqgs7zvny3whatsappvk973x6nsny8y94cqjtefkzgqgs7zvny3

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

📟 Clawdis
Binscurl

Comments