signalgrid-push_skill

Overview

This skill sends push notifications to iOS and Android devices using the Signalgrid API. It provides a simple CLI wrapper to post titles, bodies, and severity types, with an optional emergency bypass flag. Configuration is via environment variables for client key and channel, so you can keep credentials out of code. It’s lightweight and focused on delivering alerts from scripts, CI, or automation tools.

How this skill works

The skill constructs a notification payload from CLI options (title, body, type, critical) and posts it to the Signalgrid service using your SIGNALGRID_CLIENT_KEY and SIGNALGRID_CHANNEL. No phone numbers or device targets are required—Signalgrid handles delivery to your registered devices. Use it from shell scripts, deployment hooks, or automation pipelines to trigger real-time mobile alerts.

When to use it

• Send immediate alerts from CI/CD when a build fails or succeeds.
• Notify on infrastructure events like server restarts, errors, or high load.
• Push manual reminders or operational messages to your phone from scripts.
• Send critical bypass alerts that require immediate attention.
• Replace SMS for non-sensitive, rapid delivery notifications.

Best practices

• Keep SIGNALGRID_CLIENT_KEY and SIGNALGRID_CHANNEL in environment overrides, not in source control.
• Use clear, concise titles and bodies to make notifications actionable at a glance.
• Reserve critical=true for true emergencies to avoid alert fatigue.
• Integrate with deployment and monitoring pipelines for automated, consistent alerts.
• Rate-limit or deduplicate frequent events to prevent spamming devices.

Example use cases

• Post a deployment success notification after a CI job finishes.
• Alert on monitored service outages or degraded health checks.
• Send a one-off operational message from a maintenance script.
• Trigger a high-priority incident message with the emergency bypass flag.
• Notify team members of important calendar or workflow events via automation.