comm-bridge

Route messages between Telegram and Lark channels and the AI model.

1.1k|123|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/zylos-ai/zylos-core --skill comm-bridge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comm-bridge
Source: https://github.com/zylos-ai/zylos-core/tree/main/skills/comm-bridge
Command: npx skills add https://github.com/zylos-ai/zylos-core --skill comm-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires better-sqlite3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill acts as a central hub, managing all incoming and outgoing communication between external channels (like Telegram, Lark) and the AI, ensuring seamless and organized message flow.

Core Features & Use Cases

  • Unified Communication: Routes messages from various platforms to the AI and vice-versa.
  • Message Queuing & Dispatch: Handles message delivery, retries, and status tracking.
  • Checkpointing & Memory Sync: Manages conversation history for AI memory and synchronization.
  • Use Case: When a user sends a message via Telegram, this Skill receives it, queues it for the AI, and ensures the AI's reply is routed back to the correct Telegram chat.

Quick Start

Use the comm-bridge skill to send a message to the 'telegram' channel with endpoint '1234567890' containing the text 'Hello from Zylos!'.

Frequently Asked Questions about comm-bridge

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

FAQPage Schema
How do I route messages from Telegram and Lark to an AI agent?

Message routing from Telegram and Lark to an AI agent is handled by a central communication bridge that queues incoming messages, forwards them to the core AI model, and routes replies back to the correct chat endpoint.

How does message queuing work for AI agent communication?

Message queuing for AI agent communication works by receiving external messages, persisting them via SQLite database operations, and dispatching them through a daemon to ensure reliable delivery, retries, and status tracking.

Can I use SQLite for AI conversation history and memory synchronization?

Yes, you can use SQLite for AI conversation history by persisting messages and checkpoints, which facilitates memory synchronization and maintains conversation state across external channels.

What is the best way to manage external communication channels for an AI model?

The best way to manage external communication channels for an AI model is using a central gateway that unifies message routing, dispatch, and conversation history tracking across platforms like Telegram and Lark.

Do I need a database to handle AI message dispatch and status tracking?

Yes, a database is required to handle AI message dispatch and status tracking, as message persistence and control plane management rely on SQLite operations to queue and monitor delivery.

Why does conversation checkpointing fail without a dispatcher daemon?

Conversation checkpointing fails without a dispatcher daemon because the daemon manages the control plane operations required to synchronize memory and route queued messages between external channels and the AI.