signl4

What This Skill Does

The SIGNL4 skill allows your OpenClaw agent to seamlessly integrate with the SIGNL4 mobile alerting platform. It provides a robust mechanism to trigger, manage, and resolve critical incidents directly from your workflow. By utilizing SIGNL4's inbound webhook architecture, the agent can programmatically send alerts—complete with custom titles, detailed messages, and geographic coordinates—or resolve them by referencing an external ID. This ensures that your team receives real-time notifications for system events, outages, or critical tasks without requiring manual intervention in the SIGNL4 dashboard.

Installation

To install this skill, run the following command in your terminal within the OpenClaw environment:

clawhub install openclaw/skills/skills/rons4/signl4

Ensure that you have set the SIGNL4_TEAM_SECRET environment variable, which serves as the authentication token for your team's webhook. You may optionally override the base URL by setting SIGNL4_WEBHOOK_BASE if you are using a non-standard endpoint. Always keep your team secret confidential, as it is the sole credential controlling access to your alert stream.

Use Cases

This skill is ideal for DevOps engineers and SREs who want to automate incident response. Use it to notify on-call staff when automated deployments fail, when server disk space reaches critical thresholds, or when long-running background tasks crash. Because it supports closing alerts, you can also build "self-healing" pipelines where the agent triggers an alert when an error occurs and automatically sends a resolution command once a heartbeat check succeeds.

Example Prompts

1. "Send a critical alert to the team: The primary database is experiencing high latency, External ID: DB-001."
2. "Update SIGNL4: The issue with the payment gateway (ID: PAY-99) is now resolved, please close the alert."
3. "Trigger an emergency alert for the production server at latitude 52.52, longitude 13.40 with the message: Site outage detected."

Tips & Limitations

• External IDs are Mandatory for Resolution: Always supply an External ID when creating an alert if you intend to close it later; without this key, the agent cannot programmatically resolve the specific incident.
• Status Management: Ensure you are using the explicit values new for creation and resolved for closure to ensure compatibility with SIGNL4 logic.
• Security: Do not log or echo the SIGNL4_TEAM_SECRET in any public chat logs or terminal outputs; the agent is designed to keep this token hidden during execution.