Telegram Meeting Recaps
Turn a Telegram discussion into a concise recap of decisions, open questions, and action items.
Example request
Illustrative scenario, not an executed run.
Summarize this project discussion. Separate decisions from proposals and list actions with the owner and deadline only when stated.
Expected result
A recap that distinguishes confirmed decisions, unresolved questions, and proposed tasks for review.
Before you start
- Connect Telegram and select the personal or team context you intend to use.
- Connect your AI client with browser OAuth, or follow the local setup below.
- Review the workflow’s tools and target conversations. Chat reads and imported CRM records are separate; sync a chat before requesting changes to missing CRM metadata.
A skill does not schedule itself or grant permissions. Describe whether you want suggestions, a dry run, or an action. Client controls and each tool’s safeguards govern execution.
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_readfor the target conversation. - Use
summary_refreshto update the rolling summary when needed. - Extract decisions, open questions, owners, and deadlines.
- Use
tasks_suggestandtasks_addfor 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
Required tool permissions
- telegram.read
- crm.write
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.
- Browser OAuth connections you can review and revoke.
- Shared team context and tool-specific action safeguards.
- 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.

Cloud MCP
Required scopes:
telegram.readcrm.writewhen creating tasks
Useful tools:
chat_readsummary_refreshsummary_showtasks_suggesttasks_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 --jsonnpm run dev -- summary refresh <peer> --jsonnpm run dev -- tasks suggest <peer> --jsonnpm run dev -- tasks add <peer> --due <date> --why "<action item>" --json
Templates
Formatted preview from the packaged JSON asset.
Meeting recap sections
sections
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
Keep building your workflow
Read the related Telegram workflow guideFor unattended jobs, review advanced service-token setup separately.