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.
Scanned 9/7/2026
Install to Claude Code
npx -y skills add Demerzels-lab/elsamultiskillagent --skill pocketalert --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Pocketalert?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/demerzels-lab-pocketalert)More formats (shields.io, HTML) on the badges page.
---
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 <your-api-key>
```
## 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 <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
```bash
# 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
```bash
# 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
```bash
# List devices
pocketalert devices list
# Get device details
pocketalert devices get <tid>
# Delete device
pocketalert devices delete <tid>
```
### 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 <app-tid> -d all
# List webhooks
pocketalert webhooks list
# Get webhook details
pocketalert webhooks get <tid>
# Delete webhook
pocketalert webhooks delete <tid>
```
### 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 <tid>
```
## 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 <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
```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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!