# pocketalert > Send push notifications and manage Pocket Alert resources via the pocketalert CLI. Use when the user wants to send push notifications, manage applications, devices, webhooks, or API keys through Pocket Alert. Handles message sending, application management, device management, webhook creation, and API key operations. - Author: Adam Delisi - Repository: massiveadam/skills - Version: 20260131183437 - Stars: 0 - Forks: 0 - Last Updated: 2026-02-06 - Source: https://github.com/massiveadam/skills - Web: https://mule.run/skillshub/@@massiveadam/skills~pocketalert:20260131183437 --- --- name: pocketalert description: Send push notifications and manage Pocket Alert resources via the pocketalert CLI. Use when the user wants to send push notifications, manage applications, devices, webhooks, or API keys through Pocket Alert. Handles message sending, application management, device management, webhook creation, and API key operations. --- # Pocket Alert This skill enables interaction with the [Pocket Alert](https://pocketalert.app) service through its CLI tool. ## Prerequisites The `pocketalert` CLI must be installed and authenticated: ```bash # 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 ``` ## Quick Reference ### Send Push Notifications ```bash # 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 # To specific device pocketalert messages send -t "Alert" -m "Check server" -d # To all devices pocketalert messages send -t "Alert" -m "System update" -d all ``` ### List Resources ```bash # List last messages pocketalert messages list pocketalert messages list --limit 50 pocketalert messages list --device # List applications pocketalert apps list # List devices pocketalert devices list # List webhooks pocketalert webhooks list # List API keys pocketalert apikeys list ``` ### Manage Applications ```bash # Create application pocketalert apps create --name "My App" pocketalert apps create -n "Production" -c "#FF5733" # Get application details pocketalert apps get # Delete application pocketalert apps delete ``` ### Manage Devices ```bash # List devices pocketalert devices list # Get device details pocketalert devices get # Delete device pocketalert devices delete ``` ### Manage Webhooks ```bash # 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 -d all # List webhooks pocketalert webhooks list # Get webhook details pocketalert webhooks get # Delete webhook pocketalert webhooks delete ``` ### Manage API Keys ```bash # Create API key pocketalert apikeys create --name "CI Key" # List API keys pocketalert apikeys list # Delete API key pocketalert apikeys delete ``` ## Message Template Variables When creating webhooks, you can use template variables from the incoming payload: ```bash pocketalert webhooks create \ --name "GitHub Push" \ --message "Push to %repository.name%: %head_commit.message%" ``` ## Configuration View or modify configuration: ```bash # View config pocketalert config # Set API key pocketalert config set 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 ```bash # 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` - Success - `1` - Authentication or API error - `2` - Invalid arguments Always check command output for error details.