Pocketalert
@Akellacom
npx machina-cli add skill @Akellacom/pocketalert --openclawPocket Alert
This skill enables interaction with the Pocket Alert service through its CLI tool.
Prerequisites
The pocketalert CLI must be installed and authenticated:
# Install (if not already installed)
# Download from https://info.pocketalert.app/cli.html and extract to /usr/local/bin/
# Authenticate with your API key
pocketalert auth <your-api-key>
Quick Reference
Send Push Notifications
# Basic notification
pocketalert send -t "Title" -m "Message"
# Full form
pocketalert messages send --title "Alert" --message "Server is down!"
# To specific application
pocketalert messages send -t "Deploy" -m "Build completed" -a <app-tid>
# To specific device
pocketalert messages send -t "Alert" -m "Check server" -d <device-tid>
# To all devices
pocketalert messages send -t "Alert" -m "System update" -d all
List Resources
# List last messages
pocketalert messages list
pocketalert messages list --limit 50
pocketalert messages list --device <device-tid>
# List applications
pocketalert apps list
# List devices
pocketalert devices list
# List webhooks
pocketalert webhooks list
# List API keys
pocketalert apikeys list
Manage Applications
# Create application
pocketalert apps create --name "My App"
pocketalert apps create -n "Production" -c "#FF5733"
# Get application details
pocketalert apps get <tid>
# Delete application
pocketalert apps delete <tid>
Manage Devices
# List devices
pocketalert devices list
# Get device details
pocketalert devices get <tid>
# Delete device
pocketalert devices delete <tid>
Manage Webhooks
# Create webhook
pocketalert webhooks create --name "GitHub Webhook" --message "*"
pocketalert webhooks create -n "Deploy Hook" -m "Deployed %repository.name% by %sender.login%"
pocketalert webhooks create -n "CI/CD" -m "*" -a <app-tid> -d all
# List webhooks
pocketalert webhooks list
# Get webhook details
pocketalert webhooks get <tid>
# Delete webhook
pocketalert webhooks delete <tid>
Message Template Variables
When creating webhooks, you can use template variables from the incoming payload:
pocketalert webhooks create \
--name "GitHub Push" \
--message "Push to %repository.name%: %head_commit.message%"
Configuration
View or modify configuration:
# View config
pocketalert config
# Set API key
pocketalert config set api_key <new-api-key>
# Set custom base URL (for self-hosted)
pocketalert config set base_url https://your-api.example.com
Configuration is stored at ~/.pocketalert/config.json.
CI/CD Integration Examples
# GitHub Actions / GitLab CI
pocketalert send -t "Build Complete" -m "Version $VERSION deployed"
# Server monitoring with cron
*/5 * * * * /usr/local/bin/pocketalert send -t "Server Health" -m "$(uptime)"
# Service check script
if ! systemctl is-active --quiet nginx; then
pocketalert send -t "NGINX Down" -m "NGINX is not running on $(hostname)"
fi
Error Handling
The CLI returns appropriate exit codes:
0- Success1- Authentication or API error2- Invalid arguments
Always check command output for error details.
Overview
Pocket Alert enables OpenClaw agents and workflows to push alerts to iOS and Android devices. It integrates with the pocketalert CLI to deliver updates from automated tasks, workflows, and background processes.
How This Skill Works
Install and authenticate the pocketalert CLI, then OpenClaw issues pocketalert commands to send notifications. Use commands under messages, apps, devices, and webhooks to target specific devices, a particular app, or all devices. Configuration settings like API keys and base URLs are stored locally.
When to Use It
- Ops teams need real-time server alerts on mobile
- Automated workflows require user-visible updates
- CI/CD pipelines push build or deployment notifications
- On-call rotations need device-targeted mobile alerts
- Scheduled health checks or monitoring scripts notify the team
Quick Start
- Step 1: Install the pocketalert CLI and run pocketalert auth <your-api-key>.
- Step 2: Send a test notification: pocketalert send -t "Hello" -m "Test message".
- Step 3: Target an app or device: pocketalert messages send -t "Alert" -m "Test" -a <app-tid> or -d <device-tid>.
Best Practices
- Authenticate the CLI before sending any alerts
- Use clear, concise titles and messages for quick reading
- Target the right audience: specific device, app, or all
- Organize alerts by apps and devices to reduce noise
- Test notifications with non-critical messages before production
Example Use Cases
- Basic notification: pocketalert send -t "Status" -m "All systems nominal"
- Full form to an app: pocketalert messages send --title "Deploy" --message "Build completed" -a <app-tid>
- Device-specific alert: pocketalert messages send -t "Warning" -m "Disk space low" -d <device-tid>
- Broadcast to all: pocketalert messages send -t "Update" -m "System update" -d all
- List resources: pocketalert devices list; pocketalert apps list