Integrate a Signal channel into NanoClaw via JSON-RPC to signal-cli over TCP.
npx skills add https://github.com/Bartunek/nanoclaw --skill add-signal-bartunek
Please help me install this Agent Skill. Skill: add-signal Source: https://github.com/Bartunek/nanoclaw/tree/main/.claude/skills/add-signal Command: npx skills add https://github.com/Bartunek/nanoclaw --skill add-signal-bartunek
Adds Signal messaging support via a native adapter that speaks JSON-RPC to a signal-cli TCP daemon. No Chat SDK bridge — only Node.js builtins, such as node:net, node:child_process, and node:fs.
Fetch the channels branch, copy the adapter and tests, and wire the Signal channel to an agent group.
High-intent search queries and answers about installing and using this skill.
The adapter integrates Signal by speaking JSON-RPC to a signal-cli TCP daemon using only Node.js builtins like node:net and node:child_process, avoiding any Chat SDK bridge entirely.
No Chat SDK bridge is required; the adapter runs entirely on Node.js builtins such as node:net, node:child_process, and node:fs to communicate with the signal-cli TCP daemon.
Signal registration supports two paths: registering a new phone number or linking as a secondary device, with clear setup and credentials guidance provided for reliable operation.
Yes, you can wire the Signal channel to an agent group and manage messaging groups across both DM and group conversations within NanoClaw.
Limitations include relying on a wired signal-cli TCP daemon setup and requiring proper credentials; troubleshooting steps are documented to address operational issues with the adapter.
chiptoe-svgIntegrate Signal messaging into NanoClaw via signal-cli JSON-RPC TCP.
BartunekAutomate onboarding of the first NanoClaw agent for a direct message channel.
PsqasimCoordinate multi-agent communications via typed, immutable messages.
thmtzConnect a NanoClaw agent fleet to Signal via a signal-cli TCP daemon.
