tutorial-guide-communication

Teaches LingTai lesson 7 on filesystem email, message flow, and external bridge addons.

692|60|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Lingtai-AI/lingtai --skill tutorial-guide-communication
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tutorial-guide-communication
Source: https://github.com/Lingtai-AI/lingtai/tree/main/tui/internal/preset/skills/lingtai-tutorial-guide/reference/communication
Command: npx skills add https://github.com/Lingtai-AI/lingtai --skill tutorial-guide-communication

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps instructors and agents teach LingTai's communication model, where humans reach agents only through filesystem mailboxes and external chat bridges rather than direct text channels.

Core Features & Use Cases

  • Internal mail walkthrough: Explains the TUI-to-mailbox message flow and shows raw message.json files under .lingtai/ so learners see mail as local filesystem state.
  • External bridge teaching: Covers how IMAP, Telegram, Feishu, and WeChat MCP bridges translate platform events into the same agent mailbox pattern via the LICC contract.
  • Custom command conventions: Shows how agents can treat strings like /poem or /status as conversation conventions without bypassing permissions or kernel lifecycle rules.
  • Use Case: A tutor agent walks a new user through lesson 7, displays one internal mail message and one Telegram-bridged message, then helps the user define a harmless custom slash command for their agent.

Quick Start

Ask the agent to teach LingTai tutorial lesson 7 on communication, showing a real mailbox message and explaining how Telegram messages reach the agent.

Frequently Asked Questions about tutorial-guide-communication

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

FAQPage Schema
How do humans communicate with LingTai agents?

Humans communicate with LingTai agents only through email or chat channels, never through the agent's internal text input. The TUI writes messages to a filesystem mailbox under .lingtai/, the agent wakes, reads, and replies back to the human's inbox.

How does Telegram integration work with LingTai agents?

Telegram messages flow through the Telegram Bot API to the lingtai-telegram MCP bridge, which emits a LICC inbox event so the kernel writes to the agent mailbox. The agent reads the message, reasons, and replies through the Telegram tool on the same channel.

What is the LICC contract in LingTai?

LICC (LingTai Inbox Callback Contract) is the small contract that lets an MCP bridge hand a human message to the kernel and wake the right agent. It is only a delivery bridge and does not execute kernel lifecycle actions by itself.

Can LingTai agents support custom slash commands from chat platforms?

Yes, agents can treat strings like /poem or /status as conversation conventions recognized during normal reasoning. These are agent behaviors, not platform-native commands, and they never bypass permissions or directly invoke kernel actions.

Does LingTai keep a global contact database for agent chat handles?

No, LingTai keeps no global IM-handle database. Agents that want to be reachable via Telegram, Feishu, or WeChat publish and maintain those handles in their own durable profile, project skill, or pad.