Beeper API CLI

Before installing or enabling this skill, note these points: - The skill actually requires a BEEPER_TOKEN (a local Bearer token). The registry metadata incorrectly lists no required env vars. Only set this token if you trust the environment and understand it grants access to all messages available to your Beeper Desktop. - The provided beeper.sh contains a hardcoded path (/Users/ashrafali/...) to the beeper CLI binary and will fail unless you edit it to point to the correct binary on your machine. Review and update BEEPER_CLI in the script before running. - The script will try to auto-start Beeper Desktop using macOS 'open -a' if the app isn't running. That side effect can be surprising and will not work on Linux. If you don't want the skill to start apps, remove or modify that section. - The SKILL.md enforces a 'never send without explicit approval' policy in text, but the script itself does not enforce user confirmation. If you will allow agent automation, ensure the agent is configured so it cannot send messages without explicit, verifiable user approval. - Verify Beeper Desktop API settings: ensure the API token is restricted to localhost (or that allowed IPs are configured appropriately) before using the skill from another machine. - If you want to proceed: (1) inspect and edit beeper.sh to point to your beeper binary and remove/adjust the auto-start behavior, (2) export BEEPER_TOKEN and set BEEPER_API_URL to the local API, and (3) test read-only commands first (list chats, read messages) before enabling any send workflows. This skill appears to implement its stated purpose, but the metadata/script mismatches and side-effects warrant manual review and configuration before use.