telegram-ops

What This Skill Does

The telegram-ops skill empowers OpenClaw agents to manage Telegram forum-style groups autonomously. It bridges the gap between the OpenClaw orchestration layer and the Telegram Bot API. With this skill, you can programmatically create new discussion threads (topics), update topic metadata, assign custom thematic icons, and manage the underlying configuration that dictates agent behavior within specific group channels. It acts as an administrative bridge, allowing you to scale your community or operations infrastructure directly from your terminal or AI-driven workspace.

Installation

You can install this skill directly via the OpenClaw skill registry:

clawhub install openclaw/skills/skills/brennerspear/telegram-ops

Ensure your bot token is properly set in your OpenClaw configuration. You can verify your environment variables using: gateway action=config.get | jq -r '.result.parsed.channels.telegram.botToken'

Use Cases

• Automated Workflow Orchestration: Automatically create a new 'incident response' topic when a system monitoring alert is triggered in an OpenClaw session.
• Community Management: Organize large groups by creating specialized sub-topics based on user requests, setting descriptive icons for clarity.
• Agent Context Separation: By assigning different system prompts to different topics, one bot can act as a technical support agent in one thread and a project manager in another, all while maintaining isolated session history.
• Lifecycle Maintenance: Use the tool to archive old or completed projects by removing access or shifting the topic context.

Example Prompts

1. "Create a new forum topic in my team group called 'Project Alpha' and set the icon to the target symbol."
2. "Update the system prompt for the topic with ID 452 to include instructions for summarizing all incoming technical questions."
3. "List all available forum topic icons so I can choose the best one for our upcoming meeting thread."

Tips & Limitations

• Permissions: The bot must be granted 'Manage Topics' administrative permissions within the Telegram group settings; otherwise, all API requests will fail.
• Configuration Hierarchy: Remember that topic configurations inherit parent group settings. When patching via config.patch, only include the overrides to avoid cluttering your configuration files.
• Session Management: Each topic is assigned a unique session string: agent:main:telegram:group:<GROUP_ID>:topic:<TOPIC_ID>. This keeps context clean and prevents cross-contamination of unrelated topics. Avoid manual modifications to these session keys in the database.