Beeper CLI

Search chats, list/read messages, and send messages via Beeper Desktop using the beeper-cli.

Security Scan

The skill's instructions match its stated purpose (using the beeper CLI), but the registry metadata omits a required environment variable (BEEPER_ACCESS_TOKEN) and therefore the skill's declared requirements are inconsistent with its runtime instructions.

Purpose & Capability

Name/description (search/list/read/send via Beeper Desktop) align with the SKILL.md and the single required binary 'beeper'. The listed CLI commands in SKILL.md are consistent with that purpose.

Instruction Scope

Instructions are narrowly scoped to running beeper-cli commands (searching chats, listing messages, sending messages, uploading/downloading attachments, focusing the window). They reference file paths only where expected for uploads/downloads. The SKILL.md also instructs to set an API access token and to build/install beeper-cli; nothing in the instructions asks the agent to read unrelated system files or unrelated credentials.

Install Mechanism

This is an instruction-only skill with no install spec (lowest risk). SKILL.md suggests downloading releases from GitHub or running 'go install', which is a typical, expected developer/install instruction. Note: building with 'go install' will fetch code from the public repo, so users should verify the upstream release/source before installing.

Credentials

SKILL.md requires an environment variable BEEPER_ACCESS_TOKEN (appropriate for the CLI), but the registry metadata lists no required environment variables. That mismatch is an incoherence: either the skill should declare that env var as required or the runtime instructions should not depend on it. No other unrelated credentials are requested.

Persistence & Privilege

The skill does not request always:true, does not declare config paths or other system-wide changes, and is user-invocable only. It does not ask for persistent presence or elevated platform privileges.

What to consider before installing

This skill appears to do what it says (wrap the beeper CLI) but the metadata is inconsistent: SKILL.md requires BEEPER_ACCESS_TOKEN while the registry metadata lists no env vars. Before installing or using it: 1) Confirm you have the beeper binary from a trusted source and that the beeper-cli project (https://github.com/foeken/beeper-cli) is legitimate and the release you use is verified. 2) Expect to provide BEEPER_ACCESS_TOKEN in your environment — treat it like any API token (store in a password manager/secret store, and avoid pasting into public logs). 3) If you plan to build with 'go install', review the upstream repo and prefer pinned releases rather than @latest. 4) Be cautious when uploading/downloading files via the CLI; verify paths and contents before sending. 5) Consider asking the skill publisher to correct the registry metadata so required env vars are declared; the mismatch is an indicator of sloppy packaging and should be fixed before wide deployment.

beeper

Use this skill when you need to search chats, list/read messages, or send messages via Beeper Desktop.

What this is

A CLI wrapper around the Beeper Desktop API. No MCP, no curl — just beeper commands.

Requires beeper-cli.

Prereqs

• Beeper Desktop running with API enabled: Settings > Developers
• beeper-cli installed
• Env var: BEEPER_ACCESS_TOKEN set (get from Beeper Desktop: Settings > Developers > API Access Token)

Install beeper-cli

Download from releases, or build:

go install github.com/foeken/beeper-cli@latest

Commands

Accounts

beeper accounts list
beeper accounts list -o table

Chats

# List all chats (sorted by last activity)
beeper chats list

# Search chats
beeper chats search --query "John"
beeper chats search --query "project" --type group

# Get specific chat
beeper chats get "<chatID>"

# Archive
beeper chats archive "<chatID>"

# Create
beeper chats create --account-id "telegram:123" --participant "user1" --type dm

# Reminders
beeper chats reminders create "<chatID>" --time "2025-01-26T10:00:00Z"
beeper chats reminders delete "<chatID>"

Messages

# List messages in a chat
beeper messages list "<chatID>"

# Search messages
beeper messages search --query "dinner"
beeper messages search --query "dinner" --limit 10
beeper messages search --query "meeting" --sender me
beeper messages search --query "budget" --after "2025-01-01T00:00:00Z"
beeper messages search --chat-ids "<chatID>" --media-type image

# Send a message
beeper messages send "<chatID>" "Hello!"

# Send with reply
beeper messages send "<chatID>" "Thanks!" --reply-to "<messageID>"

# Edit a message
beeper messages edit "<chatID>" "<messageID>" "Corrected text"

Assets (attachments)

# Upload a file
beeper assets upload /path/to/image.png

# Download an asset
beeper assets download "mxc://beeper.local/abc123" --output /path/to/save.jpg

# Send with attachment (upload first)
beeper assets upload /path/to/photo.jpg  # returns uploadID
beeper messages send "<chatID>" "Check this!" --upload-id "<uploadID>"

Other

# Focus Beeper window
beeper focus
beeper focus --chat-id "<chatID>"

# Global search
beeper search "important"

Output formats

beeper chats list -o json   # default
beeper chats list -o table  # human-readable

Workflow

1. Find the chat: beeper chats search --query "Name"
2. Read messages: beeper messages list "<chatID>"
3. Search content: beeper messages search --query "phrase"
4. Send: beeper messages send "<chatID>" "message"

Safety

• Store BEEPER_ACCESS_TOKEN securely (e.g., in a password manager)
• When quoting messages, include only what's needed
• Confirm message text before sending unless explicit