AutoThread turns messages prefixed with /topic into organized platform-native threads, forum topics, or Signal digest messages.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install autothread
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install autothread using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is AutoThread?
AutoThread is an Openclaw Skills integration that lets an agent create a focused conversation from any message beginning with /topic. It automatically generates a concise 3–7 word title, quotes or forwards the original content, and creates the appropriate conversation container for Telegram, Nicegram, or Discord.
Signal does not provide native topics or threads, so its adapter creates a titled digest message instead. Platform credentials remain in the local OpenClaw configuration, while each adapter communicates only with the target platform API. The skill returns consistent JSON metadata so the agent can link back to the new topic and continue the conversation in its dedicated thread.
AutoThread Use Cases
- Organize busy Telegram forum groups by turning important messages into dedicated topics.
- Create public Discord threads directly from existing guild-channel messages.
- Use the same topic workflow in Nicegram chats through its Telegram-compatible API.
- Create titled Signal digests when native topic or thread support is unavailable.
- Preserve message context by quoting text and forwarding media where supported.
- Automatically acknowledge topic creation and continue responding inside the newly created conversation.
- Keep communication workflows consistent across supported platforms with Openclaw Skills.
How AutoThread Works
- Detect a message that starts with
/topicin a supported Telegram, Nicegram, Discord, or Signal context. - Identify the originating platform and collect the required context, including chat or channel ID, message ID or timestamp, sender name, and message content.
- Generate a concise 3–7 word title that summarizes the message.
- Execute the matching platform adapter: Telegram and Nicegram use forum-topic creation, Discord creates a public thread from the source message, and Signal sends a titled digest.
- Quote or forward the original message inside the new conversation where the platform supports it, including media handling for Telegram and Nicegram.
- Parse the adapter's JSON response containing
topic_id,title, andlink. - Reply to the original message with a topic-created link; omit the link for Signal because its adapter returns
link: null. - Send the agent's substantive response inside the newly created topic or thread using the returned
topic_idas the thread identifier. - Return
NO_REPLYafter both follow-up messages have been sent.
AutoThread Setup
- Install the required local binaries:
curl,jq,python3, andsignal-cliwhen Signal support is needed. - Ensure the AutoThread adapter scripts are available in the skill directory:
scripts/autothread-telegram.sh,scripts/autothread-nicegram.sh,scripts/autothread-discord.sh, andscripts/autothread-signal.sh. - Configure the relevant OpenClaw channel credentials in
~/.openclaw/openclaw.json. - For Telegram or Nicegram, enable forum topics, configure the group, provide the bot token, and grant the bot administrator access with Manage Topics permission.
- For Discord, configure the channel and bot token, then grant Create Public Threads and Send Messages in Threads permissions.
- For Signal, install and register
signal-cli, then configure the registered account under the Signal channel settings. - Optionally register Telegram autocomplete with a custom
topiccommand.
bash scripts/autothread-telegram.sh <chat_id> <message_id> "<sender name>" "<title>" "<text after /topic>"
bash scripts/autothread-discord.sh <channel_id> <message_id> "<sender name>" "<title>" "<text after /topic>"
bash scripts/autothread-signal.sh <group_id> <message_timestamp> "<sender name>" "<title>" "<text after /topic>"
For Nicegram, invoke scripts/autothread-nicegram.sh using the same arguments as the Telegram adapter. Pass an empty text argument for media-only messages. Keep Telegram's requireMention default enabled in busy or sensitive groups; disabling it causes any /topic message to trigger content reposting.
AutoThread Data Schema & Taxonomy
Adapter inputs
| Platform | Required identifiers | Content fields |
|---|---|---|
| Telegram | chat_id, message_id |
Sender name, generated title, text after /topic |
| Nicegram | Telegram-compatible chat and message identifiers | Sender name, generated title, text after /topic |
| Discord | channel_id, message_id |
Sender name, generated title, text after /topic |
| Signal | group_id, message timestamp |
Sender name, generated title, text after /topic |
Standard output
Every adapter returns JSON with this structure:
topic_id: The created topic, thread, or Signal digest timestamp.title: The generated conversation title.link: A platform link when available;nullfor Signal.
Generated conversation data
- Telegram and Nicegram create a forum topic and place the original message quote inside it; media is forwarded.
- Discord creates a public thread from the source message and posts the quote inside.
- Signal creates a titled digest message because it has no native topic object.
- Credentials are read locally from OpenClaw configuration and are not transmitted to any service other than the target platform API.
- Telegram topic names are limited to 128 characters, while Discord thread names are limited to 100 characters.
- Telegram attribution may identify the sender in text below the quote because quoted content appears as sent by the bot.
AutoThread Advanced Features
- Separate platform adapters isolate Telegram, Nicegram, Discord, and Signal-specific API behavior.
- Shared helpers provide title fallback handling and consistent JSON output across adapters.
- Supports text messages, media forwarding, quoted content, and media-only Telegram or Nicegram triggers.
- Uses returned
topic_idvalues to route the agent's next response into the correct conversation. - Supports local credential loading through
~/.openclaw/openclaw.jsonwithout introducing a separate credential service. - Provides an offline test suite with a localhost mock API server; the mock server is test-only and is not part of runtime execution.
- Telegram autocomplete can expose
/topicas a custom command for easier discovery. - Permission-aware setup supports Telegram forum administration, Discord thread permissions, and registered Signal accounts.
- Signal fallback preserves the shared workflow even when the platform lacks native topics or threads.
SKILL.md
Loading
Related Openclaw Skills
MRS Redis Metadata Check
A static analyzer that validates MRS Redis nodes-*.conf metadata and diagnoses seven configuration issues behind startup, connectivity, and cluster fault alerts.
M5Stack Firmware Query
M5Stack Firmware Query provides safe, read-only access to live public M5Burner firmware data for discovery, verification, and device-specific recommendations.
Contracko Contract Review
Contracko Contract Review helps agents analyze contracts, monitor renewal deadlines, compare versions, audit risks, and prioritize portfolio actions.
MySQL Schema Best Practice Generator
A MySQL 8.0 schema design and review skill that produces executable DDL, indexing strategies, validation checklists, and actionable risk warnings.
Global Investor Search
Builds a sourced, deduplicated, and transparently verified list of investors in a defined market without inventing completeness or contact data.
Chem-Viz Chemistry Visualization
Chem-Viz turns abstract chemistry concepts into interactive, classroom-ready HTML visualizations that students can explore and understand.
Featured*
