LogoClawIndex
CasesSkillsAbout
LogoClawIndex

platform-signal - Connect Signal to a remote Hermes agent

Connects a remote Hermes agent to Signal through a linked signal-cli HTTP daemon over SSH with an enforced E.164 allowlist.

Tags

Updated: 2026-10-04

Capabilities

Typical Inputs

Typical Outputs

What this skill does

  • Verify Hermes and Java prerequisites
  • Validate E.164 allowlists
  • Link a Signal device
  • Configure the signal-cli daemon
  • Configure Hermes Signal settings
  • Enable supervised daemon startup
  • Reload the Hermes gateway
  • Run health and smoke checks

Inputs

  • VPS IP or hostname
  • VPS SSH user
  • Signal bot account number
  • Signal DM allowlist
  • Signal group allowlist
  • Signal home channel
  • Daemon port
  • Dry-run approval
  • Signal phone QR scan

Outputs

  • Dry-run preview
  • Signal link URI or QR
  • systemd daemon unit
  • Signal daemon health status
  • Hermes environment configuration
  • Hermes gateway reload status
  • Signal smoke-test result

Requirements

  • SSH access to the VPS
  • Root-level VPS privileges
  • Hermes installed on the host
  • Java 17 or later
  • signal-cli installed on the host
  • systemd available on the VPS
  • A Signal phone for device linking

Source

  • Spec: SKILL.md

ClawIndex

OpenClaw Skills & Use Case Index

ClawIndex is an ecosystem-driven index of OpenClaw skills and real-world use cases.

Index

Skills·
Cases

Meta

About·
Disclaimer·
Email·
GitHub
© 2026 ClawIndex All Rights Reserved.
Signal
Hermes
signal-cli
SSH
remote setup
allowlist
systemd
Verify Hermes and Java prerequisites
Validate E.164 allowlists
Link a Signal device
Configure the signal-cli daemon
VPS IP or hostname
VPS SSH user
Signal bot account number
Dry-run preview
Signal link URI or QR
systemd daemon unit