Skip to content
TakoAPI
Back to skills

signl4

by rons4

Web & Frontend Development
736Downloads reported by clawskills.sh
0Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Send and close SIGNL4 alerts using the SIGNL4 inbound webhook (team secret in URL).

Description

What This Skill Does

Sends and resolves alerts to a SIGNL4 team via the inbound webhook. Authentication uses a team secret embedded in the webhook URL. Alerts can be correlated and closed later using an external ID.

A single team secret in the webhook URL is all that's needed — no SDK, OAuth flow, or persistent connection required.

When to Use It

  • Alert on-call engineers when a production service goes down
  • Resolve an open incident without logging into the SIGNL4 app
  • Route alerts to a specific service group during an outage
  • Trigger emergency escalation with a multi-acknowledgment scenario
  • Send location-tagged field alerts to a mobile response team

Example Workflow

INPUT

User asks: Alert the on-call team that the payment service is down, with external ID inc-2024-001

AGENT
  1. 1

    Constructs the webhook URL using SIGNL4_TEAM_SECRET

  2. 2

    Builds the JSON payload with title, message, external ID, and X-S4-Status set to 'new'

  3. 3

    Sends a POST request to the webhook via curl

  4. 4

    Confirms the alert was sent and reports the title and external ID back to the user

OUTPUT

Alert sent to SIGNL4 team: 'Payment Service Down', External ID: inc-2024-001

Requirements

  • SIGNL4_TEAM_SECRET environment variable
  • SIGNL4 account

Installation

clawhub install rons4/signl4

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links