add-signal

Add a native Signal channel adapter for NanoClaw via signal-cli over TCP.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/wrightchin/nanoclaw-playground --skill add-signal-wrightchin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-signal
Source: https://github.com/wrightchin/nanoclaw-playground/tree/main/.claude/skills/add-signal
Command: npx skills add https://github.com/wrightchin/nanoclaw-playground --skill add-signal-wrightchin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables NanoClaw to communicate with a Signal account through a native adapter that talks to signal-cli over TCP, removing the need for a non-native bridge.

Core Features & Use Cases

  • Native Signal channel via signal-cli TCP daemon for DMs and Groups.
  • Flexible onboarding with either a dedicated number or secondary device, plus wiring to agent groups.
  • Cross-platform guidance for macOS and Linux, including daemon lifecycle management and credential setup.

Quick Start

Register a dedicated Signal number, install signal-cli, enable the NanoClaw Signal adapter, and wire it to an agent group.

Frequently Asked Questions about add-signal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate Signal messaging into NanoClaw using signal-cli?

Signal integration uses a native TCP adapter to connect NanoClaw with a signal-cli daemon, enabling direct messaging and group chat capabilities without an external bridge.

What do I need to set up a Signal channel adapter for agent groups?

You need Java 17+, a signal-cli installation, and a configured SIGNAL_ACCOUNT. You can onboard a dedicated Signal number or a secondary device, then wire it to agent groups.

Can I run the signal-cli TCP daemon on both macOS and Linux?

Yes, the adapter provides cross-platform guidance for macOS and Linux, covering signal-cli daemon lifecycle management and credential setup for both operating systems.

How does the native TCP adapter for signal-cli compare to non-native messaging bridges?

The native TCP adapter removes the need for a non-native bridge by communicating directly with signal-cli, offering a more integrated and streamlined Signal channel workflow.

Do I need a separate phone number to link Signal to an agent group?

No, the adapter supports flexible onboarding with either a dedicated Signal number or a secondary device, allowing you to link credentials to agent groups as needed.