// Automate Telegram forum topic creation and bind agents to topics in an OpenClaw multi-agent supergroup. Use when setting up or reorganizing team topic channels.
| name | telegram-topic-setup |
| description | Automate Telegram forum topic creation and bind agents to topics in an OpenClaw multi-agent supergroup. Use when setting up or reorganizing team topic channels. |
| version | 1.0.0 |
Copy to agents/<orchestrator>/skills/telegram-topic-setup/SKILL.md. Requires a Telegram supergroup with forum mode enabled and bot admin permissions.
Use the topic-create action to create a new forum topic:
action: topic-create
channel: telegram
target: telegram:<chatId>
name: <topic-name>
icon_custom_emoji_id: <emoji-id>
Returns a topicId on success.
After creating a topic, send a first message immediately using:
threadId: <topicId>
Telegram may not display the topic in the list until the first message is posted.
Only custom emoji IDs from Telegram's forum topic sticker set are valid as icon_custom_emoji_id. There are 38 valid IDs. Common ones:
| Emoji | ID |
|---|---|
| 💻 | 5350554349074391003 |
| 🔥 | 5312241539987020022 |
| 📈 | 5350305691942788490 |
| 💡 | 5312536423851630001 |
If an invalid ID is used, Telegram ignores it and assigns a default icon.
Capture every returned topicId and record it in SUPERGROUP-MAP.md under the corresponding team and agent entry. This mapping drives config generation and agent routing.
Wire each topic to an agent in openclaw.json:
{
"topics": {
"<TOPIC_ID>": {
"requireMention": true,
"enabled": true
}
}
}
Rules:
requireMention: truerequireMention: falseenabled: false on topics owned by other agentsAudit SOUL.md, SKILL.md, IDENTITY.md, and workspace templates for frontmatter compliance, duplicate names across core/extended catalogs, description quality, placeholder hygiene, and prompt-budget size before they are copied into an OpenClaw workspace.
Manage ACPX sessions for delegating tasks from an orchestrator agent to coding agents. Use for agent-to-coding-agent work delegation with named sessions, parallel workstreams, and status tracking.
Standardize coding handoffs between builder, QA, and deploy agents. Use when a coding task moves across stages and requires strict ACK/DONE/BLOCKED status updates, branch metadata, and PR readiness checks.
Transform one source artifact into channel-specific drafts while preserving core thesis. Use for cross-post workflows (X, LinkedIn, Reddit, newsletter snippets).
Qualify leads against ICP with transparent scoring and clear next steps. Use when converting raw prospects into prioritized outreach queues.
Triage operational inputs (email, calendar, tasks) into prioritized action queues with explicit ownership and deadlines.