Signalgrid Activity

Send Live-Activities & Ongoing-Notifications to your iOS / Android phones using Signalgrid.

Security Scan

The skill's requirements and behavior match its stated purpose (sending live/ongoing notifications via Signalgrid); the code and instructions are coherent and proportionate, but there are a couple of non-malicious coding bugs that can break functionality and should be fixed before use.

Purpose & Capability

Name/description, required binaries (node), and required env vars (SIGNALGRID_CLIENT_KEY, SIGNALGRID_CHANNEL) align with a notification-sending skill. The package and API host (api.signalgrid.co) are consistent with the described service.

Instruction Scope

SKILL.md instructs running the included node script with parameters (including --token). The bundled script largely implements that behavior, but it contains bugs that break intended behavior: (1) the script reads args.update_token rather than args.token, so a provided --token won't be transmitted; (2) console.log references an undefined variable (isCritical), which will throw and cause the process to exit with error after the request completes. These are functional/incoherence issues in the runtime instructions vs. implementation.

Install Mechanism

No install spec (instruction-only install via clawdhub). The skill contains a small Node script and package.json; there are no external downloads or obscure URLs. No extract or remote code fetch during install.

Credentials

Only two service-specific env vars are required (client key and channel). These are appropriate and proportional for a notification API integration. The script only reads those two env vars.

Persistence & Privilege

always:false and no install-time changes are requested. The skill does not request persistent system privileges or modify other skills/configs.

Assessment

This skill appears to be what it claims: a small Node script that POSTs multipart form data to api.signalgrid.co using SIGNALGRID_CLIENT_KEY and SIGNALGRID_CHANNEL. Before installing or using it, consider the following: - Fix the two clear bugs in signalgrid-activity.js before relying on it in production: change the token variable to read args.token (update_token = args.token || "") so update/end flows work as documented, and define isCritical (e.g., const isCritical = finalType === 'crit') or remove it to avoid a ReferenceError that causes the script to exit non-zero even after a successful request. - Test start/update/end flows locally after setting SIGNALGRID_CLIENT_KEY and SIGNALGRID_CHANNEL to confirm token propagation and correct exit behavior. - Keep SIGNALGRID_CLIENT_KEY secret — treat it like any API key. Confirm the key's scope/permissions with Signalgrid and rotate/revoke if compromised. - The skill posts to api.signalgrid.co; if you require stricter network controls, vet that domain and the Signalgrid service first. - Because the skill runs arbitrary Node code, only install from sources you trust; the current package is small and contains no obfuscated or external downloads, but always review updates for changes. If you want, I can produce a patched version of signalgrid-activity.js with the token and isCritical fixes and optional improvements (better exit codes, response handling, and safer logging).

Signalgrid Live Activities

Send Live Activities & Ongoing Notifications to your phone through the Signalgrid API.

When to use

Use this skill whenever the user asks to:
 
  o  start an ongoing notification
  o  update progress of an ongoing notification
  o  show a live activity / live progress
  o  keep a notification updated while something runs (deploy, backup, import, CI job, etc.)
  o  end/finish an ongoing notification

Start Live Activity:

node {baseDir}/skills/signalgrid-activity/signalgrid-activity.js \
  --type start \
  --title "OpenClaw" \
  --body "Starting…" \
  --severity info \
  --steps 1 \
  --progress 10 \
  --progress_legend "true" \
  --start_text "Activity Start" \
  --end_text "Activity End" \

Update Live Activity:

node {baseDir}/skills/signalgrid-activity/signalgrid-activity.js \
  --type update \
  --token "MX2L2K" \
  --title "OpenClaw" \
  --body "Step 3/6" \
  --severity warning \
  --steps 1 \
  --progress 50 \
  --progress_legend "true" \
  --start_text "Activity Start" \
  --end_text "Activity End" \

End Live Activity:

node {baseDir}/skills/signalgrid-activity/signalgrid-activity.js \
  --type end \
  --token "MX2L2K" \
  --title "OpenClaw" \
  --body "Done" \
  --severity success \
  --steps 1 \
  --progress 100 \
  --progress_legend "true" \
  --start_text "Activity Start" \
  --end_text "Activity End" \
  --dismissal_delay 60

Parameters

Name	Type	Description
title	string	Activity title. Defaults to No Title.
body	string	Activity body text. Defaults to No Body.
type	enum	Activity phase. Common values: start, update, end. Defaults to start.
severity	string	Mapped to crit, warn, success, info (see Notes).
start_text	string	Optional. Label for the start state. Defaults to Activity Start.
end_text	string	Optional. Label for the end state. Defaults to Activity End.
steps	number	Optional. For the progressbar-prensentation if set to 5, the progressbar has 5 steps. Defaults to 5.
progress	number	Current progress value. Defaults to 10.
progress_legend	boolean	Optional. Show progress legend. Defaults to true (passed as a string).
token	string	Optional. only used with update & end messages. is for matching the activity.
dismissal_delay	string	Optional. The delay a activity is shown after end message is sent. Only on end messages

Usage

In update & end messages the following parameters need to be taken from start message and retransmitted if not defined otherwise:

  o  title
  o  body
  o  severity
  o  steps
  o  progress_legend
  o  start_text
  o  end_text
 
Otherwise the activity will change its appearance. It is allowed for flexibility, but not needed most of the time.

Notes

• Requires a Signalgrid account: https://web.signalgrid.co/  
   
• Install the skill:

clawdhub --workdir ~/.openclaw install signalgrid-activity

• And ensure your OpenClaw Tool Profile is set to full ( Config -> Tools -> Tool Profile )
   
• Configure environment variables ( Config -> Environment -> Environment Variables Overrides + Add Entry):

SIGNALGRID_CLIENT_KEY=your_client_key_here
SIGNALGRID_CHANNEL=your_channel_name_here

 

• Signalgrid notifications do not require a phone number or message target.