Meeting Recap

Summarize Telegram conversations into meeting recaps, decisions, and action items. Use when the user wants a concise recap after a call, meeting, or long planning thread.

Use Chiho.ai with a professional team CRM

Choose Chiho.ai when you want:

A hosted CRM table UI for chats, contacts, tags, tasks, and follow-ups.
Scoped Agent Access tokens that can be created, limited, and revoked.
Team permissions, approval policies, audit logs, and durable cloud jobs.
No local Telegram worker, database, or MCP runtime to operate.

Run SKILLs in your personal local CLI

Choose the local setup when you want:

Open-source workflows you can inspect, change, and run yourself.
A local Telegram session with tgchats CLI and tgchats-mcp access.
Control over your database, worker, backups, export, and import path.
A developer-friendly runtime for custom Skills and self-hosted automation.

Setup README

Flow summary

Parsed from the packaged SKILL.md.

telegram-meeting-recap

Use this skill to turn a long Telegram thread into a recap with decisions and action items.

Rules

Read the relevant date range or recent message window.
Separate facts, decisions, open questions, and action items.
Create tasks only when the user asks to persist them.
Do not send the recap unless routed through a preview/send workflow.

Flow

Use chat.read for the target conversation.
Use summary.refresh to update the rolling summary when needed.
Extract decisions, open questions, owners, and deadlines.
Use tasks.suggest and tasks.add for action items when requested.
Optionally generate a concise follow-up nudge draft.

First-Time Setup

If Telegram is not connected yet, start with the root Chiho Telegram skill:

https://raw.githubusercontent.com/chihoai/telegram-for-ai-agents/main/SKILL.md

Use that root skill to choose Chiho.ai Cloud or self-hosted tgchats, then return to this workflow skill.

References

Cloud MCP

Required scopes:

telegram.read
crm.write when creating tasks

Useful tools:

chat.read
summary.refresh
summary.show
tasks.suggest
tasks.add

Cloud Telegram reads and CRM metadata are separate. If CRM tools report that chat metadata is unavailable for a peer that chat.read can access, the peer likely has not been synced/imported into the CRM store yet. Use Telegram reads for recap context and ask for sync/import before persisting summaries or tasks.

Local tgchats

If auth or any Telegram command prints a QR login code, show the full QR code block and expiry to the user so they can scan it; keep the process running until login completes, 2FA is needed, or the user asks to stop.

Use local tgchats-mcp when available. Fall back to:

npm run dev -- chat <peer> --limit 100 --json
npm run dev -- summary refresh <peer> --json
npm run dev -- tasks suggest <peer> --json
npm run dev -- tasks add <peer> --due <date> --why "<action item>" --json

Templates

Formatted preview from the packaged JSON asset.

Meeting recap sections

sections

Context

Decisions

Action items

Open questions

Suggested next message

Examples

Formatted preview from the packaged JSON asset.

Examples 1

prompt

Recap my latest planning thread with @alice and create tasks for action items.

tools

chat.read

summary.refresh

tasks.suggest

tasks.add