From telegram
Register a new forum thread/topic mapping so messages in that thread route to a specific project subsession. Use when the user wants to connect a Telegram forum topic to a project.
npx claudepluginhub hexpy-games/butler-plugins-marketplace --plugin telegramThis skill is limited to using the following tools:
Adds a new entry to the plugin's `config.json` that maps a Telegram forum
Adds Telegram as a channel to ClaudeClaw by merging code changes from git remote, installing grammy, setting up bot token, and configuring env for control or passive use.
Guides Telegram bot setup for Orchestrator integration: BotFather bot creation, bot_token collection, credentials config in YAML, and long-polling test. Invoke via /connect-telegram.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Share bugs, ideas, or general feedback.
Adds a new entry to the plugin's config.json that maps a Telegram forum
thread ID to a project name and path. When a message arrives in that thread,
it will be routed to the project's subsession instead of the main session.
Arguments passed: $ARGUMENTS
Print:
Usage: /telegram:thread-register <thread_id> <project_name> <project_path>
Example: /telegram:thread-register 24 my-project ~/dev/my-project
<thread_id> <project_name> <project_path>Read the plugin config file. The path is relative to the plugin root:
find the plugin directory by looking for config.json alongside server.ts.
The standard location is the directory containing this SKILL.md, two levels up:
../../config.json relative to this file. Use the absolute path based on
the plugin installation location.
Parse the JSON. Ensure topicRouting object exists with the shape:
{
"topicRouting": {
"enabled": true/false,
"configSource": "...",
"tmuxSession": "...",
"scripts": { "send": "...", "start": "..." },
"topics": { ... }
}
}
Check if thread_id already exists in topicRouting.topics. If so,
warn the user and suggest using /telegram:thread-edit instead. Stop.
Add the mapping:
"topics": {
"<thread_id>": {
"project": "<project_name>",
"path": "<project_path>"
}
}
Write the updated config.json back (2-space indent, trailing newline).
Confirm: "Registered thread <thread_id> -> <project_name> (<project_path>)."
If topicRouting.enabled is false, warn:
"Note: topic routing is currently disabled. Set enabled: true in
config.json and configure tmuxSession and scripts to activate routing."